One of the rather unique things about Core is it does not function of a normal INI. Core is database driven entirely with the exception of loot control.
Because there are no INIs to edit, Core takes a different approach to making adjustments to how things operate.
Changing a Setting
There are 2 basic methods for changing a setting within core.
The first is with the built in commands that come with Core. There are several hundred scattered throughout the macro. Some are specific to a Class, or how combat is done, or casting and some are strictly environment settings for how Core operates. All of these are found throughout the menu.
an example of a built in command:/core auto
This command is both a toggle and can use an on or off value. Depending on your choice it will turn core on automatic or to manual mode.
/edit
The second is with the /edit
command. This command gives you direct edit access to the database values for Core.
An example of using the /edit
command:/edit coreAuto TRUE
will set Core into automatic mode. Setting it to FALSE would turn Core to a completely manual mode.
A lot of variables used in Core are lists of one sort or another. All lists follow the same pattern: |Item1|Item2|Item3|Item4|andsoon
.
The |
is used as a delimiter and a parsing mechanism. All lists will start with a pipe.
/edit
can be used to adjust single items within a list; to add or delete them as needed reset the variable to a default value or simply adjust to whatever you like.
Lets say Item2 in the example sucks as as a clickie and we no longer want it being cast./edit ListVariableName "Item2" delete
Now the list will look like |Item1|Item3|Item4|andsoon
.
Other /edit
options are gem
and cursor
./edit ItemNow1 cursor
would add whatever is on your cursor to the variable ItemNow1./edit healRemedy1 4 gem
would add whatever is in gem 4 to the healRemedy1 variable. Hopefully its a heal.
Unlike an INI, changing these settings take immediate effect. There is no need to restart the macro. They simply work.