Spiel konfigurieren · YAML-Editor

Baldur's Gate 3 konfigurieren

Zum Spielekatalog

Baldur's Gate 3 · World 0.7.1 · Paket 0.7.1 · Core 0.6.8
Optionsschema und YAML-Strukturprüfung verfügbar · Servergenerierung freigegeben. Separater Multiworld-/Spielclient-Teststatus

Stelle deine Optionen ein und lade die fertige Spieler-YAML herunter. Bei freigegebenen Worlds startet die isolierte Core-Prüfung beim Speichern in einem eigenen Lobby-Slot; eine erfolgreiche Seedgenerierung wird separat geprüft.

Ersetzt den Entwurf nach Bestätigung.

Entwurf · noch nicht durch den Core geprüft

Game Options · 25 Optionen
progression_balancing
Hilfe · Gewichtung möglich

A system that can move progression earlier, to try and prevent the player from getting stuck and bored early. A lower setting means more getting stuck. A higher setting means less getting stuck.

World-Standard: 50

accessibility
Hilfe · Gewichtung möglich

Set rules for reachability of your items/locations. **Full:** ensure everything can be reached and acquired. **Minimal:** ensure what is needed to reach your goal can be acquired.

World-Standard: 0

goal
Hilfe · Gewichtung möglich

(Dev note: Progression Balancing is recommended to be 0) Determines what location counts as victory. These goals also determine how many level ups are placed in the pool- Rescue Halsin: Level Cap 5 - goal is to rescue Halsin and return him safely to the Grove. Kill Inquisitor Wwargaz: Level Cap 8 - goal is to kill Inquisitor Wwargaz in the Creche. The space laser does not count. Act 1 user defined fights: Level Cap 8 - goal is to defeat selected bosses (see UserDefinedFights). Kill Myrkul: Level Cap 10 - goal is to kill the Avatar of Myrkul at the end of Act 2. Act 2 user defined fights: Level Cap 10 - goal is to defeat selected bosses (see UserDefinedFights). Kill the Nether Brain: Level Cap 12 - goal is to kill the Nether Brain at the end of Act 3. UNTESTED. Act 3 user defined fights: Level Cap 12 - goal is to defeat selected bosses (see UserDefinedFights). UNTESTED.

World-Standard: 0

user_defined_fights
Hilfe

If using a User Defined Fights goal, select which fights are required to complete the goal. Act 2 fights require the act2_user_defined_fights goal to be selected. Act 3 fights require the act3_user_defined_fights goal to be selected. Act 1 fights are Auntie Ethel - Ch'r'ai W'wargaz, Act 2 fights are Shambling Mound - Myrkul, Act 3 fights are everything past Myrkul.

World-Standard: ["Auntie Ethel", "Balthazar", "Bulette", "Ch\u0027r\u0027ai Tska\u0027an", "Ch\u0027r\u0027ai W\u0027wargaz", "Cursed Kuo-Toa Chief", "Gerringothe Thorm", "Grym", "Malus Thorm", "Myrkul", "Nere", "Netherbrain", "Shambling Mound", "Spectator", "Spider Queen", "Thisobald Thorm", "Yurgir"]

killsanity
Hilfe · Gewichtung möglich

Whether kills of individual creatures should be locations. Kills do _not_ count if they are done by falling damage or by being thrown into a chasm. Currently the only option is "All Nonmissable Hostiles" - The intent was all monsters that are either default or story-forced hostile, and are not likely to be missed by advancing plot. There still do exist some fights that are technically missable (paladins, Nere, etc), but only by transitions that have explicit warnings on them. Nonmissable Hostiles Location count - Halsin: 156, Wwargaz: 287, Myrkul: 535, Netherbrain: Not implemented yet

World-Standard: 0

killsanity_strictness
Hilfe · Gewichtung möglich

If Killsanity is on, determines how strict the requirements are for a kill to count as a location. Strict: Only kills by player characters count. Normal: Only kills count. This is the default. Relaxed: As long as they die, it counts.

World-Standard: 1

questsanity
Hilfe · Gewichtung möglich

Whether quest updates should be locations. Some locations may be buggy or missable- please tell the BG3 channel if any quest doesn't complete that you think should've. Due to the nature of the branching of BG3 paths, many quests had to have choices as to what options were viable. Currently the only option is "Most Content" - skill checks are not expected to be passed _unless_ future content depends on it. Most Content Location count - Halsin: 180, Wwargaz: 284, Myrkul: 350, Netherbrain: Not implemented yet

World-Standard: 1

containersanity
Hilfe · Gewichtung möglich

Whether opening containers should be locations. Only value 2 does anything: it turns every openable container placed in a Prologue/Act 1-3 level into a check (~9850 of them). Exists for testing. Don't do this. Very unstable, likely broken. Containersanity location count - Halsin: 1799, Wwargaz: 2556, Myrkul: 4809, Netherbrain: 9972

World-Standard: 0

statsanity
Hilfe · Gewichtung möglich

Whether stats should be items. Currently unimplemented. If selected, all characters start at all stats at 8 and you must get stats from the multiworld. This is currently only in testing. Tav only stats: Only Tav's stats are randomized, and the companions' stats are left alone. Party slots: Stats are only applied to party slots, and not the characters. Rearranging the party will rearrange stats. Universal stats: Stats are not character specific, and all characters get the same stat boosts when a stat item is received. Character stats: Stats are character specific, and each character's stats are randomized separately.

World-Standard: 0

statsanity_boost_by
Hilfe · Gewichtung möglich

If Statsanity is on, determines how much each stat item boosts the stat by. Halsin requires stats at 12, Wwargaz requires stats at 16, Myrkul requires stats at 20. The number of item slots taken will be characters * 6 * (required_stat - 8) / boost_amount, so for example if boost_amount is 2, goal is Myrkul, and party_slots is chosen, the number of items taken will be 4*6*6 = 144 (this is the highest option). Even numbers only, please.

World-Standard: 2

characters_in_logic
Hilfe

Which characters the generator should assume you will recruit. A character NOT listed here has their character-specific plot events removed from the location pool: locations named "<Character>: ..." and any "Recruit <Character>" location (e.g. removing Lae'zel drops "Lae'zel: Deal with Patrol" and "Beach-LZ: Recruit Lae'zel"). If Questsanity is on, determines which characters' quest completions are included in logic. Currently in testing - not considered stable. In particular Halsin seems required through act 2.

World-Standard: ["Astarion", "Gale", "Halsin", "Karlach", "Lae\u0027zel", "Minthara", "Shadowheart", "Wyll"]

deathlink
Hilfe · Gewichtung möglich

If true, when a player dies, all players receive an item that kills them. Currently in testing.

World-Standard: false

deathlink_consequence
Hilfe · Gewichtung möglich

If Deathlink is on, determines what happens when a player receives a deathlink. Kill: The player dies immediately. Knockout: The player is knocked out.

World-Standard: 0

sync_method
Hilfe · Gewichtung möglich

Determines how AP items will be delivered into BG3. With a current mod and client, items are delivered automatically within about a second regardless of this choice, and the AP Sync scroll remains as a manual "force a sync now" button. This option only changes behavior with an OLD mod version (no sync timer): Scroll_Tav - Items will only be generated when the scroll is cast, and placed in Tav's inventory. Any_action_Tav - Items will be generated when ANYBODY takes ANY action that the game considers worth triggering the listener flag for (which is most things).

World-Standard: 1

add_act1a_treasure
Hilfe · Gewichtung möglich

Adds 26 items into the pool.

World-Standard: true

add_act1b_treasure
Hilfe · Gewichtung möglich

Adds 62 items into the pool.

World-Standard: true

add_act2_treasure
Hilfe · Gewichtung möglich

Adds 103 items into the pool.

World-Standard: false

add_act3_treasure
Hilfe · Gewichtung möglich

Adds 191 items into the pool.

World-Standard: false

trim_treasure_method
Hilfe · Gewichtung möglich

The standard method of having 1:1 items:locations does not work for BG3. Each option instead lists how many locations or items they add. Locations are filled with progression first, then useful, and if there is room left, filler. If there are not enough locations for all of the useful items, they will be trimmed. This option determines how this trimming is done. - Remove Later Treasure First: Removes treasure items that are found later in the game first. This is the recommended option for a more balanced playthrough. - Remove Random Treasure: Removes treasure items at random.

World-Standard: 0

additional_level_ups
Hilfe · Gewichtung möglich

For an easier play through, this adds items to support additional levels into the pool. Not recommended. Each level up requires 4 fragments, so if you add 40 fragments, there will be 10 additional level ups available. Logic does not account for these- you are still expected to be able to clear the locations at the expected levels.

World-Standard: 0

traps_percentage
Hilfe · Gewichtung möglich

What percent of filler items should be traps.

World-Standard: 0

local_fill_percent
Hilfe · Gewichtung möglich

What percent of your filler and trap items are placed in your own world instead of being shuffled into the multiworld. Useful with large location counts (containersanity especially), which would otherwise flood every other player's pool with BG3 lockpicks and healing potions. Items named in local_items or non_local_items are left alone. Does nothing in a single player game.

World-Standard: 0

enabled_traps
Hilfe

Which kinds of traps should be enabled.

World-Standard: ["Bleeding", "Blinded", "Clown", "Confusion", "Monster", "Stun", "Sussur"]

block_entrances
Hilfe · Gewichtung möglich

If true, there will be barriers placed in the world that block advancement until a required item is received. This is currently in testing and may be buggy.

World-Standard: false

dev_debug_on
Hilfe · Gewichtung möglich

If true, logs debug items in debug.json

World-Standard: false

Item & Location Options · 9 Optionen
local_items
Hilfe

Forces these items to be in their native world.

World-Standard: []

non_local_items
Hilfe

Forces these items to be outside their native world.

World-Standard: []

start_inventory
Hilfe

Start with the specified amount of these items. Example: {Bomb: 1, Arrow: 3}

World-Standard: {}

start_hints
Hilfe

Start with these item's locations prefilled into the ``!hint`` command.

World-Standard: []

start_location_hints
Hilfe

Start with these locations and their item prefilled into the ``!hint`` command.

World-Standard: []

exclude_locations
Hilfe

Prevent these locations from having an important item.

World-Standard: []

priority_locations
Hilfe

Prevent these locations from having an unimportant item.

World-Standard: []

item_links
Hilfe

Share part of your item pool with other players.

World-Standard: []

plando_items
Hilfe

Generic items plando.

World-Standard: []

YAML / Expertenansicht

Gewichtete Spiele/Namen, Trigger, Linked Options und komplexe Werte bleiben erhalten. Formularänderungen schreiben die YAML neu und ersetzen ihre Formatierung und Kommentare. Ohne Änderung bleibt der Originaltext erhalten.

Gewichtungen und exotische Optionen werden als „Erweiterte Option“ dargestellt. Ungültige und unbekannte Werte werden nicht automatisch korrigiert. Die Schema-Prüfung ersetzt die isolierte Core-Prüfung nicht.

Sichere YAML-Grenzen

2 MiB, keine Aliase/Anker oder doppelten Schlüssel; 32 Auswahlwerte, 32 Trigger/Linked-Options und 128 Optionsblöcke. requires.version und requires.game werden geprüft. Optionswerte werden beim Slot-Upload mit World.from_any/verify und acht Core-Würfelproben je World geprüft. Gemeinsame Platzierung, endgültige Namen und Generierbarkeit stehen erst nach erfolgreicher Seedgenerierung fest.

„Konfiguration speichern“ speichert einen Entwurf pro Spiel und Konto ausschließlich in diesem Browser. Auf gemeinsam genutzten Geräten danach löschen. Für eine unabhängige Kopie YAML herunterladen. Bei einem World-Update werden Schemaänderungen vor dem Laden angezeigt.

Anmelden und eine Lobby öffnen, um die YAML einem eigenen Slot zuzuweisen. Die Core-Prüfung ist für freigegebene Worlds verfügbar.