Element bugs

[Phat Looser]

Try it yourself:

When you create an object server side and store it in a list, like

elementlist[k]=createObject(...)

traffic light or green goo, maybe,

and you do

removeObject(elementlist[k]) --k is the same k as above, its an integer value used as an handler

the object isn't removed, but it is afterwards, when you give the elementlist[k] another value, like

elementlist[k]=0.

Maybe I was too stupid, but this happened to me in three different scripts, I started them all from scratch, all of them pretty different, so, its a weird thing.

Also, when this bug happens, another bug happens when you use the list: the script does NOT create an element on "createObject" (especially when the map is filled with objects, like in my AI script). But that second bug doesn't appear too often, and it also might be a bug in my scripts, but since it was quite annoying...

All scripts server side.

[darkdreamingdan]

removeObject?

[Phat Looser]

removeObject?

As soon as i know all functions by heart, you may call me a geek.

I meant the one which deletes the object, which also can be used for cars, i.e.

[Mr.Hankey]

i experienced this problem too i think it has to do with testing scripts on a localhost server... Sometimes objects/elements just stay visible ingame though you clearly removed them in a function that worked 2 times correctly before and these objects don't exist in the script/element tree anymore.

[Cazomino05]

Also happens with createObject sometimes too but i don't know the cause since i use window mode AND localhost

[Ace_Gambit]

This is confirmed by me as well. Sometimes object created with createObject do not show for some players even though others can clearly see them. After reconnecting the invisible object become visible to the player who didn't see them the first time. Also removing objects is buggy at times (old object still showing after I destroyed them).