# Bad behavior in activating layers in 3.2.3

**URL:** https://forum.vassalengine.org/t/bad-behavior-in-activating-layers-in-3-2-3/5870
**Category:** Technical Support & Bugs
**Created:** [March 31, 2013, 3:18pm UTC](https://forum.vassalengine.org/t/bad-behavior-in-activating-layers-in-3-2-3/5870 "2013-03-31T15:18:15Z")
**Posts on this page:** 1
**Showing post:** 1

<div class="post-metadata">

### Author: ![maramonster](https://forum.vassalengine.org/letter_avatar_proxy/v4/letter/m/c2a13f/32.png) [@maramonster](https://forum.vassalengine.org/u/maramonster)
#### Post date: [March 31, 2013, 3:18pm UTC](https://forum.vassalengine.org/t/bad-behavior-in-activating-layers-in-3-2-3/5870/1 "2013-03-31T15:18:15Z")

</div>

Hello,

I found an issue with every build of 3.2.3 from 8566 up to 8616. if you make a layer with one image and an activate keystroke, it requires two keypresses to activate it the first time. I think it’s setting an invalid initial state, and then toggling it off on the first key press before toggling it on the second.

I’ve shown this to uckleman and he wants verification that it’s not a bug in my module. I have the simple module i created to illustrate this bug here: [http://studiospryte.com/uploads/brokenbuffclean.vmod](http://studiospryte.com/uploads/brokenbuffclean.vmod).

if you wish to replicate it yourself in your own module, the settings are here:

![](http://studiospryte.com/uploads/buffsettings.png)

---

_[View the full topic](https://forum.vassalengine.org/t/bad-behavior-in-activating-layers-in-3-2-3/5870)._