alttpr-python/docs/Customizer.md

Customizer Files

A customizer file is yaml file with different settings. This documentation is intended to be read with an example customizer file.

This can also be used to roll a mystery or mutli-mystery seed via the GUI. Example

The cli includes a couple arguments to help:

--print_custom_yaml will create a yaml file based on the seed rolled. Treat it like a spoiler.

--customizer takes a file as an argument.

Present on the GUI as Print Customizer File and Customizer File on the Generation Setup tab.

meta

Supported values:

• players: number of players
• seed: you can set the seed number for a set experience on things that are randomized instead of specified
• algorithm: fill algorithm
• names: for naming mutliworld players

Not Yet Implemented

• mystery: indicates the seed should be treated as a mystery (hides total collection_rate) (This may end up player specific)

settings

This must be defined by player. Each player number should be listed with the appropriate settings.

in each player section you can set up default settings for that player or you can specify a mystery yaml file.

1: player1.yaml 
2:
  shuffle: crossed
  door_shuffle: basic   

Player 1's settings will be determined by rolling the mystery weights and player 2's setting will be default except for those two specified in his section. Each settings should be consistent with the CLI arguments.

Start inventory is not supported here. It has a separate section.

Not Yet Implemented

Rom/Adjust flags like sprite, quickswap are not outputing with the print_custom_yaml settings

item_pool

This must be defined by player. Each player number should be listed with the appropriate pool.

Then each player can have the entire item pool defined. The name of item should be followed by the number of that item in the pool. All key items need to be listed here for now.

Bottle (Random) is supported to randomize bottle contents according to those allowed by difficulty. Pendants and crystals are supported here.

Known Issues

1. Dungeon items amount can be increased but not eliminated (as the amount of each dungeon item is either pre-determined or calculated by door rando) and these extra items may not be confined to the dungeon
2. Door rando removes Red Rupees from the pool to make room for extra dungeon items as needed.
3. Shopsanity appends extra shop items to the pool.
4. Beemizer runs after pool creation changing junk items into bees
5. Retro + Shopsanity adds more items to the pool
6. Retro + either of dropshuffle or pottery adds keys to the pool
7. Most pottery settings add a large amount of junk items to the pool

placements

This must be defined by player. Each player number should be listed with the appropriate placement list.

You may list each location for a player and the item you wish to place there. A location name requires to be enclosed by single quotes if the location name contains a # (Most pot locations have the #). (Currently no location names have both a ' and a # so you don't need to worry about escaping the ')

For multiworld you can specify which player the item is for using this syntax:

<item name>#<player number>

Example: Pegasus Boots#3 means the boots for player 3.

entrances

This must be defined by player. Each player number should be listed with the appropriate sections. This section has three primary subsections: entrances, exits, and two-way.

two-way

two-way should be used for connectors, dungeons that you wish to couple. (as opposite to decoupled in the insanity shuffle). Links house should be placed using this method as is can be decoupled logically. (Haven't tested to see if it works in game). The overworld entrance is listed first, followed by the interior exit that it leads to. (The exit will then be linked to exit at that entrance).

50 Rupee Cave: Desert Palace Exit (North) The 50 Rupee entrance leads to Desert North entrance, and leaving there will spit you out at the same place.

exits

exits is used for the Chris Houlihan Room Exit and connectors and dungeons that you wish to be decoupled from their entrances. Perhaps counter-intuitively, the exit is listed after the entrance from which it emerges.

Light Hype Fairy: Chris Houlihan Room Exit leaving Chris Houlihan Room will spit you out at the Light Hype Fairy.

(I can easily switch this syntax around if people would like me too)

entrances

entrances is used for single entrances caves, houses, shops, etc. and drops. Single entrance caves always exit to where you enter, they cannot be decoupled. Dungeons and connectors which are decoupled can also be listed here.

Chicken House: Kakariko Shop if you walk into Chicken House door, you will in the Kakariko Shop.

Known Issues

Chris Houlihan and Links House should be specified together or not at all.

doors

This must be defined by player. Each player number should be listed with the appropriate sections. This section has three primary subsections: lobbies and doors.

lobbies lists the doors by which each dungeon is entered

<lobby name>: <door name> Ex. Turtle Rock Chest: TR Lava Escape SE

doors lists pairs of doors. The first door name is listed is the key. The value of this object may be the paired door name or optionally it can have two properties: dest and type. If you want a type, you must use the second option.

The destination door is listed under dest Supported types are Key Door, Bomb Door, and Dash Door

Here are the two examples of the syntax:

Hyrule Dungeon Guardroom Abyss Edge: Hyrule Castle Lobby W

Sewers Rat Path WS:
        dest: Sewers Secret Room ES
        two-way: true
        type: Key Door

You'll note that sub-tile door do not need to be listed, but if you want them to be key doors you will have to list them.

Not Yet Implemented

one-way to indicate decoupled doors

Known Issue

If you specify a door type and those doors cannot be a stateful door due to the nature of the supertile (or you've placed too many on the supertile) an exception is thrown.

medallions

This must be defined by player. Each player number should be listed with the appropriate info.

Example:

Misery Mire: Ether
Turtle Rock: Quake

Leave blank or omit if you wish it to be random.

bosses

This must be defined by player. Each player number should be listed with the appropriate boss list.

This is done as <dungeon>: <boss>

E.g. Skull Woods: Helmasaur King for helmacopter. Be sure to turn on at least one enemizer setting for the bosses to actually be randomized.

startinventory

This must be defined by player. Each player number should be listed with a list of items to start with.

This is a yaml list (note the hyphens):

startinventory:
    1:
      - Pegasus Boots
      - Progressive Sword

To start with multiple copies of progressive items, list them more than once.

Known Issue

This conflicts with the mystery yaml, if specified. These start inventory items will be added after those are added.