# Release candidate for 3.2.0-beta1 **URL:** \ **Category:** Development\ **Created:** [May 23, 2012, 9:32pm UTC](https://forum.vassalengine.org/t/release-candidate-for-3-2-0-beta1/4947 "2012-05-23T21:32:26Z")\ **Posts on this page:** 10\ **Page:** 3
**Author:** ![Rindis](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/rindis/32/14_2.png) [@Rindis](https://forum.vassalengine.org/u/Rindis)\ **Post date:** [August 1, 2012, 5:38am UTC](https://forum.vassalengine.org/t/release-candidate-for-3-2-0-beta1/4947/41 "2012-08-01T05:38:37Z")
> [@uckelman](#): > > But, I see the same thing with your module and 3.1.20-svn8251, which > makes me think this is either an old problem, or is a problem with the > module. Interesting. I built the module in 3.2-beta, so 3.1.20 refuses to try to load that module on my machine. (‘Module too new’) ---
**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:** [August 1, 2012, 9:21am UTC](https://forum.vassalengine.org/t/release-candidate-for-3-2-0-beta1/4947/42 "2012-08-01T09:21:03Z")
Thus spake Rindis: > “uckelman” wrote: > > > But, I see the same thing with your module and 3.1.20-svn8251, which > > makes me think this is either an old problem, or is a problem with the > > module. > > Interesting. I built the module in 3.2-beta, so 3.1.20 refuses to try to > load that module on my machine. (‘Module too new’) This is not something you can normally do. I hand-edited the VASSAL version listed in the buildFile and module metadata to get around it. – J. ---
**Author:** ![Rindis](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/rindis/32/14_2.png) [@Rindis](https://forum.vassalengine.org/u/Rindis)\ **Post date:** [August 4, 2012, 11:34pm UTC](https://forum.vassalengine.org/t/release-candidate-for-3-2-0-beta1/4947/43 "2012-08-04T23:34:57Z")
> [@uckelman](#): > > Yes, something isn’t quite right here. When I turn on hex grid drawing, > the centers look dead-on, so it’s not the hex grid that’s misalligned. > > But, I see the same thing with your module and 3.1.20-svn8251, which > makes me think this is either an old problem, or is a problem with the > module. > > – > J. I just did a couple quick-and-dirty recreations of the module with the map and grid (twice, once in 3.1.19 and once in 3.2-8249), and they both have the same off-centeredness. So it seems to be the code, not the module itself. ---
**Author:** ![Flaney](https://forum.vassalengine.org/letter_avatar_proxy/v4/letter/f/3be4f8/32.png) [@Flaney](https://forum.vassalengine.org/u/Flaney)\ **Post date:** [August 5, 2012, 7:50am UTC](https://forum.vassalengine.org/t/release-candidate-for-3-2-0-beta1/4947/44 "2012-08-05T07:50:06Z")
> [@Rindis](#): > > > [@uckelman](#): > > > > But, I see the same thing with your module and 3.1.20-svn8251, which > > makes me think this is either an old problem, or is a problem with the > > module. > > Interesting. I built the module in 3.2-beta, so 3.1.20 refuses to try to load that module on my machine. (‘Module too new’) I didn’t think 3.1.20 was forward compatible with 3.2.0 Fooled me once thinking the 3.1.20 was a 3.2.0 release update 🙂 ---
**Author:** ![Brent\_Easton](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/brent_easton/32/10_2.png) [@Brent\_Easton](https://forum.vassalengine.org/u/Brent_Easton)\ **Post date:** [August 11, 2012, 11:05pm UTC](https://forum.vassalengine.org/t/release-candidate-for-3-2-0-beta1/4947/45 "2012-08-11T23:05:33Z")
> [@](#): > > Or does synchronization really take > nanoseconds and the slownes mentioned above is just the normal game starting > slowness for bulky modules (like MH)? Yep, that’s it. Any commands executed by another client while the post-synchronization load up is completing will be queued up and executed in order as expected. ---
**Author:** ![bdgza](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/bdgza/32/6764_2.png) [@bdgza](https://forum.vassalengine.org/u/bdgza)\ **Post date:** [August 26, 2012, 11:42am UTC](https://forum.vassalengine.org/t/release-candidate-for-3-2-0-beta1/4947/46 "2012-08-26T11:42:27Z")
I feel bad I didn’t think of this sooner, but I is it too late to hash the user passwords for 3.2? 3.2 is not backward compatible with 3.1.x anyway and the PLAYER entry already changed format, so it would be a great opportunity to change from cleartext to a simple hash like SHA1. Not that that can’t be broken but it makes it a little more difficult to find the user password than cleartext. Since you compare one with the other, comparing cleartext to cleartext is no different from comparing hashed to hashed. Only thing that would have to change is writing a hashed password to the prefs instead of clear when changing prefs for a module. ---
**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:** [August 26, 2012, 6:01pm UTC](https://forum.vassalengine.org/t/release-candidate-for-3-2-0-beta1/4947/47 "2012-08-26T18:01:58Z")
Thus spake bdgza: > I feel bad I didn’t think of this sooner, but I is it too late to hash > the user passwords for 3.2? 3.2 is not backward compatible with 3.1.x > anyway This is not the case. Most everything which worked with 3.1 should still work with 3.2, with only a few exceptions. This is exactly why we can’t change the password mechanism in 3.2, it it would break that. We will rectify the situation with passwords in V4. – J. ---
**Author:** ![bdgza](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/bdgza/32/6764_2.png) [@bdgza](https://forum.vassalengine.org/u/bdgza)\ **Post date:** [August 27, 2012, 7:14am UTC](https://forum.vassalengine.org/t/release-candidate-for-3-2-0-beta1/4947/48 "2012-08-27T07:14:17Z")
The password format stored in 3.2 is already different from 3.1 since it adds an extra fields with a “;”, so it’s easy to detect if it’d be a classic password-only-in-cleartext or a multi-password-field-in-hashed. So ok, my statement that only 1 place needs to be changed is not true, it would be slightly more work and would only be doable depending on in how many places you read the password (which should be one). But it would still be compatible with loading 3.1 files, just not loading 3.2-beta1 files. > [@uckelman](#): > > Thus spake bdgza: > > > I feel bad I didn’t think of this sooner, but I is it too late to hash > > the user passwords for 3.2? 3.2 is not backward compatible with 3.1.x > > anyway > > This is not the case. Most everything which worked with 3.1 should still > work with 3.2, with only a few exceptions. This is exactly why we can’t > change the password mechanism in 3.2, it it would break that. > > We will rectify the situation with passwords in V4. > > – > J. ---
**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:** [October 11, 2012, 1:17pm UTC](https://forum.vassalengine.org/t/release-candidate-for-3-2-0-beta1/4947/49 "2012-10-11T13:17:08Z")
Thus spake Rindis: > “uckelman” wrote: > > > Yes, something isn’t quite right here. When I turn on hex grid > > drawing, > > the centers look dead-on, so it’s not the hex grid that’s misalligned. > > > > But, I see the same thing with your module and 3.1.20-svn8251, which > > makes me think this is either an old problem, or is a problem with the > > module. > > > > – > > J. > > I just did a couple quick-and-dirty recreations of the module with the > map and grid (twice, once in 3.1.19 and once in 3.2-8249), and they both > have the same off-centeredness. So it _seems_ to be the code, not the > module itself. ## Does this still happen with 3.2.0-beta4? If so, please file a bug report with instructions for reproducing the problem. J. ---
**Author:** ![Rindis](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/rindis/32/14_2.png) [@Rindis](https://forum.vassalengine.org/u/Rindis)\ **Post date:** [October 13, 2012, 6:10pm UTC](https://forum.vassalengine.org/t/release-candidate-for-3-2-0-beta1/4947/50 "2012-10-13T18:10:27Z")
Still there: [vassalengine.org/tracker/sho … gi?id=9400](http://www.vassalengine.org/tracker/show_bug.cgi?id=9400) [Previous page](https://forum.vassalengine.org/t/release-candidate-for-3-2-0-beta1/4947.md?page=2)