As already mentioned it is now time to add some content to the buddy list. The account management was the most important one so this will be available with this update. The next time you may see a chat functionality and group management that may also effect the game.
[FEATURE] Auto login added for the buddy list.
[FEATURE] It is now possible to remove a buddy from the list.
[FEATURE] It is now possible to request a new password for a buddy list account.
[FEATURE] It is now possible to change the preferences (Username, Email, Password) of a buddy list account.
[IMPROVEMENT] Offline contacts are now displayed in grey color within the buddy list.
[BUGFIX] Some issues with the buddy list were corrected. (But most of them were on the server side and are fixed since a few days after the last update.)
[BUGFIX] Crash when closing Armarize from within the serverbrowser and the filter settings could not be saved.
[BUGFIX] Crash when closing Armarize and a background operation is about to be exiting.
If you have already installed Armarize, just start it. Otherwise:
Unfortunately no features for the contact list this time. I had not as much time as expected to work on Armarize but instead I played ArmA2 a bit more often than in the last months. (DayZ is just fascinating, isn't it? ) So this update got some improvements and features mostly for the serverbrowser and the launch of the game.
The next update probably includes support for Armed Assault, Take On Helicopters, (Cold War Assault aka OFP?) and... ArmA3, to be prepared for the upcoming alpha.
[FEATURE] You can now search for a modification within the modification management.
[FEATURE] The server where a buddy is playing on can now be highlighted within the browser.
[FEATURE] New type of mod selection added wherewith only those modifications defined within a profile are loaded.
[FEATURE] It is now possible to configure how modifications are selected when joining a server without the context menu.
[CHANGE] Support for the new game types on the Six-Rsync-Network added.
[BUGFIX] The value entered in the modification filter was not saved within the selected profile.
[IMPROVEMENT] When not using automatic mod selection a user will not be notified about client/server differences anymore.
If you have already installed Armarize, just start it. Otherwise:
Well, I could not hold my promise once again so I think it would be better not to promise anything this time... However, I was able to integrate a massive improvement to the serverbrowser with this update. Due to some more experience in network programming I have reworked the parts of Armarize which are responsible for the communication with Gamespy.
The result is a reduction of the refresh duration by a factor of 2 to 3. This certainly means that the network and cpu load has been increased, but I adjusted it as effectively as possible so that no one with at least 1024kbit/128kbit should experience any issues. This will probably configurable in the future wherewith users with a better connection are able to decrease the duration even greater. (uh oh, yet another promise... )
[IMPROVEMENT] Some minor interface changes to make it more intuitive.
[IMPROVEMENT] It is now possible to manually add a new favorite gameserver.
[IMPROVEMENT] Decreased serverbrowser refresh duration by a factor of 2 to 3.
[IMPROVEMENT] For every single gameserver will now a (pseudo)ping be displayed.
[IMPROVEMENT] The gameserver favorites and history are now refreshed when entering the serverbrowser even when the automatic refresh has been disabled.
[IMPROVEMENT] When connecting to a gameserver per ip and port it will now be displayed as history entry even when the automatic refresh has been disabled.
[BUGFIX] The automatic browser refresh has not been disabled when minimizing Armarize while the game was running.
[CHANGE] The status notification sound will now also be played when refreshing a gameserver manually.
If you have already installed Armarize, just start it. Otherwise:
This is really nice! Feels a bit incomplete for me as the developer but you have got the core functionality very well. Good job
---------- Post added at 21:12 ---------- Previous post was at 21:11 ----------
Due to some obviously annoying bugs for a few of you and missing translations i decided to make a bugfix release this weekend. It is only an incremental update this time and that is the reason why v1.3.3.0 is still available for download.
[IMPROVEMENT] It is now possible to manually select a mirror for the synchronisation when it was not possible to select one automatically.
[BUGFIX] Crash after closing the synchronisation wizard if it was initiated from within the serverbrowser while a refresh was running.
[BUGFIX] When custom parameters defined within a profile are not correctly formatted a message will be displayed now.
[BUGFIX] Crash during the synchronisation when an error occured while trying to prioritize the available mirrors.
[BUGFIX] Finally... a crash when a profile with a broken modification to load was opened.
[CHANGE] When using the search function of the buddy list you can now search for partial names again.
If you have already installed Armarize, just start it. Otherwise:
If you could give me a list of items you want me to cover I will do a new video tutorial. The one I made was directed towards the shacknews community and I'll gladly make one more that's more generalized and covers all topics.
That would be even nicer! But please use a higher resolution then.
Primarily the listing of features here covers the most important topics. But here are some additional things that I consider to be mentionable:
Browser/Game launch
Steam support *should* work very well as long as Steam itself has been started by the user and not by Armarize.
It is possible to use the servername-, mission- and mod-filter to explicitly exclude words. (Put "-@dayz" in the mod-filter and you wont see any dayz server.)
By default games and applications are not ran as the "same" user Armarize has been started with. If a game or application should be ran with administrator rights it has to be explicitly set.
Below in the listing where the modifications running on a server are displayed, the same colors that are used within the configuration to visualize the "state" of a modification are used. (orange = outdated, red = broken, blue = frozen)
Modifications
The revision that is used to monitor the state of a modification which is available on the six-rsync-network can be deleted by opening the mod dialog. (Right click -> Show details) (Gives finer control about the way Armarize handles the automatic skipping during the synchronisation.) [You can also use it to force Armarize so that it marks a modifcation as outdated with above mentioned color. ]
Settings
The names that are used to display modification directories within Armarize are changeable. (It is not necessary that they have the same name as the ones on the hard disk.)
When splitting the rsync package files from a modification directory, Armarize takes care so that the files are moved correctly to their new location. (Useful when using a SSD with limited capacity.)
Profiles
When marking a modification to load it will be automatically arranged in the list based on its dependencies though that is also manually manageable. (Right click in the list)
When ArmA2 and ArmA2: Operation Arrowhead has been installed separately, CombinedOps will be handled as modification so that it is not necessary to struggle with the commandline.
And of course everything what you has mentioned in your current video.