Picnum: Difference between revisions
Jump to navigation
Jump to search
m Categories |
Hendricks266 (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
picnum is the | A '''picnum''', short for "picture number", also referred to as '''tilenum''', short for "tile number", is the index of any piece of art in the game. In CON coding, since [[actor]] types are defined by tile number, the picnum of a sprite determines the code that will be executed on it. For example, any sprite that is given a picnum of 2000 in the code or in a map is thereby a PIGCOP (because the label 'PIGCOP' is defined as 2000) and will then execute the associated code. | ||
In the code of a specific [[actor]] type, the picnum of the sprite executing the code is already known. But in certain events, such as [[EVENT_GAME]], different actor types will execute the same [[onevent]] code, so getting the value of picnum can be very useful. | In the code of a specific [[actor]] type, the picnum of the sprite executing the code is already known. But in certain events, such as [[EVENT_GAME]], different actor types will execute the same [[onevent]] code, so getting the value of picnum can be very useful. | ||
Revision as of 21:32, 7 January 2011
A picnum, short for "picture number", also referred to as tilenum, short for "tile number", is the index of any piece of art in the game. In CON coding, since actor types are defined by tile number, the picnum of a sprite determines the code that will be executed on it. For example, any sprite that is given a picnum of 2000 in the code or in a map is thereby a PIGCOP (because the label 'PIGCOP' is defined as 2000) and will then execute the associated code.
In the code of a specific actor type, the picnum of the sprite executing the code is already known. But in certain events, such as EVENT_GAME, different actor types will execute the same onevent code, so getting the value of picnum can be very useful.