I’m trying to eliminate unnecessary reporting in the chat area. I do not want card plays and marker movement to get reported. The technique I used to turn off general reporting of every move made on main map is to leave the field black of coarse and use “key command to apply to all units on this map” Then use the report action trait in game piece prototypes. However this causes a new problem. You see the report format commands listed under ‘report action’ do not give you the same command words to use. Under normal report using the main map setting I can move a stack of blocks and all the names would appear on one line. However using report action to try and do the same report is impossible within unit traits. Because of the slight change in command from $pieceName$ to $oldPeieceName$ what happens is that each block in the stack generates its own text line. So instead of a nice clean one line report when moving a stack of 10 blocks I get instead 10 lines. Why doesn’t the report action trait use the same commands as the main map report option? Is this a known issue?
Also I was thinking why not add a trait to the list that would allow a module creator to silence move reporting on certain units so that the main map setting could be globally used still. Since report action works funky I don’t find it a useful trait, but a silence report trait would be a no-brainer to add for a future update. There are so many modules that could benefit from reduced report clutter. I think my idea would become a very popular trait in most modules.
Anyway here is the line I used in the report action trait that produced the multiple report lines I didn’t want.
$oldPieceName$ move from $oldLocation$ >>> $location$
Typically something like this would appear on the main map report line. Now the two are trying to do the same thing but due to slight differences in command options available I can’t get an exact match in reporting style.
$pieceName$ move from $previousLocation$ >>> $location$