Configuration

Configuration

AET stores its settings in config/anextratouch.cfg. On the client, open Mods > An Extra Touch > Config to edit them. The category pages document all settings, including defaults, units, accepted values and list formats.

Where to configure features

The config screen groups settings into feature menus and submenus matching the wiki sections, such as Camera Overhaul > General camera behavior, Turning roll, and Idle sway. Standalone toggles, such as boat controls and cake particles, sit directly in their feature menu. The file keeps its existing categories and keys, so saved configurations remain compatible.

Visual effects, local sounds, camera behavior and GUI animations are client settings. Trampling and Blizz snow placement run on the server, including the integrated server in single player. Boat controls should use matching client and server settings. Server installation also improves timing for other entities' armor and rain footsteps. Settings are not automatically synchronized between client and server.

Saving and reloading

Finish with Done on the main AET config screen to save and reload changes made in its submenus. To edit the file directly, close the game or server first so a later save does not overwrite your edits.

/aet_reload reloads the running server's config and requires permission level 2, normally an operator. It does not reload a remote player's local file. Use the GUI or restart the client for local visual changes. Restart the game or server after changing server armor/rain entity lists or trampling filters, which are cached. printMobNames also requires a restart because it runs during startup.

AET uses its own config file. It does not import AnExtraDrop settings.

Reading the tables and editing lists

Defaults describe a fresh configuration. Numeric ranges are inclusive. Boolean settings accept true or false; integer settings take whole numbers and float settings allow decimals. Times use the units stated on each row: Minecraft ticks normally run at 20 per second, GUI animations use milliseconds, and trampling expiry uses minutes.

Forge string lists contain one entry per line, without commas or quotes. For example, these footprint settings allow only players and cows:

footprints {
    B:entityClassListIsBlacklist=false
    S:entityClassList <
        Player
        Cow
     >
}

Keep semicolons inside individual override entries. For example, Creeper;;0.5; is one footprint override with two fields left empty. Most entity lists use registered names such as Cow or Player; the splash blacklist instead uses Java simple class names such as EntityXPOrb. Block and item lists use registry names such as minecraft:stone. Fluid and biome lists have their own documented formats.

An empty blacklist allows all supported entries, while an empty whitelist allows none. Lists with separate whitelist and blacklist options explain which takes priority on their feature page.

Category index

Config category	Feature article
footprints	Footprints
breath, wetness	Entity effects
armor, rain_splash, dynamic_surroundings, thunder, item_sounds	Sounds
water_splash, fluid_interactions	Water effects
waves	Coastal Waves
camera	Camera Overhaul and Shoulder Surfing additions
smooth_gui	Smooth GUI
general, trampling	Gameplay
misc	Cake effects, loading bar, Blizz snow
debug	Debugging, below

The wiki groups related features for readability. The config file keeps its existing category names; both camera articles use camera.

Debugging

Config category: debug.

Enable printMobNames and restart to find registered entity names in the log for your installed mods. Disable it again when finished. debugMode enables diagnostic logging.

Setting	Default	Range or format	Effect
debugMode	false	true / false	Enable debug logging
printMobNames	false	true / false	Print all registered mob class names to the log during postInit. Useful for configuring entityClassList and entityOverrides.