> The first step has been to build an array usable within Vassal from
> a 12x17 board and a corresponding set of at-start stacks with game
> pieces representing results. (Much copy-pasting and find-replacing
> in buildfile.txt).
>
> etc.
Pushing the boundaries for sure, but sounds like it would work. I wouldn't
worry about having to add those extra pieces. The thing that really eats
memory in VASSAL are large images. If the pieces are really complicated
(>20 traits) you might notice an increase in game load time.
rk
[Non-text portions of this message have been removed]
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/vassalengine/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/vassalengine/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
