Issues about Victoria 3

[DragonKnightOfBreeze]

1. Unlike Stellaris, in Victoria 3, more script files are encoded in UTF8-BOM
2. Unlike Stellaris, in Victoria 3 (and some other games?), there are both alias[trigger:scope_field] and alias[trigger:value_field] (so do effect), make plugin treat them as conflict, as scope_field and value_field is not easy to be matched strictly

[DragonKnightOfBreeze]

@kaiser-chris If you find more problems, plz post them here together.

[kaiser-chris]

Scope chaining leads to errors:

Example from base game file:

first and second country as well as prestige is defined in links.cwt:

I did a few tests and all of these should be valid but some are not:

[kaiser-chris]

This is a maybe.
I could not find how to configure parameters in CWT and Victoria 3 uses them sometimes when setting up scripted effects.

Example Setup:

Example Usage:

The usage is only marked as working because it is also defined in effects.cwt:

This is a workaround since theoretically this is not a base game effect function but a scripted effect.

[kaiser-chris]

Victoria 3 has one more type of color: hsv360

Example:

I tried defining it in CWT like this, but it seems unsupported:

[kaiser-chris]

There is a problem with the new ?= operator when it is directly on a value.

Example and a few tests:

All of the above should be valid.

[DragonKnightOfBreeze]

You should not use customized cwt configs to make scripted effect invocation with parameters parseable.
There is already extended (not exists in original) cwt data types to support this. See below:

With these configs all things should works.

For parameter usages are not supported here, this may be checked in the future.

[kaiser-chris]

You should not use customized cwt configs to make scripted effect invocation with parameters parseable. There is already extended (not exists in original) cwt data types to support this. See below:

With these configs all things should works.

For parameter usages are not supported here, this may be checked in the future.

Thank you.
That is why I wrote that it is a maybe.
I will add this to the Victoria 3 CWT files and will create a Pull Request into your config repo:
https://github.com/DragonKnightOfBreeze/cwtools-vic3-config

[DragonKnightOfBreeze]

OKAY

[kaiser-chris]

This is really strange but province references seem to be working semi-randomly.

They are behaving so strangely that I made a screen recording just to show it:
https://share.bahmut.de/2024-11-25_10.29.41-f3f1d1_%25pn.mp4

As you can see changing one can make the other valid and vice versa.

CWT Definition:

Screenshot from game files where provinces are defined:

They are not defined in a classical sense but state by state and collected with this complex enum.