Prohibit Pieces from Zones?

I’ve been wracking my brain trying to find a way to prohibit a piece, which must otherwise remain fully movable (whether by hand or some trait action), from being moved INTO a specific named zone. Can this be done. If so, how?

mac

I don’t know of anyway you could do that. You could have a way of triggering a layer on the piece, though …like having a big red X appear or something to tell players they’re not allowed to move there.

Pretty easy.

Give the piece a STL trait that will use the Send Back function (say CTRL B)
Also give it a Trigger Action - prop filter CurrentZone =
NameOfYourIllegalZone, keystroke Ctrl A executes CTRL B

Now in the map properties dialog box with the illegal zone, very last field
(keystroke to execute on pieces that move) CTRL A

That should do it

Post generated using Mail2Forum (mail2forum.com)

Very clever. I’ll keep that one in mind.

On Jun 12, 2010, at 7:01 AM, Dr_Nostromo wrote:

Yeah.

But the only drawback is that the effect could be a bit confusing for
the user, since there wouldn’t be any message posted to explain what
is happening. It is just that when you move a unit and release, it
moves back to where it came from. I’m assuming that at least the view
will move back to the location it ends up at.

The layer solution at least has the advantage of giving the user
feedback that this is a prohibited move. Perhaps one could couple the
move back with a report?


Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org

Post generated using Mail2Forum (mail2forum.com)

You can add a report trait which is uses the same key as the send back key or triggering key to make it obvious if necessary

From: Thomas Russ tar@isi.edu
To: VASSAL Engine Forums Mailing List messages@forums.vassalengine.org
Sent: Mon, June 14, 2010 1:40:00 PM
Subject: Re: [Module Design]Re: Prohibit Pieces from Zones?

On Jun 12, 2010, at 7:01 AM, Dr_Nostromo wrote:

Yeah.

But the only drawback is that the effect could be a bit confusing for the user, since there wouldn’t be any message posted to explain what is happening. It is just that when you move a unit and release, it moves back to where it came from. I’m assuming that at least the view will move back to the location it ends up at.

The layer solution at least has the advantage of giving the user feedback that this is a prohibited move. Perhaps one could couple the move back with a report?


Messages mailing list
Messages@forums.vassalengine.org (Messages@forums.vassalengine.org)
forums.vassalengine.org/mailman/ … engine.org

Post generated using Mail2Forum (mail2forum.com)

could even add a sound effect for illegal moves if one wanted if you were not aware to look at the chat window to see what is happening constantly

From: Timothy Mccarron timothy.mccarron@sbcglobal.net
To: VASSAL Engine Forums Mailing List messages@forums.vassalengine.org
Sent: Mon, June 14, 2010 3:11:10 PM
Subject: Re: [Module Design]Re: Prohibit Pieces from Zones?

You can add a report trait which is uses the same key as the send back key or triggering key to make it obvious if necessary

From: Thomas Russ tar@isi.edu
To: VASSAL Engine Forums Mailing List messages@forums.vassalengine.org
Sent: Mon, June 14, 2010 1:40:00 PM
Subject: Re: [Module Design]Re: Prohibit Pieces from Zones?

On Jun 12, 2010, at 7:01 AM, Dr_Nostromo wrote:

Yeah.

But the only drawback is that the effect could be a bit confusing for the user, since there wouldn’t be any message posted to explain what is happening. It is just that when you move a unit and release, it moves back to where it came from. I’m assuming that at least the view will move back to the location it ends up at.

The layer solution at least has the advantage of giving the user feedback that this is a prohibited move. Perhaps one could couple the move back with a report?


Messages mailing list
Messages@forums.vassalengine.org (Messages@forums.vassalengine.org)
forums.vassalengine.org/mailman/ … engine.org

Post generated using Mail2Forum (mail2forum.com)