08-01-2014, 10:40 AM
(08-01-2014, 04:56 AM)Nyamaiku Wrote: i did have a few problems waaay before with next: 1000(remember it was something with a ball).So after a bit of testing I found out that it seems that whenever next: is bigger than or equal to 400 it deletes the object unless it is 999 in which the object goes to frame 0 (unless in the air) or in the range 1100-1299 in which it makes the object invisible.
ever since, i tend to use 9998 more often, though i still avoid using it if possible.
about whether it is a next or state, might be that i remember wrongly. but i guess 9998 can be used on both?
That said I don't think the game handles the cases any different though I could be wrong obviously.
Could a better data changer confirm this?
Age ratings for movies and games (and similar) have never been a good idea.
One can learn a lot from reinventing wheels.
An unsound argument is not the same as an invalid one.
volatile in C++ does not mean thread-safe.
Do not make APIs unnecessarily asynchronous.
Make C++ operator > again
Trump is an idiot.
One can learn a lot from reinventing wheels.
An unsound argument is not the same as an invalid one.
volatile in C++ does not mean thread-safe.
Do not make APIs unnecessarily asynchronous.
Make C++ operator > again
Trump is an idiot.

Chat

