Allot of my mechs are showing Invalid due to "Module Slot Violation" I have fixed the problem but I posted it just so you guys can clook into it.
Things I have tried to fix the problem
1. Restart Client
No result
2. Remove all Modules and save loadout
Gives same error with modules removed.
3. Click "Strip" button and use "strip all modules" option
allowed me to save the mech with no Modules.
4. Added Modules back to mech.
Was able to save mech without error.
This was all reproducible multiple times. As you can see below however I did not change the Modules during the workaround. Just re applied them
Before workaround
After Workaround
0
5 replies to this topic
#1
Posted 11 September 2015 - 02:41 PM
#2
Posted 11 September 2015 - 02:45 PM
This appears to be a hold-over from the bug that was introduced in the September 9th patch, and was hot-fixed on the PTS before it went live.
New occurrences of this shouldn't happen as a result of the hot-fix, but the bug may have carried over from 'Mechs that were affected by this on your regular production client.
As you outlined, the Strip All Modules > Save > Try again workaround will fix this for any of your problem 'Mechs.
New occurrences of this shouldn't happen as a result of the hot-fix, but the bug may have carried over from 'Mechs that were affected by this on your regular production client.
As you outlined, the Strip All Modules > Save > Try again workaround will fix this for any of your problem 'Mechs.
#3
Posted 11 September 2015 - 02:46 PM
I decided to check something, this is the load out from the NON PTS server.
Looks like one of the Consumable Slots was moved in the PTS from Consumable section to Weapon section .
Looks like one of the Consumable Slots was moved in the PTS from Consumable section to Weapon section .
#4
Posted 11 September 2015 - 04:25 PM
I posted bug reports about this in the Atlas and Battlemaster sub-forums. I tried stripping all the modules, and then saving. Then I attempted to reapply the modules. I repeatedly had the "invalid configuration" error appear. Also, the consumable slots would not display that a module had been applied into the slot, but I would get the error. I had to select a different mech to escape out of the bug.
I restarted the client as a test. The BLR-1G(P) had been stripped of all modules and saved before I restarted. After restarting I still received the Module Slot Violation error when I tried to apply a consumable.
After further testing I've found that the problem lies in manually removing modules from the slots instead of using the "strip mech" > "all modules" button process. When done manually the interface shows the slots empty and allows you to save. Then when you try to reapply a consumable it generates the violation error.
I restarted the client as a test. The BLR-1G(P) had been stripped of all modules and saved before I restarted. After restarting I still received the Module Slot Violation error when I tried to apply a consumable.
After further testing I've found that the problem lies in manually removing modules from the slots instead of using the "strip mech" > "all modules" button process. When done manually the interface shows the slots empty and allows you to save. Then when you try to reapply a consumable it generates the violation error.
Edited by GargoyleKDR, 11 September 2015 - 04:38 PM.
#5
Posted 12 September 2015 - 11:03 AM
Tuku, on 11 September 2015 - 02:41 PM, said:
Allot of my mechs are showing Invalid due to "Module Slot Violation" I have fixed the problem but I posted it just so you guys can clook into it.
Things I have tried to fix the problem
1. Restart Client
No result
2. Remove all Modules and save loadout
Gives same error with modules removed.
3. Click "Strip" button and use "strip all modules" option
allowed me to save the mech with no Modules.
4. Added Modules back to mech.
Was able to save mech without error.
This was all reproducible multiple times. As you can see below however I did not change the Modules during the workaround. Just re applied them
Before workaround
After Workaround
Things I have tried to fix the problem
1. Restart Client
No result
2. Remove all Modules and save loadout
Gives same error with modules removed.
3. Click "Strip" button and use "strip all modules" option
allowed me to save the mech with no Modules.
4. Added Modules back to mech.
Was able to save mech without error.
This was all reproducible multiple times. As you can see below however I did not change the Modules during the workaround. Just re applied them
Before workaround
After Workaround
I had the same problem with mechs loosing one module place which was occupied => only solution was strip alll modules and reapply
only removing the modules manually doesn't remove the module in the now invisible slot => you can't remove modules where the module slot was removed, but they are hidden on the mech => invalid modules....
Edited by Rentier, 12 September 2015 - 11:05 AM.
#6
Posted 12 September 2015 - 04:13 PM
The reason this happens is because they changed the number of consumables and the number of modules a lot of mechs get. So some mechs may have only 1 weapon module whereas previously they had 2, but in the snapshot they took of your mech configs for your account, it still has the 2 modules equipped, you just can't see it.
As others have said, if you get a module slot violation, strip all of your modules and then re-add them. More than likely the issue is you either have an extra consumable that can no longer exist, or an extra module or what not.
Also, be sure to check the modules on every single mech you build on PTS. Because they have changed, you may find yourself with an extra module you can utilize.
As others have said, if you get a module slot violation, strip all of your modules and then re-add them. More than likely the issue is you either have an extra consumable that can no longer exist, or an extra module or what not.
Also, be sure to check the modules on every single mech you build on PTS. Because they have changed, you may find yourself with an extra module you can utilize.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users