Esportz.fun
Language
INTERMEDIATEAI Arena

Advanced Model Guide — Buckets, Settings, Data Flow

Advanced model guide for View All: collect clean data, set Buckets, tweak Epochs/Batch Size/Learning Rate, use Remove Sparsity, Oversampling, and Multi-Stream.

By Esportz.fun Team
Archive · original publication date unavailable
10 min read
Advanced Model Guide — Buckets, Settings, Data Flow

TL;DR

  • Use the Advanced model with Exponential Memory Updating enabled so zone edits don’t wreck unrelated data.
  • Record tight, isolated demonstrations: cut idle frames and avoid extra moves to keep training signals clean.
  • Process first runs with high Epochs and Learning Rate, low Batch Size; enable Remove Sparsity and Oversampling early.
  • Pick Buckets per ground/air zone and combine Discrete Distance + Your Direction + Angle to Opponent for reliable behavior.

What You Need to Know First

Prerequisites

ItemEffectWhere to Get
Advanced modelZone-isolated edits, advanced settings for converting bad dataSelect from model menu before training
Exponential Memory UpdatingPrioritizes recent training sessions for faster behavior shiftsAdvanced model checkbox
Remove SparsityDeletes empty info cells to make training denser and fasterProcessing options (95% usage)
OversamplingHelps memorization of positions/directions; useful in initial trainingProcessing options
Multi-StreamBoosts confirmed existing actions/directions proportionallyProcessing options (use with care)
Buckets (On Ground / In Air)Isolates training by situation (prevents cross-zone side effects)Buckets selector in Advanced UI
Epochs, Batch Size, Learning Rate, Direction and Action LambdaCore training knobs for behavior shapingProcessing tutorial / advanced settings

Levels & Time

  • No character levels are required, but expect multiple iterations. Early sessions establish baseline behavior; iteration is the meta here. Plan for several short record/process cycles rather than one long experiment.

Quick notes

  • Ixtlanian’s tip: keep demos tight and surgical. A single sloppy recording can pollute a bucket. Think like a surgeon, not a drunk barber.
  • The Advanced model is the top-tier pick for competitive players because you can edit "Side Of Stage" behavior without blowing up "On Ground" routines.

Step-by-Step Guide

  1. Choose the Advanced model and enable Exponential Memory Updating

    • Before you press record, switch to Advanced. Check Exponential Memory Updating for sessions where recent behavior matters more than legacy data.
  2. Plan your session and pick Buckets

    • Decide which Buckets you’ll record into. The isolation is the Advanced model’s main power.
ItemEffectWhere to Get
On Ground: Projectile ActiveTrained when special abilities are used on groundOn Ground bucket selector
On Ground: Opponent StunnedTriggers when opponent is stunnedOn Ground bucket selector
On Ground: Opponent KnockbackTriggers on opponent knockback eventsOn Ground bucket selector
On Ground: Opponent ActiveCatches all other ground casesOn Ground bucket selector
In Air: Near Blast Zone / Safe Zone / Under Stage / Side Of StageAir zones trained independentlyIn Air bucket selector
  1. Collect data the right way

    • Minimize Empty Information Slots: press the data button and act immediately. Long pauses add empty cells that disguise the signal.
    • Avoid Unnecessary Actions: keep each demo isolated. If you want an uppercut after a dash, demo that sequence cleanly and nothing else.
  2. Process initial training runs (establish baseline)

    • Settings table for first runs
SettingRecommendationPurpose
EpochsHighForce the model to learn core patterns
Learning RateHighAllow meaningful parameter updates early
Batch SizeLowIncrease weight of scarce examples
Direction and Action LambdaLow (initial)Permit changes to actions/directions
Remove SparsityEnabledCollapse empty cells into meaningful samples
OversamplingEnabled (early)Help model memorize positions/directions
Multi-StreamOff initiallyAvoid unintended biasing of other actions
  1. Harden or protect existing data

    • If you want to adjust a small behavior without upsetting everything, increase Direction and Action Lambda to maximum and drop Epochs/Learning Rate. That tells the system: "don’t overwrite the good stuff." Think of it as putting a guardrail on your training.
  2. Use Focus Settings to teach context-aware reactions

    • Your Actions: good for sewing multi-step combos; use late in tuning.
    • Opponent Actions: almost always on for ground training to react to enemy moves.
    • Your Positioning / Opponent Positioning: use when spatial relations matter. Your Positioning is essential for edge recovery and platform returns.
    • Your Direction + Angle to Opponent + Discrete Distance: classic combo for behavior that depends on facing and distance. This combo is your bread-and-butter for chase/grab/uppercut windows.
    • Recoveries Remaining: only for "Side Of Stage" and "Near Blast Zone" to avoid repeating failed returns.
  3. Iterate: don’t save bad sessions

    • If a processed run produces garbage, don’t keep it. Figure out which focus or setting caused the regression and re-run with corrected demos. The model rewards a clean, surgical approach more than volume.

Pro Tips

  • When teaching close-air mixups, record separate sessions for "Near Blast Zone" and "Safe Zone" so the model doesn’t conflate two different recovery priorities. Use Oversampling to reinforce near-edge behaviors.
  • If a new action corrupts unrelated behavior, flip Direction and Action Lambda to max and rerun with low Epochs/Learning Rate to nudge only the new action.
  • Use Multi-Stream only after you’ve tested changes in isolation. It accelerates confirming existing actions but can quietly weaken others if abused.
  • For edge defense, combine Opponent Off Stage + Discrete Distance + Your Direction. It forces the fighter to treat off-stage enemies differently than regular ground pressure.
  • Treat Remove Sparsity as the default for processing. You’ll waste less time debugging empty cells and training will converge cleaner and faster.

Common Mistakes to Avoid

  • Recording long demos with idle frames — fills the bucket with empty info and muddies the signal.
  • Using Multi-Stream or high Learning Rate without isolating Buckets — changes bleed into unrelated behaviors.
  • Toggling many focus settings at once — if something breaks, you won't know which setting caused it.