lol the most people hate Devils Perch....you are the first men how like it

Sorry to hear that McSlaine, but from what I have gathered so far, for each person that likes Devils Perch there are at least other 4 that do not like it. :'D Personally there isn't any Special Forces map that I truly dislike, I didn't dislike Devils Perch either. Let's see how these changes impact the server.

Staff Officer S_h_a_r_k_93 

EDIT: Correct me if I'm wrong but today the server looks like it's going well since 14 UTC non-stop, with an average of 14 players more or less!

Yeah, ran very well. up to 23 players today on SF

Thanks to dsghsdf and Princess_Unicorn we have tested and edited the safe zones to tweak them further and make sure the players can travel through the flags without getting a warning. They will still be warned if their intention is to go into the safe zones marked in orange and red.

GHOST TOWN:

(Auto resize: 512x512px, png)

SURGE:

(Auto resize: 512x511px, png)

Unfortunately the change about the unlocks has not yet gone live because the server needs a reboot but today it was active for the whole afternoon and it is still going! =D As 5tarLine pointed out the unlocks were already discussed here: https://www.lost-soldi...forum_topic&topic=580.

Staff Officer S_h_a_r_k_93 

thanks shark, zones look good. less confusion on the server.
and the unlocks are great too, gj guys.


and it mostly depends on wich server the first guys join, the rest follows.
ranked or not doesnt make a difference, yet.


can i suggest to make the fighting commander kick last for the rest of the round?
most get kicked, rejoin and go fighting commander again. some get 2 or 3 kicks in one round.
makes autoadmin look useless.
or any news on the commander/playercount restriction?

thanks for your server and your work.

Have you tested with a brand new account with no Weapons unlocked and in that case can you confirm that all Weapons were unlocked/usable?


Due to BF2CC being shit software and due to our Custom Automated Cross-Server Instant Ban Synchronisation System normal BF2 Temporary Bans which are processed through BF2CC are not possible as they damage the contents of the mm_bans.xml & banlist.con files. I have long-term plans to develop a new Temporary Ban System that will maintain the bans in a separate list within our AutoAdmin Software and simply keep kicking players who are temporarily banned when they re-connect to a Server until the time is up. I don't have time to start working on this right now and I'm not going to promise it will ever happen, we will see if it's actually worth doing this in the future when & if our Servers recover from being de-ranked when we finally leave Battlelog.

I think it "makes autoadmin look useless" is the wrong choice of words and a little harsh though considering virtually no one else has functioning AutoAdmin and being kicked from the game for breaking rules is not exactly 'useless'.


As above, I'm not aware of any drag & drop script we could use for this. We would have to write it ourselves, it shouldn't be as difficult as the Temporary Bans but it's no 5 minute job and we have to balance the time it takes to code and test this with its worth. So no news I'm afraid.


Thanks for supporting / playing on our Servers and for your feedback.

i did test it just now.
i used some old lowrank account with 1 or 2 weapons unlocked already, those worked, all other weapons/classes had no unlocks available.
the server is running since 40rounds too, so no restart yet.

i never worked with bf2cc or bf2servers in depth, just basic ingame commands.
all i knew about servers is bf42 stuff, no autoadmin, no php, no complex code,no dbs,no own ranking..
just custom servermessages/commands, mapcycles, settings and few bf42 tricks.

T-Gamers has commander limitation and i heard you/shark are in contact with tema56something.
i send shark few old links about it but i dont know if its any use to you.

sorry for being impatient and the autoadmin usless part was wrong choice of words, my english is limited.
but in the end it doesnt do much then just show warnings that everybody can read and remove the offender for 30-60 secs from the game.
he rejoins and continues until the next 30sec kick. he keeps score and everything.
but yes, "useless" autoadmin is better then no autoadmin/no rules server, thats why i play here

thx

Thank you very much for your valuable feedback as always, dsghsdf. About the unlocks ... as I said I didn't quite apply the change I was going to try. :'D ... So ... I don't know what happened with the unlocks actually. :'D

About that feature of AdminMap keeping in its memory that it kicked a certain player and should act accordingly on said player's rejoin event, it has already been pointed out before and as 5tarLine said we were thinking of making this new feature ourselves with some help, but it's not at the top of the todo list I'm afraid.

And finally about the commander/playernumber restriction there are no updates at the moment.
I will inform you if there are any.

Staff Officer S_h_a_r_k_93 

EDIT: I have just joined the servers and we're still observing the earned unlocks; as I said the change I've made is not yet applied, nor I am sure it will have the desired effect.

Okay so I have tried to uncheck the Global Unlocks setting in BF2CC but even so we're still observing the battlelog.co earned unlocks; I am not sure if that setting was actually applied but eventually I don't think it's going to do the trick. We will have to investigate further.

Meanwhile I managed to talk to Tema567 and he shared the script about restricting the commander usage with us; so I wanted to discuss with everyone and with dsghsdf what would the best threshold number be.

With the Staff Officers we thought 11 could be a nice value: the script makes the commander resign if a person tries to apply to commander when there are ≤ X players. So with 11 players in the server, if dsghsdf applied for commander he would then automatically resign.

In the event a 12th player would join the server, the script would not kick in anymore so you could have a battle between a 5-man squad + 1 commander vs 6 soldiers or vs 5 soldiers + 1 commander (in other words the script does not make you resign anymore if there's a 6 vs 6 going on in the server).

If the player number would drop back to 11, the script would activate itself again and there couldn't be any commanders anymore. Most likely the current commander (if any) would be picked up by the script and it would be automatically forced to resign.

Let me know if 11 sounds great to you guys as a possible threshold number. If possible, and I think 5tarLine would agree, if we are to install this script on all the servers I'd stay consistent with the threshold.

Staff Officer S_h_a_r_k_93 

That sounds great.

In the past it was sometimes really annoying when the people commander even though only 4 people were on the server.