Developer Diary | Modding!

[PDXKatten]

Is the next dev dairy going to be about alt Finland?

Yes it will!

 

[Arheo]

Some effects (e.g. history) are buggy, while accessing one specific division is very hard.

Define 'buggy'?

 

[CarloPDX]

Does the modifier affect all owned forts, or only forts in core provinces? (If Norway annexed France, would it magically throw the Maginot Line into disrepair?)

Can it be used in state and province scopes, or just country scopes?

It affects every single fort, but if you wanna be more specific the modifier works in the state scope too.

 

[CarloPDX]

1) Any plans on increasing the amount of variables we gain access to? For example, we cannot access convoys.
2) Any new effects, triggers regarding the new trade system?
3) Any plans to enhance access to divisions? Some effects (e.g. history) are buggy, while accessing one specific division is very hard.

Overall, very useful changes!

They're not variables but you can access convoys as equipment, with convoy_1. I do that a lot in Norway

 

[CraniumMuppet]

Could you tell a bit about the "function"/code that converts Consumer Goods into actually useful bonsuses?

You just fetch the two consumer goods variables and perform your calculations as any variable and apply them as needed, there's no convert function per se

 

[C0RAX]

1) Will the new international market be moddable?
2) There was in previous dev diaries a talk about improvement to designer companies through "Military industrial Orgs.", yet so far we've had no news about their development, will this not be included in the new DLC?
3) Will the special forces tree be moddable in a similar manner to how doctrines are?

Details on the features we have announced for arms against tyranny will be in future dev diaries. You can find what is included in arms against tyranny on the steam page for the expansion pack.

 

[C0RAX]

Anything about modding MIO's?? Or it will get its own topic like custom achievements?

in a future DD

 

[C0RAX]

@CarloPDX @C0RAX or any other Dev Can you take a look about this post please:

[1.12.14] [5555] Paradrop 3 bug in 1

Summary [1.12.14] [5555] Paradrop 3 bug in 1 Platform Steam Operating System windows Game Version [1.12.14] [5555] Enabled DLC All of the above Do you have mods enabled? No Description 00:00 0.5. how i position the div 00:37 1. wipe stack...

forum.paradoxplaza.com

Or the next DLC will be a slaughter

posting a thread here wont get it seen to faster. bugs are tracked from the bug forum and fixed according to our internal priorities system.

 

[CarloPDX]

Something that I haven't seen yet is how the joint focus trees are defined.

Do they have to be defined in every focus tree that can access it?
Or does the Joint focus tree have it's own file that can be called within a country's focus tree if the necessary parameters are met?

It's a regular old shared national focus file, the "jointness" of them is defined focus by focus

 

[CarloPDX]

Bit late so probably won't get a response but will characters be made more dynamic/less hardcoded (probably not this DLC cycle but like maybe the next one, or an intermediate)? Stuff like allowing characters themselves to be stored in variables and checks like "is_hired_as = <advisor slot>".

Characters can already be added as variables! And I think you can get workarounds for the hired as advisor slot

 

[CraniumMuppet]

Theoretically, but they tend to break. I can't give any examples because it's been a while since I last tried, but in my experience variables/event targets that store characters always return null when I try to reference them later in script.
The 'is_<advisor_slot>' triggers got updates in one of the post NSB patches to only return true if the character was currently hired in that slot, BTW. Very useful, not sure why the triggers didn't originally work that way.

on_add/on_remove with character flag is_hired is probably the most robust one atm

 

[CarloPDX]

Theoretically, but they tend to break. I can't give any examples because it's been a while since I last tried, but in my experience variables/event targets that store characters always return null when I try to reference them later in script.
The 'is_<advisor_slot>' triggers got updates in one of the post NSB patches to only return true if the character was currently hired in that slot, BTW. Very useful, not sure why the triggers didn't originally work that way.

We've been definitely fixing a bunch of issues with the character system and I'm pretty confident about it nowadays so try again, specially when the patch for AAT comes out =}