Invisibility also needs to be silent, not * ? moves ? -> ? *

I’m tossing together a simple module and one side has the option to hide units. Giving their side’s main prototype the Invisibility option and restricting it to that side works perfectly, as it should.

But moving a hidden unit toss this into the log:

  • ? moves ? → ? *

when in the game the rules do not require you to disclose whether you’re moving hidden units or not. In fact, they actively encourage you to BS this part of your turn to throw off your opponent.

How can I silence these log messages?

Is the reporting being generated by the Map itself? You could try replacnign the automated reporting of moves for all pieces, generated by the Map, with customized move reporting from a low-level Prototype which first tests for invisibility.

Yes.

Thinking about it more, the best solution would be just to silence location reporting altogether, as that’s not necessary for play.

How would I go about doing that?

That might interfere with the Log-File; I haven’t tried it myself.

Just clear the appropriate Message-format Report field in the appropriate
component, the Map in this case, and no text will be generated.

Pieter Geerkens B.Sc., CGA
pgeerkens@hotmail.com

-----Original Message-----
From: messages-bounces@vassalengine.org
[mailto:messages-bounces@vassalengine.org] On Behalf Of Shad
Sent: Saturday, January 08, 2011 7:14 PM
To: messages@vassalengine.org
Subject: [messages] [Module Design] Re: Invisibility also needs to be
silent,not * ? moves ? → ? *

“pgeerkens” wrote:

Is the reporting being generated by the Map itself?

Yes.

Thinking about it more, the best solution would be just to silence
location reporting altogether, as that’s not necessary for play.

How would I go about doing that?


Read this topic online here:
https://forum.vassalengine.org/t/invisibility-also-needs-to-be-silent-not-moves/3555/3

Thanks, I’ve got several boards in this module and was looking there for options rather than at the Main Map level. All’s silent now.

And this module is still in testing, so no worries about log errors. Thank you for your diligence though!