Page history
21 March 2017
14 March 2015
2 March 2015
→Code snippets
m+24
→Code snippets
m+340
→Process a task OnHit, without outright discarding concurrent calls
m+43
→Process a task OnHit, and wait for X seconds during or after the task: wording
m+96
→Process a task OnHit, without outright discarding concurrent calls: wording
m+28
→Process a task OnHit, and wait for X seconds during or after the task
+258
→Process a task OnHit, without outright discarding concurrent calls: fixed some more
m+3
→Process a task OnHit, without outright discarding concurrent calls: fixed
+234
no edit summary
m+20
→Process a task OnHit, without outright discarding concurrent calls
m+55
→Code snippets: combined two functionally-identical snippets
m−820
→Code snippets: More snippets, and explanations for all snippets.
+3,115
→Specific methods to minimize stack dumping
m+244
→Specific methods to minimize stack dumping
m+387
→Events that can trigger large numbers of suspended stacks
m+49
→Process a task OnHit, and don't re-process for X seconds
m+79
code snippet for BF
−101
→Events that can trigger large numbers of suspended stacks: OnHit's concurrency has been experimentally verified. Item events' consecutive...ness... has not.
m+312
→Specific methods to minimize stack dumping
m+27
CONFIRMED: RegisterForSingleUpdate(x) creates a new stack in x seconds, rather than creating a new stack immediately and suspending it for x seconds. Important distinction, that.
m+287
→How do update events work?
m+86
→Specific methods to minimize stack dumping
m+321
→Overview
m+93
→Overview
m+140
Created page with "'''Stack dumping''' is a Papyrus event that can cause unpredictable and potentially severe errors in a player's savegame. My understanding of the phenomenon is as follows: ==..."
+5,633