Create account / Log in

Hiding information from both players

Suggestions for additional features for the module editor and Vassal engine.

Moderators: uckelman, Tim M

Hiding information from both players

Postby Brent Easton » July 25th, 2009, 8:03 am

The trouble with the Restricted Access trait is that (in my opinion) it is
TWO traits in one. It restricts all traits above it to the listed sides,
AND it restricts movement to the listed sides also. In my opinion, those
two traits should have been decoupled. Restricting movement is a reason
why I have never used the trait. I wish the Restricted Access trait had a
checkbox that allowed piece movement to be restricted or not. (On by
default for backward compatibility).

Sounds like a good idea. If I go down the Restricted Access route, it will be a major rewrite, so will be easy to add this in.

B.


_______________________________________________
Messages mailing list
Messages@forums.vassalengine.org
http://forums.vassalengine.org/mailman/ ... engine.org

Post generated using Mail2Forum (http://www.mail2forum.com)
User avatar
Brent Easton
 
Posts: 3198
Joined: December 21st, 2007, 3:06 am
Location: Berry, NSW, Australia

Re: Hiding information from both players

Postby shilinski » July 25th, 2009, 4:39 pm

Brent Easton wrote:
The trouble with the Restricted Access trait is that (in my opinion) it is
TWO traits in one. It restricts all traits above it to the listed sides,
AND it restricts movement to the listed sides also. In my opinion, those
two traits should have been decoupled. Restricting movement is a reason
why I have never used the trait. I wish the Restricted Access trait had a
checkbox that allowed piece movement to be restricted or not. (On by
default for backward compatibility).

Sounds like a good idea. If I go down the Restricted Access route, it will be a major rewrite, so will be easy to add this in.


A long, long time ago, I proposed that the moving aspect of Restricted Access be split off into a new trait called "Movable." The Movable trait would control how and who could move a piece plus some other ideas I can't imagine now. Currently, movement traits are scattered among other traits such as Restricted Access and Stacking (effectively making them compound traits). Alas, due to backward compatibility issues, it's probably no longer practical to put all movement controls under a Movable trait, but it certainly would be advantageous to do so in a framework such as Vassal (more tool flexibility).
shilinski
 
Posts: 170
Joined: December 22nd, 2007, 8:46 am
Location: Laurel, Maryland

Hiding information from both players

Postby Brent Easton » July 29th, 2009, 9:26 pm

As a module designer, I cannot build a scenario with masked pieces and
have the player grab control of the masked units when he chooses a side
(even if I resign the scenario before saving). It would be great for the
players if the s/w would work somehow as follows: A player choose a side
to play. The s/w loops through all masked pieces looking for those with a
specific property (side=British). The s/w loads the player's password into
the piece thereby giving the player ownership. (If things have changed
since I first explored the issue, then I don't know about it.)

Yes, you can do this already with no fancy work required.

In the Masked trait, set the 'Can be Masked by:' option to 'Any Side' instead of 'Any Player'. You can then take the british side and set up the British masked pieces, then retire from the British side. Any other player who now takes the british side will then automatically own those masked pieces.

The wording for this option is somewhat Obscure [:)], the reference manual help is much clearer, talking about who can 'own' the piece, not who can 'mask' it.

B.



_______________________________________________
Messages mailing list
Messages@forums.vassalengine.org
http://forums.vassalengine.org/mailman/ ... engine.org

Post generated using Mail2Forum (http://www.mail2forum.com)
User avatar
Brent Easton
 
Posts: 3198
Joined: December 21st, 2007, 3:06 am
Location: Berry, NSW, Australia

Postby soft-bug » July 31st, 2009, 8:16 am

Brent,

I'm curious about the new trait ... that you are preparing to us :wink:

I just put here a little "thought" ... to share with you an idea ....

Indeed, when you want to give the "right" to be seen to a dedicate player side ... you must first know .. which side is activated and secondly if the "right" is permanent or not..

If 4 sides are declared in a module :

Side 1
Side 2
Side 3
Side 4

If during play only Side 2 and 4 are taken .. then in term of design how to get flexibility... because impossible to predict this to manage the "actived sides" in a module.

Then , if during play you can declare "can be seen" by Actived side 2 or Side 4 ... for a piece, card, token ... you can put the "right" to the current sides requiered.

I have taken more then 2 sides, because for example in a card game ... during play a player gets the temporary "right" to see another player's hand ...


Very complex problem to resolve ... if you also take care about "automation" ...

Good luck !!

Regards,

Grégory
founder of The http://www.VassalFactory.org
User avatar
soft-bug
 
Posts: 222
Joined: December 20th, 2007, 9:30 am
Location: Paris / France

Previous

Return to Feature Requests

Who is online

Users browsing this forum: No registered users and 4 guests