|
5 | 5 | 1. Loaded as part of BlockMap. |
6 | 6 | 2. Split into 10x10 chunk |
7 | 7 | 3. When the character enters into ActivateScope, they get activated |
8 | | - - This check only happes for the characters in the chunks that overlaps with the ActivateScope. |
9 | | - - This check happens every 16 frames. |
10 | | - - However if the character is already in ViewScope, then they don't get activated (This happens when a character moves far away from its spawn point, and leaves ActivateScope while the spawn point is inside ViewScope) |
11 | | - - However this rule doesn't apply when the main character warped to somewhere, or first appear in the screen |
| 8 | + |
| 9 | +- This check only happes for the characters in the chunks that overlaps with the |
| 10 | + ActivateScope. |
| 11 | +- This check happens every 16 frames. |
| 12 | +- However if the character is already in ViewScope, then they don't get |
| 13 | + activated (This happens when a character moves far away from its spawn point, |
| 14 | + and leaves ActivateScope while the spawn point is inside ViewScope) |
| 15 | + - However this rule doesn't apply when the main character warped to somewhere, |
| 16 | + or first appear in the screen |
| 17 | + |
12 | 18 | 4. Activated characters are updated each frame. (by calling .step() function) |
13 | | -5. When an activated character leaves ActivateScope, then they go back to inactive state. Go back to step 3. |
14 | | - - This check happens every 60 frames. |
| 19 | +5. When an activated character leaves ActivateScope, then they go back to |
| 20 | + inactive state. Go back to step 3. |
| 21 | + |
| 22 | +- This check happens every 60 frames. |
15 | 23 |
|
16 | 24 | # The lifecycle of the items |
17 | 25 |
|
18 | 26 | ... |
19 | | - |
|
0 commit comments