legacy:grid:api
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| legacy:grid:api [2025/01/13 16:14] – ↷ Page moved from grid:api to legacy:grid:api superadmin | legacy:grid:api [2025/01/13 16:14] (current) – ↷ Links adapted because of a move operation superadmin | ||
|---|---|---|---|
| Line 15: | Line 15: | ||
| When you decide the dimension of the grid, the maximum index is changed accordingly. i.e, if you put the dimension as '' | When you decide the dimension of the grid, the maximum index is changed accordingly. i.e, if you put the dimension as '' | ||
| - | Because the position is stored in a one-dimension array, so does the battler position. To determine the position, you have to make a nested array that represents the screen position of that said index. For example, this is the position setting in the 640x360 screen in [[grid: | + | Because the position is stored in a one-dimension array, so does the battler position. To determine the position, you have to make a nested array that represents the screen position of that said index. For example, this is the position setting in the 640x360 screen in [[legacy:grid: |
| <code ruby> | <code ruby> | ||
| Position = | Position = | ||
| Line 29: | Line 29: | ||
| ===== Getting Position ===== | ===== Getting Position ===== | ||
| - | Getting the position is largely used in the [[grid: | + | Getting the position is largely used in the [[legacy:grid: |
| ==== Neighbor direction ==== | ==== Neighbor direction ==== | ||
| Line 127: | Line 127: | ||
| return result | return result | ||
| </ | </ | ||
| - | It will yield an array with the value as '' | + | It will yield an array with the value as '' |
| ===== Other Functions ===== | ===== Other Functions ===== | ||
legacy/grid/api.1736784873.txt.gz · Last modified: 2025/01/13 16:14 by superadmin
