# Problem with new behavior of resize-world **URL:** \ **Category:** Bug Reports\ **Tags:** github, docs\ **Created:** [May 8, 2026, 9:56am UTC](https://forum.netlogo.org/t/problem-with-new-behavior-of-resize-world/822 "2026-05-08T09:56:20Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![mrkramer\_wageningen](https://forum.netlogo.org/letter_avatar_proxy/v4/letter/m/f4b2a3/32.png) [@mrkramer\_wageningen](https://forum.netlogo.org/u/mrkramer_wageningen)\ **Post date:** [May 8, 2026, 9:56am UTC](https://forum.netlogo.org/t/problem-with-new-behavior-of-resize-world/822/1 "2026-05-08T09:56:21Z")
With the new release (7.0.4) of NetLogo, many problems have been solved. It’s an impressive list! However, I was surprised by the phrase “resize-world was not resetting the tick counter”. This looks like this was a bug, but the documentation of `resize-world` has never said that it resets the tick counter. Moreover, the [issue on github](https://github.com/NetLogo/NetLogo/issues/2636) about `resize-world` seems to indicate that this was _not_ considered a bug after all. So, why (potentially) break existing NetLogo code? Anyway, if this behavior is here to stay, please update the documentation accordingly. ---
**Author:** ![Jason](https://forum.netlogo.org/user_avatar/forum.netlogo.org/jason/32/209_2.png) [@Jason](https://forum.netlogo.org/u/Jason)\ **Post date:** [May 8, 2026, 2:38pm UTC](https://forum.netlogo.org/t/problem-with-new-behavior-of-resize-world/822/2 "2026-05-08T14:38:12Z")
You’re right that we should update the documentation on this. To clarify, the root issue being addressed by this change was reported in [this ticket](https://github.com/NetLogo/NetLogo/issues/108). Resizing the world already blanks the model state. Due to that, the typical “go” button in the typical model should become deactivated by the `resize-world` call, because “go” buttons that are disabled until ticks start are expecting a populated world state. But, in older versions of NetLogo, you can see this behaving in the opposite and unintuitive way by changing the world width of a model, mid-run: the world goes blank, and the “go” button remains clickable. But clicking it achieves nothing (if not generates errors). The issue that you linked (#2636) highlighted a disagreement between @ERSUCC and myself on how this sort of thing should be conceptualized. I don’t agree that resizing the world should halt all buttons immediately, but I think he’s right to think it should stop the repetition of the typical “go” button. And, in fact, it appears that our fix to ticket #108 actually _does_ stop the errant “go” button now. Consequently, I’d say that we addressed the core issue that Isaac raised in #2636, and I’ve closed it. ---
**Author:** ![mrkramer\_wageningen](https://forum.netlogo.org/letter_avatar_proxy/v4/letter/m/f4b2a3/32.png) [@mrkramer\_wageningen](https://forum.netlogo.org/u/mrkramer_wageningen)\ **Post date:** [May 9, 2026, 2:33pm UTC](https://forum.netlogo.org/t/problem-with-new-behavior-of-resize-world/822/3 "2026-05-09T14:33:49Z")
Hi Jason, Thank you for this further background information. I would expect there are other solutions to the original problem. It seems strange to stop a forever button by clearing the tick counter. For breaking existing code, I don’t expect too many problems. One of my test models did `tick` after`resize-world` in the same procedure, but I could repair that one easily. In the Models Library, I found four models with potentially dangerous use of `resize-world`, but I was not able to cause a runtime error there. So, I accept the change to the behavior of `resize-world` and I appreciate that you update the documentation. ---
**Author:** ![ERSUCC](https://forum.netlogo.org/letter_avatar_proxy/v4/letter/e/bbe5ce/32.png) [@ERSUCC](https://forum.netlogo.org/u/ERSUCC)\ **Post date:** [August 31, 2026, 5:18pm UTC](https://forum.netlogo.org/t/problem-with-new-behavior-of-resize-world/822/4 "2026-08-31T17:18:12Z")
Hi Mark, The documentation for `resize-world` has already been updated to reflect this new behavior. Let us know if it’s still unclear or if you have any remaining issues with the behavior. Isaac B. ---
**Author:** ![mrkramer\_wageningen](https://forum.netlogo.org/letter_avatar_proxy/v4/letter/m/f4b2a3/32.png) [@mrkramer\_wageningen](https://forum.netlogo.org/u/mrkramer_wageningen)\ **Post date:** [September 2, 2026, 9:34am UTC](https://forum.netlogo.org/t/problem-with-new-behavior-of-resize-world/822/5 "2026-09-02T09:34:45Z")
Could you please add a separate paragraph stating that any running “forever” buttons are stopped? And then it is important if this is “immediately” or “after the current iteration of the button”. (There are issues with both choices. Either the state is undefined due to concurrency, or the button might never stop anymore.) ---
**Author:** ![ERSUCC](https://forum.netlogo.org/letter_avatar_proxy/v4/letter/e/bbe5ce/32.png) [@ERSUCC](https://forum.netlogo.org/u/ERSUCC)\ **Post date:** [September 2, 2026, 11:08pm UTC](https://forum.netlogo.org/t/problem-with-new-behavior-of-resize-world/822/6 "2026-09-02T23:08:05Z")
I think this is a bug. The intended (and now documented) behavior is that `resize-world` will stop any forever buttons that are marked with “Disable until ticks start”, but any other forever buttons should continue to run. We’ll look into it and see if it’s something that needs to be fixed for the next release. ---
**Author:** ![mrkramer\_wageningen](https://forum.netlogo.org/letter_avatar_proxy/v4/letter/m/f4b2a3/32.png) [@mrkramer\_wageningen](https://forum.netlogo.org/u/mrkramer_wageningen)\ **Post date:** [September 3, 2026, 6:32am UTC](https://forum.netlogo.org/t/problem-with-new-behavior-of-resize-world/822/7 "2026-09-03T06:32:56Z")
My error. I was aware of this additional condition, but forgot about it when typing the message. In the 7.1 preview documentation, I did not yet find the text about stopping any buttons. A link to `clear-ticks` might be useful as well. It might even be clearer if `resize-world` refers to `clear-ticks` for further details, and the text about which buttons are stopped and when is with `clear-ticks`. Then it is in one place, with all necessary details.