Recent content by Xeirh

surprised it still works with the update t6 recently had, sadly soon enough the steam 64-bit will come and nuke it.

this is pretty much summed up to missing includes, being using or qualified call, in the other one getpayername 1 param can be caused by alot, either too many params, most common or no params

goated btw ... if you can get past the cooljay reserved variables, but that only applies to multiple element usage, we went belt to ass on this, you will never crash using this. - Crimson J. Chin

yeah this is currently what I'm using, came to the conclusion that passing arrays via params created a temporary copy that causes a leak so a direct ref or an additional helper function will fix this, this is leak free, but I use same frame reconstruction, so I destroy and create within frames...

nothing complicated about that, arrays use twice as much memory, you have to undefine parent also to restore the memory. destroy automatically undefines the element, array = 1 parent, contents = 1 child, destroy = +1 child, but now you have to manually undefine the parent to restore the memory...

this is something that humanity probably doesn't deserve, but this would work on all titles, if conditional operators not supported just use statements with conditions and call it a day. also keep in mind that the archive system is tested for black ops II

gscr is just a custom extension, at the end of the day it gets recompiled so the game can read it, best way is the yank it from the memory or use a redacted python plugin. If it's just a reg gsc file sadly depending on the case gsc-tool won't like it even after the old compiler fix param. so...