SphereCommunity
0.56.4.704 to 0.56.4.713 trigger @step and spawn problems - Printable Version

+- SphereCommunity (https://forum.spherecommunity.net)
+-- Forum: Sphere 0.56d (/Forum-Sphere-0-56d)
+--- Forum: General Help (/Forum-General-Help)
+--- Thread: 0.56.4.704 to 0.56.4.713 trigger @step and spawn problems (/Thread-0-56-4-704-to-0-56-4-713-trigger-step-and-spawn-problems)



0.56.4.704 to 0.56.4.713 trigger @step and spawn problems - midikit - 12-13-2018 12:28 AM

When using @step trigger on item
If stepping on a triggered item,
In 0.56.4.703 and earlier versions, the trigger is executed every second.
However, from 0.56.4.704 to 0.56.4.713 the trigger is executed only once.

And, the timer of the spawn
Up to 0.56.4.703 works fine without problems.
However, from 0.56.4.704 to 0.56.4.713, all were changed to 86399.
This is the same for all spawn time ranges.
Of course, double-clicking a spawn to force a respawn will change it to match the spawn time range value.


RE: 0.56.4.704 to 0.56.4.713 trigger @step and spawn problems - Seokotov - 12-13-2018 03:11 AM

Also have many problems with memories TIMER=0 on chars.
Looks like a big timer's error.
https://github.com/Sphereserver/Source/issues/161


RE: 0.56.4.704 to 0.56.4.713 trigger @step and spawn problems - Coruja - 12-20-2018 06:58 AM

I think this problem is related to sphere startup not setting TIMER value correctly on chars/items loaded from worldsave files, which already got fixed yesterday

so try using the latest build 719 to check if it's working fine


RE: 0.56.4.704 to 0.56.4.713 trigger @step and spawn problems - midikit - 12-20-2018 11:33 AM

This problem works fine at 0.56.4.719
Thanks coruja Smile