Re-uploaded as the download I had previously put up was corrupted and wouldn't open.
Printable View
Re-uploaded as the download I had previously put up was corrupted and wouldn't open.
Rather curious thing: there is no problem setting the tool up for most of my mods, except for "Regions and Provinces" - I am getting an 'unhandled exception' error. The setting worked on previous versions, so I thought maybe a registry snafu and deleted the setting.
Same error when I set up a new setting.
Hope the error message helps.
Another thing: when I try to edit the setting (any), it insists on a new name for the setting (duplicate name). Which means I will have to create a new setting if I want to use a new path. That function maybe is not really needed?
Spoiler Alert, click show to read:
Any chance you will make ATVTW read custom factions and not report COMBAT_V_FACTION?
Still working on it.
Version 2.1.3
This is a bug fix release:
Changes from 2.1.2 Version:
- Fixed crash if a bad event is encountered in a trigger
- Restored ancillary listing to the ancillary trigger tab
- Added all other faction names from the kingdoms campaigns to the M2TW Combat_V_Faction_X set of attributes (this should reduce attribute errors until a better solution is found)
Go to the first post to get the new version.
I notice that recently you've changed to this:
this throws up a lot of errors where the GeneralWithAncKilled refers to an ancilliary - as per docudemons - and not an ancilliary typeQuote:
GeneralWithAncKilled now check for ancillary type instead of ancillary name
The docudemons are wrong, there's a discussion about it somewhere. The condition was supposed to check for ancillary but was set to check for ancillary type. The worst part is the error checking for the log checks for ancillary so using it the way its coded to be used will generate an error in your log if the ancillary type doesn't match the ancillary name.
Thanks for info - hopefully someone will amend the docudemons or put some sort of note on them for that condition.
ah - there's thread about GeneralWithAncKilled here:
http://www.twcenter.net/forums/showt...89#post3331689
and this:
The ‘GeneralWithAncKilled’ condition looks for the ancillary’s type, not its name. See posts 503 to 511:
http://www.twcenter.net/forums/showt...269194&page=26
discussion seemed to fizzlle out.
would the errors give rise to end of battle CTDs I wonder - we're getting quite a few in stainless steel?
I have made triggers with type as Marshall of Antioch and Jerusalem etc and i get it when i conquer those cities and i'm sure i have tested it in battlemap also not just by auto resolve.:hmm:
But i will check it just to make sure as my mod will be ruined lol and post a VM to you.:)
As part of technical staff I'm trying out a new bug tracking/feature request system. If you have any bugs to report or features to request for ATVTW please add them to ATVTW Bug/Feature Tracker.
If you have any problems with the tracker please PM me with the details.
quick q:
running a campaign script through the validator
throws up
Line 6715 - Error: Invalid condition , expected 'Trait <trait name> <login token> <level>', found 'Trait FactionRegent > 0'.
but no error for "and not Trait FactionRegent > 0"Code:monitor_event BecomesFactionLeader FactionType norway
and not FactionIsLocal
and not Trait FactionRegent > 0 (no error for this line)
historic_event norway_king_event
end_monitor
monitor_event BecomesFactionLeader FactionType norway
and not FactionIsLocal
and Trait FactionRegent > 0 (Line 6715)
historic_event norway_regent_event
end_monitor
is that correct?
Check to see if there's a tab instead of space on the line or visa versa.
checked - same error for every faction.
tab at start of both lines in every case.
The first line not reporting an error does not mean anything because I forgot to check for the use of not in a condition line. As for the error I think its an bug where I've coded the script checking to look for lines that have too many arguments on them. I'm investigating.
Thx for taking the time to sort out problem!
This has been fixed for the next release, see the bug tracker I linked above.
Version 2.2.0
Added:
- Ability to validate advice files, export_descr_advice.txt and text/export_advice.txt are now required
Changes/Fixes from v2.1.3:
- All events are now included in ATVTW (previously only character related events)
- Various performance improving changes
- Fixed a parsing error when reading to a new entry if an error is found
- Fixed parsing error where the parser though the file was ended when there was one last line to read
- Fixed condition parser not properly parsing unit names (each word in the unit name had been considered separate)
- Fixed crash for empty character, antitrait, excludecultures and excludedancillaries lines (i.e. with nothing after the key word)
- Reading settlements no longer requires descr_strat.txt (fixed bug where not all settlements were recognized if the settlement wasn't listed in descr_strat.txt)
- Fixed errors in the path to descr_regions.txt
- Fixed crash with unknown condition name
- Fixed some typos in condition checking code
- Fixed various typos in event and condition listings
- Fixed script parsing not recognizing the not keyword
- Fixed script parsing looking for too many things on a trait or ancillary related condition
- Fixed various errors in error messages
Go to the first post to get the new version.
Version 2.2.1
Changes/Fixes from v2.2.0:
- Lists of conditions, effects and affects now color only the lines with an error
- Fixed bug with conditions with no requirement
- Added == to M2TW logic tokens
- Added named_character to character types (named character is still included)
- Added a check to EDCT validation for ancillary related condition as they do not work in EDCT
- Fixed inability to edit settings
- Fixed a typo that prevented very_hard being recognized as a campaign difficulty
- Fixed bad argument list for condition PercentageUnitAttribute
- Added conditions I_HotseatEnabled & I_IsFactionAIControlled
- Fixed two mispellings of Siege
- Fixed enum reader expecting a new enumeration but finding a non-comment
- Fixed corrupted settings not being deleted because the registry entries had been opened in read-only mode.
Go to the first post to get the new version.
Thanks for the X-mas goodies!