# Possible Vassal bug causing extra GKC execution after Send To (Zone) Location

**URL:** <https://forum.vassalengine.org/t/possible-vassal-bug-causing-extra-gkc-execution-after-send-to-zone-location/79821>\
**Category:** Technical Support & Bugs\
**Created:** [June 17, 2024, 7:38pm UTC](https://forum.vassalengine.org/t/possible-vassal-bug-causing-extra-gkc-execution-after-send-to-zone-location/79821 "2024-06-17T19:38:09Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![marktb1961](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/marktb1961/32/231_2.png) [@marktb1961](https://forum.vassalengine.org/u/marktb1961)\
**Post date:** [June 18, 2024, 11:16pm UTC](https://forum.vassalengine.org/t/possible-vassal-bug-causing-extra-gkc-execution-after-send-to-zone-location/79821/7 "2024-06-18T23:16:03Z")

</div>

I agree that stacking can cause these kind of issues. I encountered a very similar-sounding problem a while ago, that I described in [this post](https://forum.vassalengine.org/t/automated-movement-onto-a-stack-send-to-location-working-through-a-double-action-problem/72825).

Update: I can see from @Brent_Easton’s explanation below that I must have been working around the same bug, without exposing the root cause with sufficient clarity at that time.

---

_[View the full topic](https://forum.vassalengine.org/t/possible-vassal-bug-causing-extra-gkc-execution-after-send-to-zone-location/79821)._