Gamma Campaign Research Bug #4556
Comments
notos98 uploaded file Save game files |
vexed changed blocking which not transferred by tractive |
vexed changed blockedby which not transferred by tractive |
vexed commented Yes, please use 3.1.5, or, please help test the fixes that Berserk Cyborg has been doing. We are in need of testers for 3.2 campaign issues! Please see here: http://forums.wz2100.net/viewtopic.php?f=1&t=12714 for info on how to help! Thanks! |
Hironaru commented Hello, This issue seems to persist in 3.2.3. Operating System |
Berserk Cyborg changed status from |
Berserk Cyborg changed resolution from `` to |
Berserk Cyborg commented This don't seem to happen anymore according to campaign testers. See post in http://forums.wz2100.net/viewtopic.php?f=1&p=139372#p139354. |
resolution_closed
type_bug
| by notos98Short and to the point:
This bug occurs when you load a savegame from gamma campaign or starting a fresh one from the main menu. Beta and Alpha are unaffected by this bug.
What it does: Nullifies almost all previous research, all units already built and built after the bug will have base stat values for the body, propulsion, and turret. Structures are bugged as well, turrets on defenses do base damage/ROF but some structures retain some upgrades (health on factories is 1100 and walls down to 550) but not what you have access to in gamma.
It will NOT happen if you enter Gamma campaign normally (Final Beta mission -> starting Gamma). However it will return as soon as you load after saving, so you can still beat gamma but only if you do it in one sitting.
Will upload 2 saves, Beta - 11(final mission) and Gamma - 1 bugged saved. You can recreate it by loading a campaign from the menu and look at your units, if the tanks you have are 1600~ 2000~ commander then you are bugged.
One odd thing worth mentioning if you load a fresh gamma campaign the machine gun turret does not exist in the blueprints when you select "show obsolete tech". Hope that helps
Issue migrated from trac:4556 at 2022-04-16 12:40:23 -0700
The text was updated successfully, but these errors were encountered: