
Originally Posted by
maat7043
1.,Have you considered:
CODE
getlocal 0
Pushscope
Returnvoid
Right after code rather than simply putting returnvoid? This would completely resolve the issue of trying to guess where the correct pushscope is. The second instance of loc0 pushscope will never be accessed.
2. I have used file size, line count and hits on certain things like trait slots to distinguish the correct file. There is always a way
3. If you do mods first and you don't know what type of private hacks the user may be adding you have no idea if your automatic hacking are finding bits if the users code. After is more fool proof
1) You have a point. But it was just giving the first exemple that came to my mind. Its not always as simple as that

2) File size? Line count? Its not reliable at all in my opinion .
Of course i look for strings, named methods, trait slots, etc... to locate the
FILE & some
NAMES -it depends-
The problem is mainly when you have to patch the code. You must find the correct location ,sometimes with something like 3 or 4 consecutive instructions.. and there can be junk stuff between those instructions.. I wont code an "ignore junk stuff to find those instructions set" for
each individual hack who need it.
* Because i want to keep the source code simple. And avoid Copy pasta ! There is already too many stuff i should turn into methods.
* Junk is a problem? Deal with that once and for all -> Make a function which takes the file as parameter and return the dejunked code.
3) And mods will be screwed depending on which hacks you apply

. But you are right, since most of the people wont use mods anyway.
Its up to mods makers to test if their stuff works after hacking. For that there is already the "leave dissasembled files" option in config.ini and the log display what files are modified by each mod
I have to take care about hacks and nothing else. (mods = modselector stuff, hacks = orape automatic feature when i talk)