Profiles

General usage

Profiles allow you to store the current configuration and load it at a later time. By default, AT comes with 10 different profiles - the maximum amount of profiles one can have is 64. Sufficient profile management is achieved with the the following commands:

Description	Cheats enabled	Without cheats
Save configuration at profile <name>	/function at-prof:save {name:foo}	/trigger save-profile set 1
View configuration of profile <name>	/function at-prof:view {name:foo}	/trigger view-profile set 3
Load profile <name>	/function at-prof:load {name:foo}	/trigger load-profile set 5
Remove profile <name>	/function at-prof:delete {name:foo}	/trigger delete-profile set 7
List existing profiles	/function at-prof:list	/trigger list-profiles

Note: Loading a profile can be simplified by left-clicking on the command output of the list command. Just click on the profile you would like to try out (either on the name or its [index], for /trigger command) to automatically suggest the corresponding profile load command.

Using /trigger

While profile management using /function is consistent, meaning that you can save, load, etc to / from the same name, and will always access the same profile, management using /trigger is not. It's designed this way to give players without cheats the ability to access existing (pre-made) profiles.

With triggers it works like this: The score you enter at the save gets appended behind “trigger”, forming a unique name like “trigger0” or “trigger42”, so saving works as expected.

Loading is a bit different though. To load the profile, you first need to know its index, which you can obtain by entering the list command. (the number in square brackets []) If you have decided what profile you want to have, run the load command with the index behind your profile. The correct profile should now be loaded. The same principle also applies to the view and delete command.

This functionality may change at a later time, if / when I have a better idea for solving this issue.