Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Tracking Smoke in VASSAL
04-23-2025, 11:42 PM,
#1
Tracking Smoke in VASSAL
It is a minor difficulty in VASSAL to track smoke usage.  There is no smoke counter nor is there a way to label unit ID.   If there was a smoke counter, one could simply stack them under the unit and expend one each time the unit fires smoke.  If we could give the units an ID number/letter, then one could track on a spreadsheet.   

The current smoke overlay is great for marking where smoke has landed, but not for tracking usage.

Another method, if possible, is to have a right click call out with a "smoke" number one could increase or decrease.
Reply
04-24-2025, 12:56 AM,
#2
RE: Tracking Smoke in VASSAL
(04-23-2025, 11:42 PM)Blackcloud6 Wrote: It is a minor difficulty in VASSAL to track smoke usage.  There is no smoke counter nor is there a way to label unit ID.   If there was a smoke counter, one could simply stack them under the unit and expend one each time the unit fires smoke.  If we could give the units an ID number/letter, then one could track on a spreadsheet.   
Tracking smoke in Vassal isn't any harder than with a dead-tree game. Still the point of ID's is noted. I was going to give OBA markers ID's with the next module update. On-board units are more complicated, because the counter is busier and a little irregular.
 
(04-23-2025, 11:42 PM)Blackcloud6 Wrote: Another method, if possible, is to have a right click call out with a "smoke" number one could increase or decrease.
Matt Brown did something like that with his WaS Vassal games. I don't know how I would work it into PG Uber.
... More and more, people around the world are coming to realize that the world is flat! Winking
Reply
04-24-2025, 06:09 AM,
#3
RE: Tracking Smoke in VASSAL
Quote:Matt Brown did something like that with his WaS Vassal games. I don't know how I would work it into PG Uber.
Unit attributes has a "spreadsheet" attribute, maybe that is what he uses?
Reply


Forum Jump:


Users browsing this thread: