# Map Window Size - bugs

**URL:** <https://forum.vassalengine.org/t/map-window-size-bugs/90692>\
**Category:** Technical Support & Bugs\
**Created:** [November 15, 2026, 4:02pm UTC](https://forum.vassalengine.org/t/map-window-size-bugs/90692 "2026-11-15T16:02:11Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Korval](https://forum.vassalengine.org/letter_avatar_proxy/v4/letter/k/ecc23a/32.png) [@Korval](https://forum.vassalengine.org/u/Korval)\
**Post date:** [November 15, 2026, 4:02pm UTC](https://forum.vassalengine.org/t/map-window-size-bugs/90692/1 "2026-11-15T16:02:11Z")

</div>

I have just noticed the following bug/issues w/ Map Windows.

I have defined a secondary Group map window size as 500 x 500 and an associated Multi-Zone Grid with a _single_ zone for the entirety of the map window (500 x 500).

My goal being to ensure that if a piece is dragged to/from the main map to the Group Map, the chat log properly reports the movement.

I have encountered the following bugs:

1. It is possible to resize the secondary map window to larger than the defined window size (i.e., bigger than 500 x 500).

2. After resizing the window to larger than the defined size, chat log reporting is inconsistent when dragging to/from outside the zone definition. Sometimes it reports the zone name and sometimes it says “offboard.”

Desired behavior - if a map window is defined as a certain size, the user should not be able to expand the window to larger than the defined size.
