Spin Khan 0 Report post Posted August 17, 2017 What is the going wisdom for troubleshooting filters that just don't seem to "take?" I keep getting hit with this one, Quote 17.08.2017 18:19:34: Spin (73.255.117.176:2304) 0e1a00fcda93fcf75393b8d91c65a5ca - #0 "chFrame", babe_core_fnc_handleEHs] call BIS_fnc_addStackedEventHandler; } else { BABE_MAINLOOP = addMissionEventHandler ["EachF" Despite the fact that (using BE_AEG) I've got, Quote !="chFrame\", babe_core_fnc_handleEHs] call BIS_fnc_addStackedEventHandler; \n} else\n{\nBABE_MAINLOOP = addMissionEventHandler [\"EachF" Added to line #2, the exception strings for the eventHandler keyword. If that doesn't work, and the BE kick keeps happening, I'm stuck on where to go next! Any thoughts or help? Thanks! Share this post Link to post Share on other sites
Z80CPU 527 Report post Posted August 18, 2017 Hello Spin, I personally take shortcuts. MOST of the time, they are 'safe', not always! So BE CAREFUL! Do this, instead of an EXACT MATCH, use 'match anything' You: !="chFrame\", babe_core_fnc_handleEHs] call BIS_fnc_addStackedEventHandler; \n} else\n{\nBABE_MAINLOOP = addMissionEventHandler [\"EachF" Me: !"BABE_MAINLOOP" or !"BABE_" This removes ANY chance of a syntax error in your line. Also, ANY command that uses "BABE_MAINLOOP"/"BABA_" will get 'passed thru'. Again, this CAN BE A DANGEROUS 'shortcut'! Use at your own risk! Outside of the risk, it does work like a champ! If this still does not work, then this means one of three things: #1 - You have it on the 'wrong line' #2 - You have it in the wrong file #3 - #1 and #2 Share this post Link to post Share on other sites