Important notice to BF3 admins.

[Ki!ler-Mk1]

The ingame admin we use is generated by an RCON, While i do not believe multiplay are correct in saying that procon is to blame for a lot of crashes, we are going to cease using procon while we are playing. Just in case.

In order to kick a player you will need to contact either myself or thatbloke, and we can do it in clanforge.

I dont know when i will go back to procon(still use it to fill the server), but assuming the server keeps on crashing ill go back to it sooner.

/me hopes for no crashes

Afteral i'd rather a stable server than an admin'd server.


____

Today i got the server up to critmass (40 ppl) in 1/3 the time it took yesterday, and i have learned that the method i was copying was slightly flawed.

 

[Ki!ler-Mk1]

If you are on the server and the kill streak messages are enabled this means that procon is running, in this event, the admin commands below are online for all admins:

!say, !kill, !kick, !tban, !yes, !cancel.

You must still give a reason when using !kick & !tban:

!kick <player> <Reason>

Its important to note that even without an RCON we can still make space in the server via random kicking in clanforge.

 

[VibroAxe]

Afteral i'd rather a stable server than an admin'd server.

How's it going so far?

 

[Ki!ler-Mk1]

It would appear to be correct, the kickall bug does only happen when procon is on, but it is not clear if it is related to user input/plugins or dice error.

If you can see the kill streak messages, procon is on, the scrolling server messages are not from procon.

 

[Traxata]

It would appear to be correct, the kickall bug does only happen when procon is on, but it is not clear if it is related to user input/plugins or dice error.

If you can see the kill streak messages, procon is on, the scrolling server messages are not from procon.

Procon has nothing to do with DICE/EA so they're hardly to blame for someone elses third party mod breaking their servers are they?

I feel a told you so coming along here ....

 

[Ki!ler-Mk1]

Procon has nothing to do with DICE/EA so they're hardly to blame for someone elses third party mod breaking their servers are they?

Well, they paid for the lead developer to fly from Australian to Sweden before launch. And something may be caused by procon, but so far those problems have all be related to BF3server not being capable of handling lots of commands.

I mass kick issue is not to do with procon, K say today it was the server loosing connection to EA.

I feel a told you so coming along here ....

I dont think so.

 

[thatbloke]

Procon has nothing to do with DICE/EA so they're hardly to blame for someone elses third party mod breaking their servers are they?

I feel a told you so coming along here ....

No Trax, but if procon is sending syntactially correct commands to the server but the server is cocking up the execution of those commands, then it's the server's fault, not procon's.

But I have asked Mk1 to keep procon off as much as possible for now anyway, and so far the server has at least seemed to be more stable.