Europa Universalis V

Europa Universalis V

评价数不足
Bugfix of the Rise of the Turks
   
奖励
收藏
已收藏
取消收藏
文件大小
发表于
更新日期
364.282 KB
11 月 11 日 下午 8:42
11 月 17 日 下午 4:34
8 项改动说明 ( 查看 )

订阅以下载
Bugfix of the Rise of the Turks

描述
This mod adds no content for the Turks or others in the region. it ONLY fixes the logic in the situation so that the content fires appropriately. Please see below for the full list of bugfixes.

Update: Good news! Paradox responded to the bug report saying the issues fixed by this mod have been addressed. In terms of compatibility with any update, this mod does nothing if you're already past the situation. So it can be disabled safely. As for saves taken during the situation, it should be fine to disable when the situation is fixed in a new patch. I very specifically did not add or remove anything, only fixed what was there.

Update2: Bad News. They weren't fixed in 1.0.5. Accordingly, I've updated the mod to include their fixes for 1.0.5 within my files. So the bugfixes they did do for the Rise of the Turks are included, but still has my fixes for the problems listed below.

Changelog:
Version 1.2
Game Version 1.0.5
No Additional Bugfixes from mod content..

Version: 1.1
Game Version: 1.0.4
1. Fixed a bug where the strongest Beylik, as a subject, could gain other Beyliks as their vassal, thus having vassals of vassals.

Version: 1.0
Game Version: 1.0.3
1. The mysterious "Ottomans does NOT exist" condition that could be fulfilled, but the situation wouldn't end.
2. The situation being able to end with a Beylik receiving both the event for winning AND the event for losing.
3. The situation ending with everyone else ALWAYS receiving an event that a Beylik won (even when they didn't).
4. The ability for the event to end by all Beyliks being conquered, but the situation still saying a "ERROR:[target_country.GetNameWithNoTooltip]" won.
5. A vassal Beylik being able to win the situation.
6. A beylik who was released via a peace deal, revolt, or manually would not be re-added to the list of eligible countries.
7. The strongest Beylik being able to vassalize other Beyliks through events, despite those beyliks already having vassals of their own.
8. The situation being invisible to the strongest Beylik's neighbors if that Beylik is anyone but the Ottomans.
9. An edge case possibility where a non-Ottoman Beylik could have the situation become invisible, despite them being the strongest candidate to win it.
10. Localization fix (English only) for the event where the Beyliks lose the situation.

If you'd like more information on any of these bugs (or just to help bring them to Paradox's attention!) please see the bug report I made for all of this before making the mod (linked below).

Bug Report on Paradox Forums: https://forum.paradoxplaza.com/forum/threads/severely-broken-logic-in-the-rise-of-the-turks-situation.1871092/

Shoutout to WallSoGB on Nexusmods for the pony bit. I love the joke so much.
https://next.nexusmods.com/profile/WallSoGB/mods?gameId=130
7 条留言
Bolso's Bizarre Adventure 11 月 19 日 下午 5:24 
aight then, hopefully its fixed soon, cuz jeez
Marcus Aurelius  [作者] 11 月 19 日 下午 5:15 
Correct. These bugs are not fixed as of 1.0.6. Developer "Big Boss" confirms they're in code review in the thread and should be fixed in (hopefully) 1.0.7 or 1.0.8.
Bolso's Bizarre Adventure 11 月 19 日 下午 2:14 
this still needed right?
Marcus Aurelius  [作者] 11 月 17 日 下午 4:38 
Mod is updated for 1.0.5
Marcus Aurelius  [作者] 11 月 13 日 上午 8:18 
Update: Good news! Paradox responded to the bug report saying the issues fixed by this mod have been addressed. In terms of compatibility with any update, this mod does nothing if you're already past the situation. So it can be disabled safely. As for saves taken during the situation, it should be fine to disable when the situation is fixed in a new patch. I very specifically did not add or remove anything, only fixed what was there.
Marcus Aurelius  [作者] 11 月 12 日 上午 11:48 
It's a massively complex game and it's clear they've got a lot of work to do. 2200 bug reports 1 week after release. That's over 300 a day on average. Even with the lengthy information I gave, that doesn't mean that it'll be quick to fix for them. Took me like twelve hours of coding to fix. (Then again, they actually _know_ their tools better than I do (I hope!)).
UtahGirlScratch 11 月 12 日 上午 10:15 
Should have been an obvious catch before release. I'm just glad someone fixed it. Here's hoping they can get to it in the next few patches.