Difference between revisions of "Talk:OnCellDetach - ObjectReference"
Jump to navigation
Jump to search
imported>Rasikko (Created page with "== Attachment and Detachment == * For exteriors, cell attachment/detachment means the cells which load around the player. Default is 5x5 cells. Any cell that becomes no longer...") |
imported>Rasikko |
||
| Line 1: | Line 1: | ||
== Attachment and Detachment == | == Attachment and Detachment == | ||
* For exteriors, cell attachment/detachment means the cells which load around the player. Default is 5x5 cells. Any cell that becomes no longer part of this grid of cells is detached. For interiors, it's the cell you enter(attached) and exit(detached). Now that's cleared up, on to my real issue. This may only happen when using the COC command to leave cells as you can't normally fast travel out of dungeons, but I'll put this here anyway - if you leave a cell and into a new one too quickly, there's a chance this event will fire '''for the destination cell''' as if the engine thinks THAT cell is the one that became | * For exteriors, cell attachment/detachment means the cells which load around the player. Default is 5x5 cells. Any cell that becomes no longer part of this grid of cells is detached. For interiors, it's the cell you enter(attached) and exit(detached). Now that's cleared up, on to my real issue. This may only happen when using the COC command to leave cells as you can't normally fast travel out of dungeons, but I'll put this here anyway - if you leave a cell and into a new one too quickly, there's a chance this event will fire '''for the destination cell''' as if the engine thinks THAT cell is the one that became detached. That can be troublesome if you're using this event to track some kind of data of a ref from the previous cell upon leaving as it will instead look at data for a ref in the new cell. --[[User:Rasikko|Rasikko]] ([[User talk:Rasikko|talk]]) 2021-10-12T13:43:22 (EDT) | ||
Revision as of 12:45, 12 October 2021
Attachment and Detachment
- For exteriors, cell attachment/detachment means the cells which load around the player. Default is 5x5 cells. Any cell that becomes no longer part of this grid of cells is detached. For interiors, it's the cell you enter(attached) and exit(detached). Now that's cleared up, on to my real issue. This may only happen when using the COC command to leave cells as you can't normally fast travel out of dungeons, but I'll put this here anyway - if you leave a cell and into a new one too quickly, there's a chance this event will fire for the destination cell as if the engine thinks THAT cell is the one that became detached. That can be troublesome if you're using this event to track some kind of data of a ref from the previous cell upon leaving as it will instead look at data for a ref in the new cell. --Rasikko (talk) 2021-10-12T13:43:22 (EDT)