Jump to content
  • 0
Sign in to follow this  
112112113

ZERO :quest BUG??

Question

 Such as:

       next();
        setquest(21001);

Such as this setquest or related quest command scripts will be stuck。

No NEXT~~~~~

 

 use is Ragexe1206 _zero.exe~ Ragexe1212 _zero.exe~

:bawling:

Can you test it

 Such as:

       next();
        setquest(21001);

Such as this setquest or related quest command scripts will be stuck。

No NEXT~~~~~

 

 use is 1206 _zero.exe

The client task interface also cannot display tasks.

Can you test it?

SBE9PG`[X(4OOF7J`(W(%G4.png

R){8MI1B2ONP1_}WL6W}GAX.png

Share this post


Link to post
Share on other sites

7 answers to this question

Recommended Posts

  • 0

Questid2display.txt does not seem to be a problem,

even if no information in the questid2display.txt SETQUEST or "NULL" will be reflected in the client,

but the client in ZERO within the existing QUEST instruction will cause the script do not continue to run, people stuck, without any client information display.

Share this post


Link to post
Share on other sites
  • 0

Zero client not support questid2display.txt at all.

I think it using lua files for quests. And if this files removed from grf, will be not quests.

112112113 probably you using quests in grf from main kro client, but it may not works. Or server quest may be missing in quests lua files.

Share this post


Link to post
Share on other sites
  • 0
 

It is now found that the task information file of the ZREO client is in the SYSTEM/OngoingQuestInfoList.lub

The file contains most of the tasks of the old version and the task of ZERO, and the information of most of the HERC's existing tasks is included in this file.

For example, there are some new novice tasks and the Eden mission.

Both the client and the server appear BUG~

Using setquest in the script will cause the script to be stuck.
Unable to appear NEXT or CLOSE.
The client does not seem to have received the information at all.

These problems appear only in the zero client.

 

Edited by 112112113

Share this post


Link to post
Share on other sites
  • 0

Can you check same issue on one of latest kro clients? I mean 2017-12 ot 2017-12

 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
Sign in to follow this  

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.