Yes it does. Most themes scripts that are properly written use the & prefix before all of the events that it uses, so it isn't processed if $halted is true as a result of another script halting the text BEFORE the theme. When you load a new script, that script by default goes to the bottom of the script list and is processed after the theme if they had a theme loaded previous to the new script. For Joe User that likes themes and is looking for a script to use, he wouldn't have any idea what to do in this situation. It has nothing to do with poor scripting skills in this case, as both scripts do what they are supposed to do. Right now, it would be pointless to tell a script (a theme script) to move itself to the bottom every single time a new script loads. It would be a pain in the butt and there is a much simpler solution. If all you do is add a -t flag to the /load command, it would treat the script file as a theme script and it would process all of the theme scripts (if for whatever reason they have more than one) in order, AFTER the regular scripts have been processed. Maybe calling it a "theme script" is a bad choice of words. Basically, it is just a flag to force the script to process last without actually making it last in the script list.