Jump to content

BSL:Functions: Difference between revisions

m
(chr_index information)
Line 73: Line 73:
In this example Mukade have the index 2, but once it's deleted (in this case directly by <tt>chr_delete</tt> function) there will be hole where his id were. When Bomber is spawned, it isn't associated the index 3, but it will be associated the index 2, to fill the hole left behind.
In this example Mukade have the index 2, but once it's deleted (in this case directly by <tt>chr_delete</tt> function) there will be hole where his id were. When Bomber is spawned, it isn't associated the index 3, but it will be associated the index 2, to fill the hole left behind.


Seems the <tt>chr_index</tt> variable works like in a buffer in memory, once some variable in the buffer is cleared, in the next opportunity it is filled up again.
Seems the <tt>chr_index</tt> variables make part of an array in memory, once some variable in the array is cleared, in the next opportunity it is filled up again.


==Native functions==
==Native functions==
489

edits