Post: #11

using FOR you are far away from perfectionism

Post: #12

(08-14-2012 11:35 AM)WRWR Wrote:  using FOR you are far away from perfectionism

Think better, FOR is for things that are not common.
If you don't want to store lots of TAGs, the best way is using FOR.
But, each one knows what is better for them.
If you see my FOR, its breakable by RETURN 1 if the quest is already completed.
Or just use defnames or mysql or whatever...
I know one thing: for this problem, FOR is faster than MYSQL requests.
FOR is for standards, if you know the template, FOR is the best thing to use.

But of course, I can be wrong or not, just my opinion.

Post: #13

If you have a religious necessity to use one variable, i think the better way is LISTs. There you have FINDELEM and don't need to to handreds of loops. But really, I think my method(above) is the best one - the simple IF check and minimal use of memory. 10 tags? But what harm do 10 tags? My 10 tags will use less memory, than your 1 tag.

Post: #14

(08-13-2012 11:22 AM)Extreme Wrote:  Or you can store the Number ID of all completed quests in only one tag.
And check if the Number ID is in the tag to avoid repeat it.

When complete:

Code:

TAG.COMPLETEDQUESTS .= ",<QUESTNUMBER>"

To check if the quest is already completed:

Code:

[FUNCTION F_QUESTS_CHECKCOMPLETE]
LOCAL.QUESTNUMBER <ARGS>
ARGS <TAG.COMPLETEDQUESTS>
FOR 0 <EVAL <ARGV>-1>
IF STRMATCH(<LOCAL.QUESTNUMBER>,<ARGV[<LOCAL._FOR>]>)
  RETURN 1
ENDIF
ENDFOR
RETURN 0

Usage F_QUESTS_CHECKCOMPLETE <QUESTNUMBER>

I´m updating my scripts with this system.

What is the best method to repeat a completed quest?
How do you extract a single <LOCAL.QUESTNUMBER> from all TAG.COMPLETEDQUESTS string?

Post: #15

(10-05-2012 08:55 PM)Gil Amarth Wrote:  

(08-13-2012 11:22 AM)Extreme Wrote:  Or you can store the Number ID of all completed quests in only one tag.
And check if the Number ID is in the tag to avoid repeat it.

When complete:

Code:

TAG.COMPLETEDQUESTS .= ",<QUESTNUMBER>"

To check if the quest is already completed:

Code:

[FUNCTION F_QUESTS_CHECKCOMPLETE]
LOCAL.QUESTNUMBER <ARGS>
ARGS <TAG.COMPLETEDQUESTS>
FOR 0 <EVAL <ARGV>-1>
IF STRMATCH(<LOCAL.QUESTNUMBER>,<ARGV[<LOCAL._FOR>]>)
  RETURN 1
ENDIF
ENDFOR
RETURN 0

Usage F_QUESTS_CHECKCOMPLETE <QUESTNUMBER>

I´m updating my scripts with this system.

What is the best method to repeat a completed quest?
How do you extract a single <LOCAL.QUESTNUMBER> from all TAG.COMPLETEDQUESTS string?

<GETARGVX X,<TAG.COMPLETEDQUESTS>>
Where x is the position.


To get the position :
<GETARGVPOS <STRINGTOSEARCH>,<STRING>>

Post: #16

If you are making repeatable quests... why would you write their value into a tag that records which quests have been completed and prevents players from repeating them?

Post: #17

Really I don´t want this script for quests, but the code it´s the same for other projects which I want store in only one tag.

Thank you very much, Extreme. I owe you one.

Post: #18

(10-06-2012 12:19 AM)Mordaunt Wrote:  If you are making repeatable quests... why would you write their value into a tag that records which quests have been completed and prevents players from repeating them?

It can be used in many systems, just need know what system is better to use hehe

(10-06-2012 02:47 AM)Gil Amarth Wrote:  Really I don´t want this script for quests, but the code it´s the same for other projects which I want store in only one tag.

Thank you very much, Extreme. I owe you one.

Nope!

Post: #19

I think you dont need even for argv and for cycle to check whether your tag consist of what you want to seeking for. That is so simple

Whether you check for argn or argv or even args , it is up to you.

IF STRMATCH(*<argn>*,<TAG.COMPLETEDQUESTS>)
RETURN 1
ENDIF
ENDFOR
RETURN 0

Post: #20

(10-06-2012 05:57 AM)Avatar Wrote:  IF STRMATCH(*<argn>*,<TAG.COMPLETEDQUESTS>)
RETURN 1
ENDIF
ENDFOR
RETURN 0

I think you dont need even for argv and for cycle to check whether your tag consist of what you want to seeking for.

Sure, but, looking for quest 1, it will match in quest 10, so isn't perfect.