08.02.2012, 14:07
if its the gamemode, a return 1; will do fine, as vince stated. (return 1; sends a "succes. all fine. abort excecution).
if you're using it as filterscript, remove the return 0/1 in order to let the (failed) text pass to the next scripts' callback. (no aborting at all, compiler will complain, ignore that).
if you want a filterscript to fuck up the gamemodes' onplayertext (not passing scripts until the gamemode script can catch the text), then return 1; in a filterscript.
to all who want to rage coz "you NEED to return something in that callback blablabla", go try it yourself, or keep your mouth shut, iam abusing this trick in >4 (loaded together) filterscripts yet, without ANY problems +++
if you're using it as filterscript, remove the return 0/1 in order to let the (failed) text pass to the next scripts' callback. (no aborting at all, compiler will complain, ignore that).
if you want a filterscript to fuck up the gamemodes' onplayertext (not passing scripts until the gamemode script can catch the text), then return 1; in a filterscript.
to all who want to rage coz "you NEED to return something in that callback blablabla", go try it yourself, or keep your mouth shut, iam abusing this trick in >4 (loaded together) filterscripts yet, without ANY problems +++