What does CRITICAL:Exception code=0c0000005, addr=022f3, in Main Loop mean?
This sadly is a catchall error with no one specific or easily discernable cause. Here is an impartial list of things that can cause them:
Missing
[EOF] at the end of files
NPCs getting negative stats (like an item script that does a -5 STR on unequip for example)
Missing
ENDIFs on if statements
Missing
ENDDOs in
DORAND/
DOSWITCH statements.
Script equipping a
t_script item.. use
t_eq_script.
To ease troubleshooting efforts, only add one new script at a time, resync, test it out thoroughly. If it works ok, then add another. Usually if you get these errors, it's one of the recent scripts you've added or changed causing it. Alternatively, it could be a new NPC or item that was created or spawned in the worldfile that you scripted ages ago. Remember, a script can be completely broken and you won't know it until it is used in the game.
What does 19:52:ERROR:(some_script.scp,21)Undefined symbol " mean? It is spamming my console!
This generally means a script is telling Sphere to get a value of a
TAG or
VAR that doesn't exist. Basically, if you had a script doing
IF (<SRC.TAG.BLAH> == 2) and
TAG.BLAH didn't exist, it would give you this error, because the result of that would be something like
IF (nothing == 2). To prevent this error, always define your
TAGs and
VARs beforehand with
TAG.BLAH=0 or
VAR.BLAH=0. Any value will work, that's just the easiest.
What does this mean? I get it after I resync Sphere.ini changes.
WARNING:Resource 'sphere.ini' changed, resync.
CRITICAL:Exception code=0c0000005, addr=053f26a, in Main Loop
CRITICAL:Assert pri=2:'purecall' file 'unknown', line 1, in Main Loop
This doesn't happen all the time, and very rarely with a
Sphere.ini that has no router settings, but when it does it's rather annoying. Basically, I only see this happen to me when I have two entries (because I use a router) in
Sphere.ini under
[SERVERS]. Not much to do to fix this, just restart Sphere when you change the .ini if you get this error too. After getting it, make sure you do a good worldsave, then restart Sphere. No one will be able to connect to you after getting that error until you restart it. This error is either fixed or -very- uncommon in the later 99x versions of Sphere. Happens the most in 55i from my experience.