3.2 builds

Development
161

Sorry for lurking, but would it be “safe” in terms of compatibility to take the latest build of 3.2 and to start designing a module for it?

Would I just have issues later down the road when a final release is done?

At what point do you think it would be safe to start designing in 3.2?

Thanks, Vassal is an amazing piece of software.

162

Thus spake chrono280:

Sorry for lurking, but would it be “safe” in terms of compatibility to
take the latest build of 3.2 and to start designing a module for it?

Would I just have issues later down the road when a final release is
done?

At what point do you think it would be safe to start designing in 3.2?

I expect that the 3.2.0 release will be substantially as the 3.2 builds
are now, modulo bug fixes. As long as you’re not relying on behavior
caused by bugs, you should be fine.

–
J.

163

That’s great news, thanks! I don’t suppose there’s any documentation yet that I could crawl through?

164

Thus spake chrono280:

That’s great news, thanks! I don’t suppose there’s any documentation
yet that I could crawl through?

Most of the new features are undocumented, unfortunately.

–
J.

165

You can at least look at:
vassalengine.svn.sourceforge.net … iew=markup

166

Great!

Any resources on learning BeanShell stuff to recommend while we’re at it? :smiley:

I know a tiny tiny bit of Java and Javascript…Thanks again