View Issue Details
| ID | Project | Category | Date Submitted | Last Update | |
|---|---|---|---|---|---|
| 0024087 | AI War 2 | Bug - Gameplay | Nov 10, 2020 12:26 am | Nov 10, 2020 8:57 pm | |
| Reporter | Wuffell | Assigned To | Chris_McElligottPark | ||
| Status | resolved | Resolution | fixed | ||
| Product Version | 2.628 Mod Proliferation | ||||
| Fixed in Version | 2.629 Ship Cap Hotfix | ||||
| Summary | 0024087: Unit cap not increased with higher tiers | ||||
| Description | Since the patch today, the unit cap for units seems to act as if they're MkI. I loaded a current game, my Parasite MkVII is at 312/104, and others are similar. I started a new game and increased tech levels, but the unit cap no longer increases. I didn't see this in the change log and I believe it would be a terrible change unless the ships get a lot more powerful. Can you please take a look? Cheers! | ||||
| Tags | No tags attached. | ||||
| related to | 0024088 | resolved | Chris_McElligottPark | Loaded save has misapplied technologies |
|
|
I see this was linked to another. Just a note, this isn't solely related to a saved game. it can be reproduced by starting a game and levelling up a technology. I put three levels in and my parasites showed the Mk increase, but still showed the same cap. |
|
|
I have the same issue. Forcefields or turrets don't increase caps. |
|
|
Yikes! Thanks for the report. I think that this is probably a mistake in the new xml parser. I am looking into it. Most likely it's just a minor typo on my part that affects certain data types, but not others, in the presence of multiple xml files. I should have a fix out within an hour or so. |
|
|
Thanks! * A simple typo was breaking all of the xml parsing for sub-lists of data of the following types (unless they had the requirement of IsUnique on): fint, arcenpoint, vector2, vector3, ** Most of these were new or unused in general, but fint was not new and is used for the scaling of ship caps in the game, as well as for the engine stun seconds progression. ** All of our other list parsing, which are more commonly used, were all working fine. |
|
|
Thanks for the fix! |
|
|
My pleasure! Sorry for the trouble, and thanks for catching it. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| Nov 10, 2020 12:26 am | Wuffell | New Issue | |
| Nov 10, 2020 1:28 am | BadgerBadger | Relationship added | related to 0024088 |
| Nov 10, 2020 1:32 am | Wuffell | Note Added: 0059521 | |
| Nov 10, 2020 2:48 am | ArnaudB | File Added: 20201110084635_1.jpg | |
| Nov 10, 2020 2:48 am | ArnaudB | Note Added: 0059522 | |
| Nov 10, 2020 8:43 am | Chris_McElligottPark | Note Added: 0059527 | |
| Nov 10, 2020 9:24 am | Chris_McElligottPark | Assigned To | => Chris_McElligottPark |
| Nov 10, 2020 9:24 am | Chris_McElligottPark | Status | new => resolved |
| Nov 10, 2020 9:24 am | Chris_McElligottPark | Resolution | open => fixed |
| Nov 10, 2020 9:24 am | Chris_McElligottPark | Fixed in Version | => 2.629 Ship Cap Hotfix |
| Nov 10, 2020 9:24 am | Chris_McElligottPark | Note Added: 0059528 | |
| Nov 10, 2020 7:28 pm | Wuffell | Note Added: 0059541 | |
| Nov 10, 2020 8:57 pm | Chris_McElligottPark | Note Added: 0059546 |
