Auto-report movement to the map not working

Module Design
1

I am using a Send To trait to send a piece to an eliminated box on another Map Window and I have an Auto-report format set up for movement to this map. The report works if I drag the piece to the second Map Window with the mouse, but not if I send it using the Send To trait.

Is this behavior expected and is there a way to get the report to run with the Send To trait?

Mike

2

Might the Send To Location trait be triggered by a Global Key Command trait which has the Suppress Individual Reports box checked?

3

Please give a link to the module in question - it is hard to diagnose the problem without the module. See also How to report problems for more on how to effectively ask for help or report a problem.

Yours,
Christian

4

The Send To trait is being called be a series of Trigger Action traits that use Marker traits to determine what Zone to send them to. No Global Key Command is involved. The actual move works like a champ, it is the report for movement to the map that doesn’t work. The report does work if I use the mouse to drag it to the other map.

All of the Send To and Trigger Action traits are in a Prototype. The Prototype is called Send To, there is a similar one called Artillery Send To as the artillery units have a slightly different behavior. It also does not report when the Send To trait is triggered.

There are two maps involved, one is Union Efficeincy/Turn Track and the other is Confederate Efficiency/Turn Track. I know that the Union one is misspelled but it is consistent throughout.

Right clicking on the unit then selecting Send To then either Eliminated or Routed will trigger the action.

Here is a link to a Dropbox folder that has the module. It is not for public release and will be used for playtesting purposes for a new game.

Thank you for all the help.

Mike

5

The Send to Location trait does not count as movement, and no movement report is therefore shown. If you want that, you should add a Report Action that reacts to the key.

BTW, I’m not sure why you have the chain of Trigger Action actions. Why not simple have a CSA SendTo and a USA SendTo prototypes for the Eliminate entry, and then brigade specific X SendTo Prototype (which can include the respective CSA SendTo or USA SendTo prototype). It makes the logic a whole lot simpler. You can move the Send to Sub-Menu trait to the respective Combat ... prototypes so that you can keep the order of the context menu entries (commands included in a sub-menu can be declared in other prototypes).

You can also define the zones to send the units to via a Marker traits which you can use in the Send to Location traits. For example

  • Prototype Send to
    • Send to Location
      • Command: Eliminated
      • Map: {EfficiencyMap}
      • Board: {EfficiencyBoard}
      • Zone {"Eliminated Units"}
    • Send to Location
      • Command: Routed
      • Map: {EfficiencyMap}
      • Zone: {RoutedZone}
  • Prototype: USA
    • Marker
      • Name: EfficiencyMap
      • Value: Union
    • Marker
      • Name: EfficiencyBoard
      • Value: Union Efficiency
  • Prototype: Salomon Brigade

If you are somewhat disciplined with the naming of maps, boards, and zones, you can also do

  • Prototype Send to
    • Send to Location
      • Command: Eliminated
      • Map: {Faction}
      • Board: {Faction+" Efficiency"}
      • Zone {"Eliminated Units"}
      • Key: EliminatedKey
    • Send to Location
      • Command: Routed
      • Map: {Faction}
      • Board {Faction + " Efficiency"}
      • Zone: {Brigade + "Routed Units"}
      • Key: RoutedKey
    • Report Action
      • Keys: [EliminatedKey,RoutedKey]
      • Report: {PieceName+" send to "+CurrentMap+"/"+CurrentZone+" from "+OldMap+"/"+OldLocationName}
  • Prototype: USA
    • Marker
      • Name: Faction
      • Value: Union
  • Prototype: Salomon Brigade

Note that you can then also use f.ex. the Salomon Brigade in an Activaition Marker pieces and have a similar prototype to send to the right zone.

Prototypes are “cheap” in the sense that they are always unrolled when the piece state is build.

BTW, make sure to save your set-ups with the active player being <observer> or users may not be able to take ownership. Note, observer> is treated differently from other players by Vassal.

Please remember to mark the solution to your problem - it really helps other find the solution to their problems. Only you as OP can do that.

Yours,
Christian