# Development plan, 2026-06-02

**URL:** <https://forum.vassalengine.org/t/development-plan-2026-06-02/90188>\
**Category:** Development\
**Created:** [June 2, 2026, 7:54pm UTC](https://forum.vassalengine.org/t/development-plan-2026-06-02/90188 "2026-06-02T19:54:35Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![uckelman](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/uckelman/32/10020_2.png) [@uckelman](https://forum.vassalengine.org/u/uckelman)\
**Post date:** [June 2, 2026, 7:54pm UTC](https://forum.vassalengine.org/t/development-plan-2026-06-02/90188/1 "2026-06-02T19:54:35Z")

</div>

Development report for 2 June 2026:

🎉 I am now devoting my development time to V4 tech demos. 🎉

### V4 Demo

The initial demo is nearly complete:

Review initial demo work from May 2025  
 Load maps, pieces from a file  
 Load individual images  
 Crop images  
 Slice images  
 Position maps, grids with anchors  
 Click select pieces  
 Lasso select pieces  
 Drag pieces  
 Pan view  
 Zoom view  
 Rotate view  
 Hex grids  
 Square grids  
 Snap to grid  
 Undo/Redo  
 Logging

## Next up

April and May were not as conducive to progress as I’d hoped. I switched jobs at the end of April and was away at a conference (Rust Week 2026) in May, which left little time for much else.

### V4 Demo

Piece stacking  
 Demo write-up/presentation

### Maintenance

Review PRs for 3.7.23  
 Release 3.7.23  
 Upgrade server

## Near-term forecast

Once the above V4 Demo tasks are complete, I intend to publish the demo for public comment.

It may be several months before I return to any game library issues. If there are module library issues you want addressed sooner, please consider volunteering to help with them.

Game library Issues may be found in the [issue tracker](https://github.com/vassalengine/game-library/issues). Most of them are underdescribed at the moment, so the first step would be asking for a better description. Especially for the frontend issues, we could use pointers to examples of good design.

---

<div class="post-metadata">

**Author:** ![Romulus](https://forum.vassalengine.org/letter_avatar_proxy/v4/letter/r/839c29/32.png) [@Romulus](https://forum.vassalengine.org/u/Romulus)\
**Post date:** [June 8, 2026, 11:11pm UTC](https://forum.vassalengine.org/t/development-plan-2026-06-02/90188/2 "2026-06-08T23:11:45Z")

</div>

Hello @uckelman !

I just discovered the Vassal project and am excited about your work. Coincidentally, I was prototyping my own board game engine born out of needs from the Kriegsspiel community.

I noticed in screenshots from your previous dev logs that you are using the Bevy engine to create your v4 demo. I had started my own prototype using Bevy but ended up choosing Macroquad for ease of use and because I wanted to build most of the engine myself. But for Vassal’s requirements, I think that Bevy is a fantastic choice.

After you release the v4 demo, will there be any contribution opportunities to a v4 alpha? Glad to have caught you early in your development because I would love to follow along and help out in the future if possible.

---

<div class="post-metadata">

**Author:** ![uckelman](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/uckelman/32/10020_2.png) [@uckelman](https://forum.vassalengine.org/u/uckelman)\
**Post date:** [June 9, 2026, 10:46pm UTC](https://forum.vassalengine.org/t/development-plan-2026-06-02/90188/3 "2026-06-09T22:46:46Z")

</div>

> [@Romulus](#):
>
> But for Vassal’s requirements, I think that Bevy is a fantastic choice.

I’m quite happy with Bevy thus far. It’s nice to use and has a friendly, active community around it.

> [@Romulus](#):
>
> After you release the v4 demo, will there be any contribution opportunities to a v4 alpha?

Yes, and it would be lovely to have help. There’s still some work to do prior to that point, but watch this space.