BF2CC v1.0.2170 released
Die Entwickler des Server-Managers Battlefield 2 Command Control (BF2CC) haben etwas überraschend eine neue Version ihrer Software veröffentlicht. Die bisherigen Releases wurden immer angekündigt oder erfolgten direkt nach einem neuen Patch für Battlefield 2.
BF2CC für BF2 v1.12 & Special Forces
Die neue Version enthält eine ganze Serie von Bugfixes, Veränderungen und Neuigkeiten. Der wichtigste Punkt wird vor dem offiziellen Changelog separat aufgezählt: In der neuen Version kann es nicht mehr vorkommen, dass eine Map in die Rotation aufgenommen wird, die nicht existiert. Dieses Problem ist vor allem bei Mods aufgetreten. Die Software überprüft nun, ob die Map vorhanden ist und setzt bei einem fehlerhaften Eintrag eine vorhandene Map in die Liste. Mit der neuen Version kommen deshalb auch veränderte Mod-Manager Scripte (Vers. ?j?).
Weitere Features & Changelog
- FIXED (Daemon) - MM AutoAdmin functions were not properly being disabled when running a Mod because the modmanager.con file that was being edited was in the mods\modname\ folder; however, the daemon tells BF2 to read ALL .con files from the mods\bf2\ folder.
- FIXED (Client) - Upon Restoring the Map List form from a previous session, if the client hadn't queried the running Mod before the Map Form was loaded, the user would see a "Null Reference Exception" and the map list would show as blank. This only happened when the BF2 server was running.
- FIXED (Client) - Added the "+modPath mods/
" to the Join Parameters so that players won't have to load BF2 twice to join a modded server. - FIXED (Client) - Changed the Format of the Time and Idle column so that they sort properly.
- Possibly FIXED - Changed Threading model to hopefully fix the issue, on certain computers, where the client does NOT start refreshing after a server start. So far it has worked 50 times in a row on a computer where it didn't work 100% of the time previously, so it looks good.
- FIXED (Client) - "Mass Destruction" Map shows the correct teams/flags now.
- FIXED (Client) - When an admin uses !setnext (map), in-game, the Map Control on the client properly moves the Next Map Indicator to the appropriate map.
- FIXED (Client) - The "Enabled" field in the user accounts grid is visible again.
- ADDED (Client) - !setnext and !change (in game map commands) now can accept a Map Index (integer) or Map String (can be partial)
- FIXED (Daemon) - In-Game Ban Commands was banning in minutes instead of seconds, the command still accepts minutes but the Daemon now properly sets the bantime in seconds (minutes * 60).
- ADDED (In-Game Admin) - Admins will see an "ERROR" Warning when inputing Invalid Commands.
- ADDED (Client) - Added Correct SF Flag Icons
- ADDED (Scripts + Client) - Added SF Vehicle Names to Client
- CHANGED (Daemon) - The Running Map List in the Map List section now shows you whether you are looking at the "Current Map List from Server" or if you are looking at "Map List from Profile: ProfileName". This makes it much easier to understand what you are looking at. Remember: When you load a settings form or a map list form while the BF2 server is running, the client will always show you the settings/maps queried directly from the server. To see the settings/maps that are stored in the Profile (the profile drop down on the dashboard control) you need to click the Green "Refresh Current Profile" button next to the profile dropdown. Obviously, when the server is stopped, you are always looking at profile settings.
- CHANGED (Daemon) - The daemon now disabled MM's Team Swap by default by writing "mm_clanmatch.roundSwitch 0" to the modmanager.con file.
- CHANGED (Daemon) - The daemon now comments out the default MM Auto-Message "Server Rules: No team killing...." etc.
- CHANGED (Daemon) - Removed +modpath command line parameter from the Daemon because it is no longer needed.
- CHANGED (Daemon) - Daemon now ignores any
field in the config.xml file because it is no longer needed. - ADDED (Daemon) - Command Line Param "-debugIGA" to add extra debug information for In Game Admin (To figure out why it won't work on some systems).
- FIXED (Daemon) - Disabling/Enabling Auto-Messages works again (Both the Global On/OFF and each messages's own "Enabled" propertly.
- CHANGED (Client) - Users are informed that they can NOT register an admin's hash for in-game admin if they have unapplied changes in their user accounts form. Also, if the user accounts form is open while they register an admin's hash, the accounts will refresh to show the newly registered hash under the hash column.
- FIXED (Client) - Hashes are now removed from the User Properties table when users are deleted. This will prevent an old/different hash from being automatically registered to a new user account with the same name as an old deleted user.
- FIXED (Daemon) - A Bug where admins were trying to ban using a negative ban time. This may have been screwing up the ban system.
- FIXED (Deamon) - A Bug where an old profile caused the daemon to crash because of null mod.
die werde ich bei gelegenheit bei uns auf dem Server auch mal installieren.
newa
pfffff!