23.11.2012, 08:05
compare each filterscripts' functions/callbacks used, and pay special attention to the return's at the functions end. if you load f.ex my old fireworks script, which contains a return 1; in its dialog response, it will stop the gamemodes' dialogresponses. when you remove that return 1; from my script, then it wont stop other dialogs being processed.
one first start would be: sort your callbacks, its easier to compare them (maybe on 2 monitors lol)
another way would be to load only 2 filterscripts, loaded in a different order, to track down the "bug".
yes, that bothered me for a long time aswell, i have read shit like "make it return 1, or return 0, or return -1" - the sad fact is, "return" means fucking RETURNing a value, regardless of the value, therefore it stops processing.
tip#1: make a backup of your entire filterscripts directory (copy it to somewhere else), so you can modify your existing scripts with no need to worry about to screw them.
addition: i AM talking of the order of loading the scripts, its vital to know how each script behaves.
modifying the order can lead you to the right conclusion.
one first start would be: sort your callbacks, its easier to compare them (maybe on 2 monitors lol)
another way would be to load only 2 filterscripts, loaded in a different order, to track down the "bug".
yes, that bothered me for a long time aswell, i have read shit like "make it return 1, or return 0, or return -1" - the sad fact is, "return" means fucking RETURNing a value, regardless of the value, therefore it stops processing.
tip#1: make a backup of your entire filterscripts directory (copy it to somewhere else), so you can modify your existing scripts with no need to worry about to screw them.
addition: i AM talking of the order of loading the scripts, its vital to know how each script behaves.
modifying the order can lead you to the right conclusion.