Sims 2:Object Errors - Revision history

Nysha at 08:55, 5 August 2017

2017-08-05T08:55:07Z

2014-07-31T01:54:25Z

2014-07-31T01:52:42Z

‎Object Error Listing:

2014-07-09T20:37:17Z

‎8. Undefined Transition: Added note about using these a debugging tool.

2014-07-09T20:28:14Z

‎7. Too many iterations

2014-07-09T20:27:40Z

‎7. Too many iterations

2014-07-09T20:21:28Z

‎108. Slot number out of range: Added link to the Wiki Slot entry

2014-07-09T20:18:24Z

‎129. Attribute Number out of range: Up to 8 attributes are available by default

2014-07-09T20:09:35Z

‎7. Too many iterations: Added note about introducing an Idle to prevent this error

2012-09-19T03:53:03Z

Reverted edits by HugeLunatic (talk) to last revision by Kiwi tea

@@ Line 149: / Line 149: @@
 #  Random number range evaluated to zero.
 #  Bad parameter to update primitive.
-#  Temporary reference out of range.
+#  [[#133. Temporary reference out of range|Temporary reference out of range]].
 #  Bad operator.
 #  Bad parameter in look towards primitive.
@@ Line 263: / Line 263: @@
 ====130. '''Illegal primitive code'''====
 	Occurs when a non-existent Primitive is attempted to be called; Primitives being defined as an OpCode between 0x0000, and 0x00FF
 ====136. '''Divide by zero'''====

@@ Line 246: / Line 246: @@
 	When an expression attempts to change a read-only value, such as "Time of Day".  Most of the ''Global From Simulation'' data types are read-only.
-====118. '''Bad gosub tree number'''====
+====118.'''Bad gosub tree number'''====
-        When you have a BHAV in a format for an EP you don't have.
+	When you have a BHAV in a format for an EP you don't have.
 ====120.'''Reference to stack object out of range'''====

@@ Line 134: / Line 134: @@
 #  Expression attempting to write in a read-only area. [http://www.sims2wiki.info/wiki.php?title=Object_Errors#116._Expression_attempting_to_write_in_a_read-only_area 116]
 #  Zero distance in finding direction.
-#  Bad gosub tree number.
+#  [[#118. Bad gosub tree number|Bad gosub tree number]].
 #  Bad alert tree number.
 #  Reference to stack object out of range. [http://www.sims2wiki.info/wiki.php?title=Object_Errors#120.Reference_to_stack_object_out_of_range 120]
@@ Line 245: / Line 245: @@
 ====116. '''Expression attempting to write in a read-only area'''====
 	When an expression attempts to change a read-only value, such as "Time of Day".  Most of the ''Global From Simulation'' data types are read-only.
 ====120.'''Reference to stack object out of range'''====

@@ Line 193: / Line 193: @@
 ====8. '''Undefined Transition'''====
-	This occurs when a node's true, or false branch lead it to error(a value of 0xFFFC), rather than another line, or ending the BHAV as true(0xFFFD) or false(0xFFFE).
+	This occurs when a node's true, or false branch lead it to error (a value of 0xFFFC), rather than another line, or ending the BHAV as true(0xFFFD) or false(0xFFFE). The intentional insertion of error(0xFFFC) tests during code development is a useful means of debugging, but ideally these should be removed from production code in favour of either silent error handling routines or the provision of user friendly error messages.
 ====48. '''Inventory token propert index out of range'''====

@@ Line 190: / Line 190: @@
 This occurs when a node in a BHAV is run more than 10,000 times.  It often occurs when a node is linked to itself, or in [[0x001F|Set To Next]] that are too broad(resulting in more than 10,000 items), or if you zero out the variable you using in [[0x001F|Set To Next]] prior to each call (resulting in the same item being found 10,000 times).  In this case the error can be fixed by using concise searches, and by making sure that no nodes make loops that will cause them to be run 10,000 times.
-At other times this error will occur even if there is no mistake in the coding, but simply because an object is running a long and complex section of code without giving the game time to service other functions. In this case the insertion of an [[Idle]] at some point in the code prior to where the error typically occurs will prevent the "Too many interations" error. The idle call often only requires "1" tick as its parameter.
+At other times this error will occur even if there is no mistake in the coding, but simply because an object is running a long and complex section of code without giving the game time to service other functions. In this case the insertion of an [[Idle]] at some point in the code prior to where the error typically occurs will prevent the "Too many interations" error. The [[Idle]] call often only requires "1" tick as its parameter.
 ====8. '''Undefined Transition'''====

@@ Line 229: / Line 229: @@
 ====108. '''Slot number out of range'''====
-	This means that there is no entry in the SLOT of the value requested in that node.
+	This means that there is no entry in the [[SLOT]] of the value requested in that node.
 ====109.'''Motive number out of range or not an acceptable value'''====

@@ Line 256: / Line 256: @@
 ====129. '''Attribute Number out of range'''====
-If you see this error, the likelihood is that you have not allocated space for the number of attributes you are trying to use. Space must be allocated in the [[OBJD#Raw Data - Data Space|OBJD - Data Space]]. You seem to be able to use a few without having to do this, so I expect there is some amount of space pre-allocated for attributes, but if you have a bigger number of attributes, then you definitely need to do this.
+If you see this error, the likelihood is that you have not allocated space for the number of attributes you are trying to use. Space must be allocated in the [[OBJD#Raw Data - Data Space|OBJD - Data Space]]. Eight attributes are preallocated by default, but if you need a bigger number than this, you will need to explicity define the quantity you require.
 ====130. '''Illegal primitive code'''====

@@ Line 188: / Line 188: @@
 ====7. '''Too many iterations'''====
-This occurs when a node in a BHAV is run more than 10,000 times.  It often occurs when a node is linked to itself, or in [[0x001F|Set To Next]] that are too broad(resulting in more than 10,000 items), or if you zero out the variable you using in [[0x001F|Set To Next]] prior to each call (resulting in the same item being found 10,000 times).  It can be fixed by using concise searches, and by making sure that no nodes make loops that will cause them to be run 10,000 times.
+This occurs when a node in a BHAV is run more than 10,000 times.  It often occurs when a node is linked to itself, or in [[0x001F|Set To Next]] that are too broad(resulting in more than 10,000 items), or if you zero out the variable you using in [[0x001F|Set To Next]] prior to each call (resulting in the same item being found 10,000 times).  In this case the error can be fixed by using concise searches, and by making sure that no nodes make loops that will cause them to be run 10,000 times.
 ====8. '''Undefined Transition'''====