-
We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
Anybody interested in testing the 1.1 beta with Germany? You would have to informate us about any bugs and if you have any ideas we would be glade to hear them
Since Germany is my favorite nation to play as in any Paradox game, I am more than happy to test them.
That's good to hear I'm pretty sure you will enjoy it... I will upload the mod today and then I send you the link via pm!
Here are some screens of my current game!
ai china vs ai japan is doing a good job too!
ai china vs ai japan is doing a good job too!
yes you are absolutely right! Well we don´t have the right ai file for CommChina since we use the china scenario from DH 1.4, I will ask Limith!
Event files are needed for that..not ai files.
People don't understand the limits AI files can do.
You can go ahead and write event files if you wish. I am working on events we are using for DHF 1.04 but that won't be finished for a long time (well, anytime reasonably soon enough for your mod release) since I am very busy with work right now. I will likely reject events in EoD for DHF though based on the event quality and the fact the events I see in the mod do not work under the design principles of DHF (not a comment on if the mod is bad or not, TRP's design is different from DHF, and as a result we can't include events from that)
-Why Events are required:
--AI never moves sliders
--CHC starts too isolationist to DoW CHI
--CHI can't DoW CHC
--AI Event required to move sliders for AI to allow AI to DoW based on .ai files.
--AI Event required to switch .ai files for CHC to DoW
---Since we are already using events, it would be simpler to just have an event cause CHC to DoW CHI instead of writing an ai file and then writing a event to switch AI whereby the AI may or may not actually DoW.
---Even if we do do the above, then CHC may DoW CHI, peace out and then choose to DoW later stupidly when it can't survive since the "tell CHC to DoW CHI" ai is still loaded so we need to write ANOTHER ai file and event later to tell it to stop doing so.
---Intermediate ai switches may or may not mess up the process above.
As you can see, events in this case (as is in many cases) are better than ai files at handing diplomacy and DoW.
What AI events/switches/files should be used for:
--Intelligence
--Trade favors (embargo SHOULD, although it is not currently being done in DHF due to poorly written legacy code, be done via events)
--Accept demands chance
--AI neutrality
--Technology research
--Combat changes
---Garrison what provinces
---Ignore what country borders
---Launch sea invasions where
---How aggressive to be
--Build Priority Changes
NOTHING ELSE.
To be honest, my feedback right now, is that you should really stop adding in new things for the next few releases (keep the new CHI OOB though since that actually fixes the no point "Long March" + "Encirclement Campaign" events, what you do is use those events and for now force transfer the communists to Xi'an), go back and start REMOVING things and REWRITING them. Because a bazillion small things are broken right now or missing. There is a saying that the mark of a good coder is not one who adds new features (feature creep), but one who is willing to remove things and replace them with better more concise, and better coded, stuff. It's why I am rewriting CCIP from scratch. (And I feel KR should get a complete code rewrite as well, but it'll never happen, and it's sort've stable enough and too wacky/ahistoric anyway so the random weirdness that occurs isn't always stuff not working as intended. I also don't have confidence a code rewrite will necessarily result in better coded events, and well, in Computer Science, there is more than one way to do something, and brute force + bad code will still work, so, not my problem).
People don't understand the limits AI files can do.
You can go ahead and write event files if you wish. I am working on events we are using for DHF 1.04 but that won't be finished for a long time (well, anytime reasonably soon enough for your mod release) since I am very busy with work right now. I will likely reject events in EoD for DHF though based on the event quality and the fact the events I see in the mod do not work under the design principles of DHF (not a comment on if the mod is bad or not, TRP's design is different from DHF, and as a result we can't include events from that)
-Why Events are required:
--AI never moves sliders
--CHC starts too isolationist to DoW CHI
--CHI can't DoW CHC
--AI Event required to move sliders for AI to allow AI to DoW based on .ai files.
--AI Event required to switch .ai files for CHC to DoW
---Since we are already using events, it would be simpler to just have an event cause CHC to DoW CHI instead of writing an ai file and then writing a event to switch AI whereby the AI may or may not actually DoW.
---Even if we do do the above, then CHC may DoW CHI, peace out and then choose to DoW later stupidly when it can't survive since the "tell CHC to DoW CHI" ai is still loaded so we need to write ANOTHER ai file and event later to tell it to stop doing so.
---Intermediate ai switches may or may not mess up the process above.
As you can see, events in this case (as is in many cases) are better than ai files at handing diplomacy and DoW.
What AI events/switches/files should be used for:
--Intelligence
--Trade favors (embargo SHOULD, although it is not currently being done in DHF due to poorly written legacy code, be done via events)
--Accept demands chance
--AI neutrality
--Technology research
--Combat changes
---Garrison what provinces
---Ignore what country borders
---Launch sea invasions where
---How aggressive to be
--Build Priority Changes
NOTHING ELSE.
To be honest, my feedback right now, is that you should really stop adding in new things for the next few releases (keep the new CHI OOB though since that actually fixes the no point "Long March" + "Encirclement Campaign" events, what you do is use those events and for now force transfer the communists to Xi'an), go back and start REMOVING things and REWRITING them. Because a bazillion small things are broken right now or missing. There is a saying that the mark of a good coder is not one who adds new features (feature creep), but one who is willing to remove things and replace them with better more concise, and better coded, stuff. It's why I am rewriting CCIP from scratch. (And I feel KR should get a complete code rewrite as well, but it'll never happen, and it's sort've stable enough and too wacky/ahistoric anyway so the random weirdness that occurs isn't always stuff not working as intended. I also don't have confidence a code rewrite will necessarily result in better coded events, and well, in Computer Science, there is more than one way to do something, and brute force + bad code will still work, so, not my problem).
Last edited:
Can't wait to play next version 
I hope that problems with German mobilisation events will be solved
I hope that problems with German mobilisation events will be solved
There won't be a 1.03 RC4. There may be an unofficial 1.03.5 depending on when Martin comes back from his vacation.
