←  Battlefield 3

PBBans

»

What is Corrupt Module List?

thetoast's Photo thetoast Jan 5, 2012

Citeren

Kick Command Issued (RESTRICTION: Corrupt Module List) for (slot#3) XXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXX deespys

Server was rolling good, then all of a sudden everyone gets kicked for Corrupt Module List. Still getting this after a server restart.
Quote

LumpyNtZ's Photo LumpyNtZ Jan 5, 2012

yup, many people now getting this..... :S
Quote

Rainer_Wahnsinn's Photo Rainer_Wahnsinn Jan 5, 2012

Same here. I would bet on a pb update that went wrong. I counted more than 200 kicks on our servers the past ten minutes. It seemed to work again and one of our servers filled up with 64 players but five minutes later all players were kicked again :(
Edited by Rainer_Wahnsinn, Jan 5, 2012 - 12:09 PM.
Quote

fozzer's Photo fozzer Jan 5, 2012

It's a restriction kick that has appeared on other games in the past and been fixed by Even Balance staff.

This is a response way back in 2007 when the same issue affected another game;
http://www.pbbans.com/forums/corrupt-module-kick-info-t30760.html/page__view__findpost__p__85292
Quote

jossmeruk's Photo jossmeruk Jan 5, 2012

Had to apply PB update to all our 7 BF3 server as everyone started to get PB kick which emptied all our servers. Thanks for that.
Please also update your client
Quote

MaydaX's Photo MaydaX Jan 5, 2012

If your server is still kicking a lot of people for it you can temporally set pb_sv_restrictions 0 and it will not kick players for those restrictions. But I'd advise admins re-enable later once it stabilizes.

I've also moved this to a public area to help others who have this issue.
Quote

jossmeruk's Photo jossmeruk Jan 5, 2012

Thanks
Quote

SuperTaz's Photo SuperTaz Jan 5, 2012

EB's quality control department is on vacation, I guess. :bigthink:
Quote

wickysnip-NNB's Photo wickysnip-NNB Jan 5, 2012

There have been reports of a mass kick issue with the following statement:

[PunkBuster Server: Kick Command Issued (RESTRICTION: Corrupt Module List) for (slot#14)

It has only affected some servers. If you receive this error, there is no need to open a ticket, as the developers are already looking into this issue.
Quote

LYTHA20's Photo LYTHA20 Jan 24, 2012

Thanks
Quote