> I don't understand why you have to Replace the counter with another one
> and use Restrict Access, rather than just having the Restrict Commands
> trait depend on dynamic or system markers.
>
> Perhaps I don't understabnd what you are trying to do?
My goal is to take a counter, interact wiith it, move it, rotate it, and
then after I'm satisfied with its location/state render it unmovable and
turn off almost every command it has (all but a "Move Fixed DIstance"
command).
I can easily use the Restrict Commands trait to disable all the commands,
but I also want to make it unmoveable. The two ways I am aware to make
the counter unmoveable are:
1. Use "Does not stack" with "Move" set to "Never"
2. Use "Restrict Access" and make the counter belong to a side that does
not exist.
How would you suggest accomplishing the goal? I hope its some simple
solution that I've overlooked.
I guess one thing I haven't tried yet, is doing the piece-swap thing with
a new piece that has "Restrict Commands" and "Does not stack", instead of
"Restrict Access" (at least I don't remember trying that). I'll have to
see what that yields.
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/vassalengine/
<*> 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/
