Batch Tools

Batch tools are available for users that frequently work on several characters together. This is especially meant to ease the common operations when working on several Rage character that all represent the same in-game character, but corresponding to different fight conditions and/or different specs.

Getting Started

You can start using batch tools after you have defined all the Rage profiles that you want to work with. You can start the batch tools from Tools > Batch Tools. You will be presented with a list of characters that is initially empty and optimization controls. You can create a batch list by using File > Import and selecting several character xml files or clicking on ... button to add them one by one. Characters will use whatever model they were last saved with. After your list is complete you can save it with File > Save so that you can quickly reopen it in later sessions.

In the list each character shows its current score, weight, new score and a button to show the character in main Rage window. Be careful when displaying characters while you have some other character open from before. The previous character will be put aside and you will only be able to work on it again after you close the batch tools (at that point the batch character will be hidden and the character that was loaded before starting batch tools will appear again). Note that if you add a character to the list that was also opened in the Rage that those two will be treated as two different characters, changes made to one will not show in the other.

Batch tools are best suited if you mark your item availability with specific available items (using blue diamonds and mod restrictions). When you make changes to the item availability you can use Tools->Set Available Items to quickly copy available items from currently shown character to all characters in the list. If the changes made some equipped items unavailable you can use Tools->Replace Unavailable to correct those changes (for example if an item changes mods it will replace previous version with the currently available one).

At the core of batch tools are the optimization functions. Tools->Optimize will simply run optimize on each character in the list with the currently selected settings. One change from doing it manually is that it will try running optimize several times (up to max defined with the Max Rounds slider, default 3) if it is not able to match current score of the character. It will also retry optimize when it finds a new optimum (and reset the max rounds count). This way you can combat the inherent problem that optimizer cannot guarantee to find the optimum solution in a single run. After the optimizer finds a better solution it will display this in the New Score column and marking character name with a *. You can then either save all characters with Tools->Save Characters or save a copy of them with Tools->Save Characters As Copy which will append a timestamp to character file names.

Last function is build upgrade list. It functions a bit differently than running build upgrade list separately on each character. It won't create separate upgrade lists for each fight condition, instead it will look at upgrades and see how much of an upgrade it provides for each of them and compute a weighted average using the specified weight. It forces the same modding of an item to be evaluated for all characters and only then it computes the average. If you would run upgrade list separately you might get which modding is best in each of the setups, this way you get which is best overall. It will also correctly take into account that for example remodding currently available item might rise value on one character, but drop it on another character. At the same time if the item is not used in the best setup of the other character then it will correctly identify that changing mods creates no difference for that character. This can help in identifying alternative moddings for items that you're no longer using for most common situations.

Last edited Mar 11, 2012 at 5:54 AM by KeithJRome, version 1

Comments

No comments yet.