Avoid player "save" and "load"

[wanrex]

I am pretty new in writing Wherigo, searched a bit about that in forum, not found, so decided to start a new thread.

 

I am writing a Wherigo, that require cacher to travel from zone a to zone b within 30 seconds.

 

So how can I avoid cacher use save and load to cheat it?

 

Thanks in advance.

[+on4bam]

I am writing a Wherigo, that require cacher to travel from zone a to zone b within 30 seconds.

 

So how can I avoid cacher use save and load to cheat it?

 

Don't know if it's possible but could a timestamp be used instead of a timer? Then even after saving the time should be kept and the difference measured.

[Ranger Fox]

Wherigo is set up so all timers expire when the cartridge is resumed. If this is not the case in the Wherigo Player you are testing, it is not functioning to specification and should be fixed.

[wanrex]

Wherigo is set up so all timers expire when the cartridge is resumed. If this is not the case in the Wherigo Player you are testing, it is not functioning to specification and should be fixed.

All timer expired after it resumed?

Um... I tried like that, set a timer for 30 second, then run it at ipad and android.

When the timer is started, I didn't save the game, BUT kill the task at ipad and android (kill the apps i mean).

Then when I restart Wherigo player, the timer will continue, does it normal? or sth wrong?

Please advise, thanks in advance.

[Ranger Fox]

Yes, something is wrong if the timer does not expire after the cartridge is resumed. That's provided the cartridge author didn't set something up to resume the timer on restore. But according to when I discussed timers in 2008, countdown timers are supposed to expire upon restore. (Count up timers are a different story.)

[wanrex]

Yes, something is wrong if the timer does not expire after the cartridge is resumed. That's provided the cartridge author didn't set something up to resume the timer on restore. But according to when I discussed timers in 2008, countdown timers are supposed to expire upon restore. (Count up timers are a different story.)

 

Ok, then I understand why, actually I am using the count up timer, but use a variable to make it run for 30s (then I can show the remaining time to cacher every second) ....

um... I need to think of a workaround.

Thanks.

[Ranger Fox]

Ok, then I understand why, actually I am using the count up timer, but use a variable to make it run for 30s (then I can show the remaining time to cacher every second) ....

um... I need to think of a workaround.

Try one of my cartridges, Run to "The Outback". I used a countdown timer that expired every few seconds so I could display the current time remaining to the player. I didn't have the timer set for every second because I was worried about the Garmin units being able to keep up. This was in 2010, when many people in my area were playing with an Oregon.

[wanrex]

Ok, then I understand why, actually I am using the count up timer, but use a variable to make it run for 30s (then I can show the remaining time to cacher every second) ....

um... I need to think of a workaround.

Try one of my cartridges, Run to "The Outback". I used a countdown timer that expired every few seconds so I could display the current time remaining to the player. I didn't have the timer set for every second because I was worried about the Garmin units being able to keep up. This was in 2010, when many people in my area were playing with an Oregon.

Thanks for your help.

I used the event of "Cart Restore" to avoid cacher save and load, it works fine now.

And I had tune the counter to display remaining time every 3s now, hope it work fine in all device.

Anyway, thanks for your help again, you are so helpful!