"Sickles Stays Home (U-Corps)" - bug (?)

[bafonetto]

perhaps there is an error of coordinates (and movement) in the scenario "Sickles Stays Home (U-Corps)":

command TIME
16:40:00 PM, OOB_U_JBarnes, Amoveto, 112500,102000 ,,,,,
16:40:00 PM, OOB_U_JBarnes, Auseroad ,,,,,,,

command events (wrong(?)):sick:
evtarrived, OOB_U_JBarnes, Amoveto, 107850.84900 ,,,,,
.
.
.

command events (right(?)):(
evtarrived, OOB_U_JBarnes, 112500,102000 ,,,,,
evtcont, OOB_U_JBarnes, Amoveto, 107850,84900 ,,,,,
.
.
.

[Little Powell]

perhaps there is an error of coordinates (and movement) in the scenario "Sickles Stays Home (U-Corps)":

command TIME
16:40:00 PM, OOB_U_JBarnes, Amoveto, 112500,102000 ,,,,,
16:40:00 PM, OOB_U_JBarnes, Auseroad ,,,,,,,

command events (wrong(?)):sick:
evtarrived, OOB_U_JBarnes, Amoveto, 107850.84900 ,,,,,
.
.
.

command events (right(?)):(
evtarrived, OOB_U_JBarnes, 112500,102000 ,,,,,
evtcont, OOB_U_JBarnes, Amoveto, 107850,84900 ,,,,,
.
.
.

Ah, once again good eye bafonetto.

So since the evtarrived coordinates are invalid, when Barnes arrives at his destination, he will be staying in Column formation and keeping whatever orders he currently has instead of Hold. A minor issue but an issue none the less. Thanks for reporting it.

[RebBugler]

Yeah, that's a scripting error, should have followed up evtarrived with arrival-coordinates, with the command column left blank...like you corrected it.

However, it's a moot point since Barnes would never have gotten there anyway since he was not TC'd. The game has evolved since, now, with a recent patch, TC'd units can use the evtarrived command...before, not.

[Little Powell]

Been doing some testing with this. With the fixed script, Barnes does approach his assigned destination every time even un-TC'd, but it's still a moot point because the scenario ends before he can get there. :laugh:

So really there's no fix necessary. The evtarrived lines should probably just be removed to clean things up.

Thanks for reporting anyway bafonetto! When are we going to see a mod scenario from you?

[bafonetto]

bafonetto[/b]! When are we going to see a mod scenario from you?

Thanks for the nice words LP.
I am not able to 'invent' scenarios ... thus correct (if necessary) those made by the community.

Speaking of errors: A.P. Hill scenarios:
GBLP02-July1-Take Hill Cemetery (C-Corps)
evtdisttarg, OOB_U_TAROWLEY2, "Aorders: attack, 500",
evtdisttarg, OOB_U_JSWADSWORTH, "Aorders: attack, 500",


GBLP04-July2-End This Fight Here (C-Corps)
evtdisttarg, OOB_U_JBARNES, "Aorders: probe, 500",

These commands should not be enclosed into quotes. I think.

[Little Powell]

These commands should not be enclosed into quotes. I think.

I checked those commands and they are not in quotes when viewed in excel.

Copied from the battlescript:

OOB_U_TAROWLEY2 Aorders:attack,500
OOB_U_JSWADSWORTH Aorders:attack,500

So it must be something with viewing them in a text editor that adds the quotes.

[bafonetto]

I use NOTEPAD or the 'old' WAREDIT 'of TC2M.
(I prefer notepad for an overview, then check the right commas with WarEdit)

If you open your files [battlescript] with notepad you should see what I reported.

PS: OpenOffice saves files [.csv] with quotes ("...").

Happy day from Italy

[Little Powell]

I use NOTEPAD or the 'old' WAREDIT 'of TC2M.
(I prefer notepad for an overview, then check the right commas with WarEdit)

If you open your files [battlescript] with notepad you should see what I reported.

PS: OpenOffice saves files [.csv] with quotes ("...").

Happy day from Italy

Yes, I'll have to do some testing. I can see the quotes in Notepad, but they are not there with Excel. In Excel, the commands look exactly how they are supposed to. IIRC, the commands are working properly as well. Again, I'll need to do some testing. Thanks again.

Edit: We also worked on getting the files to work with Open Office, but there are some format issues with the Time column.