Use this forum if you have a relatively general question or comment about a game, Ventrilo, TeamSpeak, or Murmur/Mumble server with us. If you have a server-specific question that might not help out the community, please directly contact us through your control panel instead.
Number024 wrote:I was asked to post this from the IRC support channel because the NFO admin thought it was a good idea:
1. Would you consider having the admin daemon keep a timestamped log of server chat available for retrieval? Break it into 1 hour chunks and keep a couple weeks of logs or up to a certain disk space allocation of chat.
2. Keep a timestamped file for each in-game admin entered into the daemon for tracking the various commands he/she has run in the game?
I thought these two suggestions would provide a straightforward way for server operators to validate or invalidate allegations of admin abuse. The per-admin file would give you a list of what commands were run at what time by a specific admin. The chat log would let you look up the corresponding time commands were run and see the context in which those commands were run.
Thanks for the consideration!
if implemented, provide yes/no check boxes for both #1 and #2, so we have the option to opt out of keeping the logs if we want. might as well note here that procon already provides this ability if you want to implement it.
Number024, the game itself should add logs for the remote admin system at a later time, like BC2's. We'll likely wait for this and only implement our own logging system if they decide not to -- it's actually a pretty complicated thing to do from our perspective, since the daemon is centralized.
Edge100x wrote:The request was for per-round, so I made it per round.
Is it all possible to add an additional option for !scramble on map change as well? Some of our servers need to be scrambled per round and other need a scramble on map change.
Edge100x wrote:The request was for per-round, so I made it per round.
Is it all possible to add an additional option for !scramble on map change as well? Some of our servers need to be scrambled per round and other need a scramble on map change.
Thank you
i support this as well, can we get it done on map change? that would be very beneficial. it seems as though =Quack=Major.Pain alluded to this same idea.
thanks again NFO for the excellent work on the bf3 admin daemon in easy setup.
Edge100x wrote:The request was for per-round, so I made it per round.
Is it all possible to add an additional option for !scramble on map change as well? Some of our servers need to be scrambled per round and other need a scramble on map change.
Thank you
Dito for the option to make it "per map change" as well...
The Adjust Player Limit Automatically is working wonders to populate our server ! Thanks !
disconnect wrote:Does the cycler have the smarts to know what map was played last so they dont play the same two rush or conquest maps back to back? I would like to set it up so its rush, rush, conquest, conquest.
Yes, it does have a little intelligence in this respect. In random mode, it won't let the same map + mode run twice in a row, so you wouldn't have Panama Canal on Conquest twice, for instance.
Also, thanks for all the feedback, guys. I will be working on many of these features for the next iteration .
Is it possible/feasible to add logic to ensure that a map only repeats after all other maps have cycled? I have seen times when a map would repeat after two map changes. So basically for every map played take it out of the cycle until the rest have been played/loaded.
The "adjust player limit automatically" feature is a nifty tool. Is there any way to do something similar, only on the "round start player count" side of things? That is: I'd like to set my var for round start player count at 2, but when more than 8 people are on the server, I'd like the var to change to 8.
The reason I ask is because of the black box of QM, of course. One of the rumors I've heard is that QM favors the round start player count 8 servers.
Edge100x wrote:
saltney, possibly. But, I shouldn't put more time into the auto-player-limit-adjuster.
I agree with you, John - you definitely shouldn't have to spend time working on scripts to get around the nonsense associated with this game's matchmaking. Hopefully DICE will refine their systems. Thanks for the extra things you've done.
.