Command Turrets seem to require their own unique brains #3438
Comments
|
Shadow Wolf TJC uploaded file Adds 3 new brains for the 3 Command Turrets that are lacking one |
|
Shadow Wolf TJC commented At the moment, Command Turrets II, III, and IV seem to not appear at all, even when they're researched. I believe that this is because they don't have a respective Commander brain assigned to them (as seen in brain.txt). |
|
Shadow Wolf TJC commented Replying to Warzone2100/old-trac-import#3438 (comment:1):
However, I'm still working with beta 7, and I don't have any plans to update to beta 9 anytime soon, so if I do make updates for those files, then developers SHOULD just splice the new stuff into the latest builds to avoid creating unwanted glitches. That's assuming that those files have been updated since beta 7 came out of course. |
|
Per commented What do you mean, appear? From the little I know about command turrets, there should be only one of them in skirmish. |
|
Shadow Wolf TJC commented According to the guide (http://guide.wz2100.net/w/), there appear to be 4 Command Turrets in total, with the more advanced ones requiring Composite Alloys upgrades. However, these more advanced Command Turrets weren't showing up. I later found out that they each required their own command brains as well, so I provided an updated brain.txt, as well as additional instructions on how to fix this in case you were using a different version of Warzone 2100 than I was. |
|
Shadow Wolf TJC uploaded file Since this hasn't been worked on yet, as can be seen on 3.1 rc3, I've decided to attach a simple mod that enables all the missing Command Turrets. Please note that, as with researching new weapons that make older weapons obsolete, researching the new Command Turrets won't replace older ones that are currently on the field. (You'll need to edit resultcomponent.txt to fix that issue.) |
|
Shadow Wolf TJC commented I've recently created a new account on GitHub, made my own fork on Warzone 2100, and pushed for a few changes on there, including one that's designed to fix this bug (though I needed to make changes to 4 separate files in the 3.1 branch): ShadowWolfTJC/warzone2100@7da3045 |
|
Cyp changed type from |
|
Shadow Wolf TJC commented Thanks Cyp. By the way, here's a new brain.ini for master builds: ShadowWolfTJC/warzone2100@e5271c3 |
|
Per changed status from |
|
Per changed resolution from `` to |
|
Per commented We no longer have commander upgrades. |
keyword_Commander_Brain_brain.txt_command_turretresolution_invalidtype_patch (an actual patch, not a request for one)| by Shadow Wolf TJCI've discovered this bug while testing out some new command turrets that I added to my mod, and I quickly found out how to fix it. It seems as if Command Turrets require their own brains (as specified in brain.txt) in order to appear and/or function correctly.
To fix this bug, we'll 1st need to create a new brain for each Command Turret. Next, in resultcomponents.txt and redcomponents.txt, we'll need to replace each of the Command Turrets with the new brains. That should allow players to use those Command Turrets properly.
I've included a new brain.txt file to help fix this bug, though it'll be up to you guys to replace the Command Turrets with the new brains in resultcomponents.txt and redcomponents.txt, and add the new brains in names.txt (as even they need a name it seems).
Issue migrated from trac:3438 at 2022-04-16 09:46:34 -0700
The text was updated successfully, but these errors were encountered: