Closed adriangaro closed 4 months ago
Most of these types for parameters normally could never be inferred since the ECO_CAT
for example is used as part of this syntax, which would be nigh impossible to deduce
complex_trigger_modifier = {
trigger = check_modifier_value
parameters = {
modifier = $ECO_CAT$_$RESOURCE$_produces_add
}
mode = add
}
Yes you could technically go and declare configs manually for all these parameters for inlines/script values etc, but it would be cumbersome and detached from the definition of the inline/script value etc.
Yet again this all already works (which shows how great your work for the custom cwt configs is), the main thing would be just auto complete for the parameters defined explicitly in cwt config
Will be checked in 1.3.5
Will still be unresolved after completion if it's not already defined in actual.
Will be implemented in 1.3.5
While this seems initially as not necessarily as a bug, and to be frank it is not, it can have some usecases for the purpose of creating some dummy inlines for easy type hinting for example, where the parameters can be passed to an inline with a cwt config declared for its parameters, but said parameters are never used, the game does not mind and considers as valid.
For example i have the following
The purpose of this empty inline with cwt config is to be able provide essentially preconfigured type inference/hints for parameters of an inline/scripted effect etc.
I use the above as following
This works and it correctly makes the parameters of that type declared in the cwt config i made, but autocomplete is never provided since the fake parameters declared in the cwt config are never used.
![image](https://github.com/DragonKnightOfBreeze/Paradox-Language-Support/assets/11583810/2bae29e5-521b-4527-80fd-9a2549b48f85)