Mass Server Update Thread

I lied.. the server is still failing and the providers are equally fail. I'll keep you posted, most likely moving it once I find a better not-so-dip-shit host.

The server is located in Frankfurt and it's running on the fastest core for core Sandy Bridge-E procs available for commerical use (except for the upcoming X5 & E5 procs). The problem is at the data-center and not the server itself.

Yes, I have tried and used i3d.net and they're sh*t imo. They use watered down hardware and run too many servers on a single machine (we even just recently tested them again, if you remember they're also the ones that butchered the BF3 Beta). They are the equivalent to Gameservers.com in the states.

No worries we'll figure it out.

Upcoming EA Blaze Updates 3/20

<div class='quotetop'>QUOTE </div>

<div class='quotetop'>QUOTE (Bender @ Mar 20 2012, 03:15 AM) <{POST_SNAPBACK}></div>

Oeps.. I just dropped that in the shitbox. My bad.

InterNap Service Inbound 3/27

<div class='quotetop'>QUOTE </div>

There is still some weird stuff going on with the Internap maintenance, that has been causing a fair amount of latency on the servers and the servers to crash. It's being worked on now but that is the reason why the Chicago based servers are failing on and off.

Hopefully it will be resolved soon.

Server Side Update R20:

<div class='quotetop'>QUOTE </div>

Fixes - PC Server operation
- Having the same map occur multiple times in the maplist now works properly
- If adding a new map to the servers maplist after a clear and then running "mapList.runNextRound" the server will ignore any remaining rounds on the map that it still run since before the clear and move to the new first map in the list. The server will now have reset the current rounds per map and run the map in the list for the number of rounds stated when adding the map.
- Maplist can contain up to 1000 entries now
- mapList.list will return at most 100 entries. To get the entire list, perform mapList.list repeatedly with increasing offsets (like banList.list)
- The locked-in-place warm-up has been replaced by a warm-up where players can move around, shoot, and take objectives; scoring is disabled during warm-up
- The Conquest Assault layouts on Back to Karkand maps have had the gamemode names changed to reflect that Conquest Assault is a gamemode in its own right
- vars.serverDescription is documented (it shows a string on a server’s detail page on Battlelog)
- vars.roundLockdownCountdown can be used to control the pre-round timer


The renamed Conquest Assault modes will cause initial confusion. The 3rd party admin tools don't know about this change yet, and existing Maplist.txt configurations contain the old names, so this is something that server administrators need to be wary of. It is a one-time change though, and it's worth it in the long run.

Server Side and Battlelog Update 3/31:

<div class='quotetop'>QUOTE </div>

Provider Blaze Notification:

<div class='quotetop'>QUOTE </div>

Yes.

Yes Pimp it was to repair the player dumps that were occurring yesterday.

Also the R22 update should be out at any time to fix the fubar rcon protocal. It should fix the random "killed or kicked by admin: something, something" glitch that have been occurring pretty regularly since the last patch.

ADMIN ABUSE!!!

Hey! Good job... you guessed BNder's middle name

BL and EA Blaze Maintenance 4/3

<div class='quotetop'>QUOTE </div>

EDT is 4hrs behind UTC

All of the servers are going to go down, so we're going to need some guys/idlers to get them going again.

No because it's a back-end update

The update appears to be rolling through now and an Origin update was also released, so you will need to update your client. The update ended up rolling our later that originally reported.

Right now you can't connect to any our of servers and if you recieve this message:



It's due to the update and not your game failing or the servers, hopefully the update finishes before it completely nukes the servers