Difference between revisions of "User:DavidJCobb/Stack dumping"
m
→Overview
imported>DavidJCobb m (→Overview) |
imported>DavidJCobb m (→Overview) |
||
| Line 13: | Line 13: | ||
<pre>Suspended stack count is over our warning threshold, dumping stacks:</pre> | <pre>Suspended stack count is over our warning threshold, dumping stacks:</pre> | ||
This means that if a mod has a problem that leads to stack dumping, that mod will interfere with itself, with other mods, and with Bethesda-authored scripts (because Papyrus doesn't care where the problem is coming from; it'll dump as many stacks as it can, indiscriminately, until it feels safe). The problem will have unpredictable consequences, which may or may not break other content or otherwise lead to save corruption. As a modder, the best approach to take here is the maximally cautious one, because even if a stack dumping issue doesn't wreck ''your'' savegame, it could wreck someone else's. | This means that if a mod has a problem that leads to stack dumping, that mod will interfere with itself, with other mods, and with Bethesda-authored scripts (because Papyrus doesn't care where the problem is coming from; it'll dump as many stacks as it can, indiscriminately, until it feels safe). The problem will have unpredictable consequences, which may or may not break other content or otherwise lead to save corruption. As a modder, the best approach to take here is the maximally cautious one, because even if a stack dumping issue doesn't wreck ''your'' savegame, it could wreck someone else's. If your mod has a flaw that leads to stack dumping, fixing that needs to be a high priority. | ||
== Specific methods to minimize stack dumping == | == Specific methods to minimize stack dumping == | ||