System gamearrays: Difference between revisions
Hendricks266 (talk | contribs) No edit summary |
Mblackwell (talk | contribs) mNo edit summary |
||
(2 intermediate revisions by 2 users not shown) | |||
Line 6: | Line 6: | ||
*[[sizex|tilesizx]][MAXTILES] | *[[sizex|tilesizx]][MAXTILES] | ||
*[[sizey|tilesizy]][MAXTILES] | *[[sizey|tilesizy]][MAXTILES] | ||
Sectors that are visible in 2d map mode: | |||
*[[show2dsector]][numsectors] | |||
Determine which [[statnum]]s will be in the loop for hitradius damage checks: | |||
* [[radiusdmgstatnums]][MAXSTATUS] | |||
Determine if a specific [[tilenum]] has been rendered this frame: | |||
* [[gotpic]][MAXTILES] | |||
Determine if a [[sector]] was rendered this frame: | |||
* [[gotsector]][numsectors] | |||
[[Category:Gamearray manipulation]] | [[Category:Gamearray manipulation]] |
Latest revision as of 20:36, 24 August 2024
These are gamearrays which are defined as direct pointers to internal arrays in the game. While some will change frequently, others will remain static for the whole game. Please note that the values of these array may be different on each peer, so be sure of what you are doing or you could possibly have an effect on sync.
The following is a listing of accessible arrays along with their size in brackets. Where the size is variable, it indicates the maximum allowable index plus 1. All of the built-in arrays are read-only.
The tilesiz(x/y) arrays are indexed by tile numbers and hold the x/y dimensions of the loaded tiles. If a tile doesn't exist, they will be 0.
Sectors that are visible in 2d map mode:
- show2dsector[numsectors]
Determine which statnums will be in the loop for hitradius damage checks:
- radiusdmgstatnums[MAXSTATUS]
Determine if a specific tilenum has been rendered this frame:
- gotpic[MAXTILES]
Determine if a sector was rendered this frame:
- gotsector[numsectors]