docs(AOneBlock): explain phase weights and add a phase customization guide

[tastybento]

Why

An admin asked:

in the phases config, what do the numbers represent... as in the numbers after the Material or Entity... I know it is not the number that spawn over the phase, is it a weighting?

They were right, and there was nowhere in the docs that said so. The overview page called them "relative probability" in one tabbed panel, and never mentioned that blocks:, mobs: and custom-blocks: all draw from a single shared pool — so a mob weight is directly comparable to a block weight and pushes every block's percentage down.

What

New page — gamemodes/AOneBlock/Phases.md, "Customizing Phases", added to the nav under AOneBlock. It covers:

• The three kinds of number in a phase file and how to tell them apart: weights (blocks/mobs/custom-blocks), positions (fixedBlocks/holograms keys), and the section name (the top-level '0': key).
• Weights in depth — the weight ÷ phase total formula, a worked example using the exact Winter phase the admin quoted, a table of the real shipped Plains percentages showing blocks and mobs interleaved in one pool, why only the ratio matters, and tuning recipes.
• CHEST as a special case: its weight is the chance of a chest, and rarity is a second roll at the hard-coded 62/25/9/4.
• fixedBlocks and holograms positions, CHEST_WITH_<ITEM>, and the support-block caveat.
• phases_index.yml order/length, and that file-name numbers are only a hint now.
• Commands, placeholders and requirements.
• Chests, with the "build them in game with setchest" advice.
• Custom blocks — including that probability: is a weight in the same pool — and the quoting and spawner-timing gotchas.
• Version gating at phase, block and mob level.
• A step-by-step "build a new phase" walkthrough.
• A troubleshooting table keyed off the actual log messages the addon emits.

Overview page fixes (gamemodes/AOneBlock/index.md):

• blocks tab now says "weight", explains the raffle, and notes CHEST's two-stage roll.
• mobs tab gains a warning that mob weights share the block total, with the real Plains numbers.
• Custom Blocks tab notes that probability is a weight in the same pool, and documents the custom-blocks: sibling list.
• A pointer to the new page at the top of "Phase Config Files".

Companion change in AOneBlock itself rewrites the comments in the shipped 0_plains.yml, which is where admins look first.

mkdocs build passes; all new internal links and anchors resolve.

[tastybento]

Why

An admin asked:

in the phases config, what do the numbers represent... as in the numbers after the Material or Entity... I know it is not the number that spawn over the phase, is it a weighting?

They were right, and there was nowhere in the docs that said so. The overview page called them "relative probability" in one tabbed panel, and never mentioned that blocks:, mobs: and custom-blocks: all draw from a single shared pool — so a mob weight is directly comparable to a block weight and pushes every block's percentage down.

What

New page — gamemodes/AOneBlock/Phases.md, "Customizing Phases", added to the nav under AOneBlock. It covers:

• The three kinds of number in a phase file and how to tell them apart: weights (blocks/mobs/custom-blocks), positions (fixedBlocks/holograms keys), and the section name (the top-level '0': key).
• Weights in depth — the weight ÷ phase total formula, a worked example using the exact Winter phase the admin quoted, a table of the real shipped Plains percentages showing blocks and mobs interleaved in one pool, why only the ratio matters, and tuning recipes.
• CHEST as a special case: its weight is the chance of a chest, and rarity is a second roll at the hard-coded 62/25/9/4.
• fixedBlocks and holograms positions, CHEST_WITH_<ITEM>, and the support-block caveat.
• phases_index.yml order/length, and that file-name numbers are only a hint now.
• Commands, placeholders and requirements.
• Chests, with the "build them in game with setchest" advice.
• Custom blocks — including that probability: is a weight in the same pool — and the quoting and spawner-timing gotchas.
• Version gating at phase, block and mob level.
• A step-by-step "build a new phase" walkthrough.
• A troubleshooting table keyed off the actual log messages the addon emits.

Overview page fixes (gamemodes/AOneBlock/index.md):

• blocks tab now says "weight", explains the raffle, and notes CHEST's two-stage roll.
• mobs tab gains a warning that mob weights share the block total, with the real Plains numbers.
• Custom Blocks tab notes that probability is a weight in the same pool, and documents the custom-blocks: sibling list.
• A pointer to the new page at the top of "Phase Config Files".

Companion change in AOneBlock itself rewrites the comments in the shipped 0_plains.yml, which is where admins look first.

mkdocs build passes; all new internal links and anchors resolve.

[tastybento]

Why

An admin asked:

in the phases config, what do the numbers represent... as in the numbers after the Material or Entity... I know it is not the number that spawn over the phase, is it a weighting?

They were right, and there was nowhere in the docs that said so. The overview page called them "relative probability" in one tabbed panel, and never mentioned that blocks:, mobs: and custom-blocks: all draw from a single shared pool — so a mob weight is directly comparable to a block weight and pushes every block's percentage down.

What

New page — gamemodes/AOneBlock/Phases.md, "Customizing Phases", added to the nav under AOneBlock. It covers:

• The three kinds of number in a phase file and how to tell them apart: weights (blocks/mobs/custom-blocks), positions (fixedBlocks/holograms keys), and the section name (the top-level '0': key).
• Weights in depth — the weight ÷ phase total formula, a worked example using the exact Winter phase the admin quoted, a table of the real shipped Plains percentages showing blocks and mobs interleaved in one pool, why only the ratio matters, and tuning recipes.
• CHEST as a special case: its weight is the chance of a chest, and rarity is a second roll at the hard-coded 62/25/9/4.
• fixedBlocks and holograms positions, CHEST_WITH_<ITEM>, and the support-block caveat.
• phases_index.yml order/length, and that file-name numbers are only a hint now.
• Commands, placeholders and requirements.
• Chests, with the "build them in game with setchest" advice.
• Custom blocks — including that probability: is a weight in the same pool — and the quoting and spawner-timing gotchas.
• Version gating at phase, block and mob level.
• A step-by-step "build a new phase" walkthrough.
• A troubleshooting table keyed off the actual log messages the addon emits.

Overview page fixes (gamemodes/AOneBlock/index.md):

• blocks tab now says "weight", explains the raffle, and notes CHEST's two-stage roll.
• mobs tab gains a warning that mob weights share the block total, with the real Plains numbers.
• Custom Blocks tab notes that probability is a weight in the same pool, and documents the custom-blocks: sibling list.
• A pointer to the new page at the top of "Phase Config Files".

Companion change in AOneBlock itself rewrites the comments in the shipped 0_plains.yml, which is where admins look first.

mkdocs build passes; all new internal links and anchors resolve.

[tastybento]

Why

An admin asked:

in the phases config, what do the numbers represent... as in the numbers after the Material or Entity... I know it is not the number that spawn over the phase, is it a weighting?

They were right, and there was nowhere in the docs that said so. The overview page called them "relative probability" in one tabbed panel, and never mentioned that blocks:, mobs: and custom-blocks: all draw from a single shared pool — so a mob weight is directly comparable to a block weight and pushes every block's percentage down.

What

New page — gamemodes/AOneBlock/Phases.md, "Customizing Phases", added to the nav under AOneBlock. It covers:

• The three kinds of number in a phase file and how to tell them apart: weights (blocks/mobs/custom-blocks), positions (fixedBlocks/holograms keys), and the section name (the top-level '0': key).
• Weights in depth — the weight ÷ phase total formula, a worked example using the exact Winter phase the admin quoted, a table of the real shipped Plains percentages showing blocks and mobs interleaved in one pool, why only the ratio matters, and tuning recipes.
• CHEST as a special case: its weight is the chance of a chest, and rarity is a second roll at the hard-coded 62/25/9/4.
• fixedBlocks and holograms positions, CHEST_WITH_<ITEM>, and the support-block caveat.
• phases_index.yml order/length, and that file-name numbers are only a hint now.
• Commands, placeholders and requirements.
• Chests, with the "build them in game with setchest" advice.
• Custom blocks — including that probability: is a weight in the same pool — and the quoting and spawner-timing gotchas.
• Version gating at phase, block and mob level.
• A step-by-step "build a new phase" walkthrough.
• A troubleshooting table keyed off the actual log messages the addon emits.

Overview page fixes (gamemodes/AOneBlock/index.md):

• blocks tab now says "weight", explains the raffle, and notes CHEST's two-stage roll.
• mobs tab gains a warning that mob weights share the block total, with the real Plains numbers.
• Custom Blocks tab notes that probability is a weight in the same pool, and documents the custom-blocks: sibling list.
• A pointer to the new page at the top of "Phase Config Files".

Companion change in AOneBlock itself rewrites the comments in the shipped 0_plains.yml, which is where admins look first.

mkdocs build passes; all new internal links and anchors resolve.

[tastybento]

Why

An admin asked:

in the phases config, what do the numbers represent... as in the numbers after the Material or Entity... I know it is not the number that spawn over the phase, is it a weighting?

They were right, and there was nowhere in the docs that said so. The overview page called them "relative probability" in one tabbed panel, and never mentioned that blocks:, mobs: and custom-blocks: all draw from a single shared pool — so a mob weight is directly comparable to a block weight and pushes every block's percentage down.

What

New page — gamemodes/AOneBlock/Phases.md, "Customizing Phases", added to the nav under AOneBlock. It covers:

• The three kinds of number in a phase file and how to tell them apart: weights (blocks/mobs/custom-blocks), positions (fixedBlocks/holograms keys), and the section name (the top-level '0': key).
• Weights in depth — the weight ÷ phase total formula, a worked example using the exact Winter phase the admin quoted, a table of the real shipped Plains percentages showing blocks and mobs interleaved in one pool, why only the ratio matters, and tuning recipes.
• CHEST as a special case: its weight is the chance of a chest, and rarity is a second roll at the hard-coded 62/25/9/4.
• fixedBlocks and holograms positions, CHEST_WITH_<ITEM>, and the support-block caveat.
• phases_index.yml order/length, and that file-name numbers are only a hint now.
• Commands, placeholders and requirements.
• Chests, with the "build them in game with setchest" advice.
• Custom blocks — including that probability: is a weight in the same pool — and the quoting and spawner-timing gotchas.
• Version gating at phase, block and mob level.
• A step-by-step "build a new phase" walkthrough.
• A troubleshooting table keyed off the actual log messages the addon emits.

Overview page fixes (gamemodes/AOneBlock/index.md):

• blocks tab now says "weight", explains the raffle, and notes CHEST's two-stage roll.
• mobs tab gains a warning that mob weights share the block total, with the real Plains numbers.
• Custom Blocks tab notes that probability is a weight in the same pool, and documents the custom-blocks: sibling list.
• A pointer to the new page at the top of "Phase Config Files".

Companion change in AOneBlock itself rewrites the comments in the shipped 0_plains.yml, which is where admins look first.

mkdocs build passes; all new internal links and anchors resolve.

[tastybento]

Why

An admin asked:

in the phases config, what do the numbers represent... as in the numbers after the Material or Entity... I know it is not the number that spawn over the phase, is it a weighting?

They were right, and there was nowhere in the docs that said so. The overview page called them "relative probability" in one tabbed panel, and never mentioned that blocks:, mobs: and custom-blocks: all draw from a single shared pool — so a mob weight is directly comparable to a block weight and pushes every block's percentage down.

What

New page — gamemodes/AOneBlock/Phases.md, "Customizing Phases", added to the nav under AOneBlock. It covers:

• The three kinds of number in a phase file and how to tell them apart: weights (blocks/mobs/custom-blocks), positions (fixedBlocks/holograms keys), and the section name (the top-level '0': key).
• Weights in depth — the weight ÷ phase total formula, a worked example using the exact Winter phase the admin quoted, a table of the real shipped Plains percentages showing blocks and mobs interleaved in one pool, why only the ratio matters, and tuning recipes.
• CHEST as a special case: its weight is the chance of a chest, and rarity is a second roll at the hard-coded 62/25/9/4.
• fixedBlocks and holograms positions, CHEST_WITH_<ITEM>, and the support-block caveat.
• phases_index.yml order/length, and that file-name numbers are only a hint now.
• Commands, placeholders and requirements.
• Chests, with the "build them in game with setchest" advice.
• Custom blocks — including that probability: is a weight in the same pool — and the quoting and spawner-timing gotchas.
• Version gating at phase, block and mob level.
• A step-by-step "build a new phase" walkthrough.
• A troubleshooting table keyed off the actual log messages the addon emits.

Overview page fixes (gamemodes/AOneBlock/index.md):

• blocks tab now says "weight", explains the raffle, and notes CHEST's two-stage roll.
• mobs tab gains a warning that mob weights share the block total, with the real Plains numbers.
• Custom Blocks tab notes that probability is a weight in the same pool, and documents the custom-blocks: sibling list.
• A pointer to the new page at the top of "Phase Config Files".

Companion change in AOneBlock itself rewrites the comments in the shipped 0_plains.yml, which is where admins look first.

mkdocs build passes; all new internal links and anchors resolve.

[tastybento]

Why

An admin asked:

in the phases config, what do the numbers represent... as in the numbers after the Material or Entity... I know it is not the number that spawn over the phase, is it a weighting?

They were right, and there was nowhere in the docs that said so. The overview page called them "relative probability" in one tabbed panel, and never mentioned that blocks:, mobs: and custom-blocks: all draw from a single shared pool — so a mob weight is directly comparable to a block weight and pushes every block's percentage down.

What

New page — gamemodes/AOneBlock/Phases.md, "Customizing Phases", added to the nav under AOneBlock. It covers:

• The three kinds of number in a phase file and how to tell them apart: weights (blocks/mobs/custom-blocks), positions (fixedBlocks/holograms keys), and the section name (the top-level '0': key).
• Weights in depth — the weight ÷ phase total formula, a worked example using the exact Winter phase the admin quoted, a table of the real shipped Plains percentages showing blocks and mobs interleaved in one pool, why only the ratio matters, and tuning recipes.
• CHEST as a special case: its weight is the chance of a chest, and rarity is a second roll at the hard-coded 62/25/9/4.
• fixedBlocks and holograms positions, CHEST_WITH_<ITEM>, and the support-block caveat.
• phases_index.yml order/length, and that file-name numbers are only a hint now.
• Commands, placeholders and requirements.
• Chests, with the "build them in game with setchest" advice.
• Custom blocks — including that probability: is a weight in the same pool — and the quoting and spawner-timing gotchas.
• Version gating at phase, block and mob level.
• A step-by-step "build a new phase" walkthrough.
• A troubleshooting table keyed off the actual log messages the addon emits.

Overview page fixes (gamemodes/AOneBlock/index.md):

• blocks tab now says "weight", explains the raffle, and notes CHEST's two-stage roll.
• mobs tab gains a warning that mob weights share the block total, with the real Plains numbers.
• Custom Blocks tab notes that probability is a weight in the same pool, and documents the custom-blocks: sibling list.
• A pointer to the new page at the top of "Phase Config Files".

Companion change in AOneBlock itself rewrites the comments in the shipped 0_plains.yml, which is where admins look first.

mkdocs build passes; all new internal links and anchors resolve.

[tastybento]

Why

An admin asked:

in the phases config, what do the numbers represent... as in the numbers after the Material or Entity... I know it is not the number that spawn over the phase, is it a weighting?

They were right, and there was nowhere in the docs that said so. The overview page called them "relative probability" in one tabbed panel, and never mentioned that blocks:, mobs: and custom-blocks: all draw from a single shared pool — so a mob weight is directly comparable to a block weight and pushes every block's percentage down.

What

New page — gamemodes/AOneBlock/Phases.md, "Customizing Phases", added to the nav under AOneBlock. It covers:

• The three kinds of number in a phase file and how to tell them apart: weights (blocks/mobs/custom-blocks), positions (fixedBlocks/holograms keys), and the section name (the top-level '0': key).
• Weights in depth — the weight ÷ phase total formula, a worked example using the exact Winter phase the admin quoted, a table of the real shipped Plains percentages showing blocks and mobs interleaved in one pool, why only the ratio matters, and tuning recipes.
• CHEST as a special case: its weight is the chance of a chest, and rarity is a second roll at the hard-coded 62/25/9/4.
• fixedBlocks and holograms positions, CHEST_WITH_<ITEM>, and the support-block caveat.
• phases_index.yml order/length, and that file-name numbers are only a hint now.
• Commands, placeholders and requirements.
• Chests, with the "build them in game with setchest" advice.
• Custom blocks — including that probability: is a weight in the same pool — and the quoting and spawner-timing gotchas.
• Version gating at phase, block and mob level.
• A step-by-step "build a new phase" walkthrough.
• A troubleshooting table keyed off the actual log messages the addon emits.

Overview page fixes (gamemodes/AOneBlock/index.md):

• blocks tab now says "weight", explains the raffle, and notes CHEST's two-stage roll.
• mobs tab gains a warning that mob weights share the block total, with the real Plains numbers.
• Custom Blocks tab notes that probability is a weight in the same pool, and documents the custom-blocks: sibling list.
• A pointer to the new page at the top of "Phase Config Files".

Companion change in AOneBlock itself rewrites the comments in the shipped 0_plains.yml, which is where admins look first.

mkdocs build passes; all new internal links and anchors resolve.