Difference between revisions of "Error Codes"

From SphereWiki
Jump to: navigation, search
(Created page with '__FORCETOC__ ==Exit Codes== When Sphere closes, an 'exit code' will normally be shown in the console to describe why it is being shut down. In general, an exit code less than 0 i...')
 
m (Added languagemenue)
Line 1: Line 1:
 +
{{Languages|Error_Codes}}
 +
 
__FORCETOC__
 
__FORCETOC__
 
==Exit Codes==
 
==Exit Codes==

Revision as of 21:53, 26 November 2010

Help
Available languages


Exit Codes

When Sphere closes, an 'exit code' will normally be shown in the console to describe why it is being shut down. In general, an exit code less than 0 is considered to be an error code, and values above 0 are normal shutdown codes. In most cases, a more descriptive error will be shown in the console and/or log file to help better diagnose the reason behind error codes.


The following table lists all of the current codes and their meanings.


Code Description
-10 Unexpected error occurred
-9 Failed to bind server port
-8 Failed to load world save(s)
-3 Failed to load server settings (script, ini, mul files)
-1 Shutdown via commandline (/?, /T and /Q switches)
1 X in console or
SIGHUP signal, terminal closed (Linux Only)
2 SHUTDOWN command
4 Service shutdown (Windows Only)
5 Console window closed (Windows Only)
6 SIGABRT signal, process aborted (Linux Only)


Garbage Collection

The purpose of garbage collection is to validate all of the server objects and free up unused UIDs. Garbage collection is initiated:

  • After the world save is loaded at startup.
  • Before a world save begins, if the FORCEGARBAGECOLLECT setting is enabled in Sphere.ini.
  • After the IMPORT or RESTORE functions have been used on the server object.
  • When the 'G' command is entered via the Sphere console
  • When the GARBAGE function is used on the server object.


When garbage collection encounters a problem with an object it may attempt to automatically correct the error, otherwise the object will be removed. When an object is removed by garbage collection there will normally be an error shown in the console describing the item that was removed along with the reason. The following table lists all of the garbage collection codes along with their description:


Code Description
1102 Disconnected character not acting as such.
1103 NPC with STATF_Ridden does not have the correct action set.
1104 Ridden NPC without a mount item.
1105 Ridden NPC with a mount item that is not linked to them.
1106 Disconneced NPC neither dead or ridden.
1107 Ingame character that is neither a player or an NPC.
1108 Character not on a valid position.
1203 NPC with STATF_Ridden does not have the correct action set.
1204 Ridden NPC without a mount item.
1205 Ingame character that is neither a player or an NPC.
2102 Item without an ITEMDEF.
2103 Item ITEMDEF with an ID of 0.
2104 Disconnected item.
2105 Item not on a valid position.
2106 Item flagged as being in a container but it isn't.
2202 Item flagged as equipped but it isn't.
2205 Item's LINK property is set to itself or a UID that doesn't exist.
2206 GM Robe or Deathshroud not on a character.
2207 Deathshroud not on a dead character.
2208 GM Robe on a character without privileges.
2220 Trade window memory not equipped in the correct layer, or not equipped to a player.
2221 Client linger memory not equipped in the correct layer, or not equipped to a player.
2222 Memory not equipped or is not a real memory.
2226 Mount memory not equipped in the correct layer.
2227 Hair or beard item is not equipped, not in a corpse, and not in a vendor box.
2228 Hair or beard item is equipped, but not in the correct layer.
2229 Game piece not in a container.
2230 Item equipped in layer_none but it isn't a trade window.
2231 Item equipped in layer_special but it isn't a memory or script type.
2233 Item equipped in layer_horse but it isn't a mount memory.
2234 Item equipped in the client linger layer but it isn't a client linger memory.
2235 Item equipped in the murder memory layer but it isn't a murder memory.
2236 Item flagged as decay but without timer set.
3101 Object is totally lost, no parent exists.
3102 Object was deleted or UID is incorrect.
3201 More than one object with the same UID.
4222 Memory item is not equipped, not in the memory layer, or without colour
4223 Memory not on a character.
4224 Guild/town memory does not link to the character's town/guild.
4225 Guild/town memory linked to a stone, but the character is not a member.
7101 Object's UID does not match up with server's UID table.
7102 Object does not exist.
FFFF Bad memory allocation (unknown error occured).