Script configuration parameters
Rerolling script uses proll2.ini file to read configuration
parameters and store strength cache. If it can not find this file,
it will create one with default values for all configuration parameters.
The following configuration parameters are available for tweaking:
Common section:
- window_title - title of the game window to operate;
- primary_mouse_button - which mouse button will be clicked
(left or right);
- mouse_click_down - how long in milliseconds to hold mouse
button pressed;
- mouse_click_delay - how long to wait after releasing mouse
button;
- mouse_speed - how fast to move mouse, use 0
for instant movements. Setting this value too low may break
script;
- number_of_clicks - how much mouse button clicks to make,
when there are no other means to find out that mouse click
was noticed by the game;
- zero_update_delay - delay in arbitrary units after clicking
mouse button and before testing for response from the game;
- first_update_delay - delay in the same arbitrary units
if no response on mouse click was noticed when zero delay has expired;
- second_update_delay - delay in milliseconds, if there
was no response after both zero and first delays have expired.
This value should be large enough to guarantee that game window
is updated if mouse click was noticed by the game;
- gui_delay - interval between closing any script dialog
and generating any activity in the game window - attempt
to avoid sending trash events to the game window;
- update_every - how often to update rerolling progress
display. Setting this to 1 will update statistics after each
roll, while setting to higher values may improve rerolling
speed for a couple of milliseconds;
- tune_every - how often to attempt to decrease update delay
values. Script may increase delays after each iteration,
if it could not detect any reaction on mouse click after hitting
Reroll button, but it will try to decrease delays only as often,
as this parameters says;
- learn_strength - set this parameter to 1 to make script
reroll abilities without saving best combinations, which allows
filling strength cache faster;
- impurity_limit - minimum allowed impurity.
Script will not even look at abilities with impurity higher that this one
(impurity means how much points should be added to abilities
to make best possible score for current character type);
- strength_limit - maximum allowed strength;
- max_iter - maximum number of iterations, script will
pause when this number of iterations without improvent in abilities
has passed;
- max_time - maximum execution time for reroll process
after Continue rolling? dialog;
- rolls_num - number of rolls between randomly moving
mouse point around the screen;
- rest_time - how long in milliseconds to randomly move
mouse pointer around the screen;
- use_hash_table - when set to 1, script will use
hash tables to optimize access to caches of abilities and strength,
and gain no noticable improvement in speed;
- use_profiler - when set to 1, it will output some
profiling information for some time critical places;
- save_stats - when set to 1, it will save statistical
information useful for mathematicians and gamblers;
- stats_prefix - filename prefix for statistical data,
number of distinct values for each ability is also appended to
the filename, so statistics for each character class may be
written in different file for different classes.
Cache section:
- size - strength cache size, in other words, number of
distinct cached strength values;
- strN - checksum of strength image that was saved in
cache slot N;
- valN - strength value entered by user and saved in
cache slot N.
You can remove entire Cache section, then script may ask strength
values on next executions and refill its cache, which might be
necessary if you are using script for different versions of
Baldur's Gate (for example, Baldur's Gate,
Baldur's Gate 2: Shadows of Amn etc).