Square Brackets In Unit Name Cause Parsing Problem
Brought to you by:
mshariy
Menu
▾
▴
#7 Square Brackets In Unit Name Cause Parsing Problem
Atlantis Llittle Helper version 2.6.4, build 194
wxWidgets 2.6.1
Python is not supported.
It appears that having square brackets in a unit name causes Helper to not be able to match the unit with its actions for that turn.
For example "Pack Team [Grain]":
Events during turn:
Pack Team [Grain] (443): Gives 2404 silver [SILV] to Nthorhan the
Black (267).
Pack Team [Grain] (443): Walks from grotto (11,5,underdeep) in Raymdyn
to grotto (12,6,underdeep) in Raymdyn.
All other units seem to be reporting their events correctly. I have 3 units with square brackets and all three have nothing despite events.
The section where the events should be.
A followup: Changing the name to remove the square brackets on one causes the Events to display while the ones with brackets still show no events.
It must be caused by generic parsing routine oriented at structures like
2404 silver [SILV]
I do not think it is worth fixing at this stage in the development :)
In general, comments like this are much better to put in the 'comments' pane like this: ;Grain
Yes, the first symbol of the comment must be semicolon.
If it is done like this, the comment value can be displayed in the unit grid and units can be sorted on this value, which is quite beneficial.
If you disagree please let me know
I appreciate the reply. It is certainly not a critical bug, but it is a bug that ought to be fixed, in my opinion.
As far as putting them in the comments, that is certainly a work around but I prefer to have the name reflect it so when I browse the text Report I can can tell who is doing what during the events.
I could also just as easily use a unit description (which I do) but I still need a way to easily follow the events. I don't actually use AH for issuing orders, as I find it easier to use the orders template and go down the list.
Ok, if you send me your report and unit number I will see if it is easy enough to fix. Please send it to mshariy@gmail.com