Repository navigation
Releases
v0.6.0
v0.6.0
Changes since v0.5.0.
Features
Three-second warnings and focused control polish
For WoW Burning Crusade Classic2.5.6 / Interface20506. The owner explicitly authorized publishing this completed issue13 follow-up on October30,2026. It preserves the v0.5.0 Brawl/watch, host-succession, hit-feedback and varied-AI gameplay while shortening the real warning clock and polishing the existing original UI. Blizzard/native asset skins, a style toggle, unique levels and AFK-dialog changes are not included.
Upgrade every participant together
This release uses R6. Published v0.5.0 and the earlier frozen b98c93c candidate use R5 and cannot participate, even though that candidate displays0.4.0 and this source displayed0.5.0 before release. Timing, AI and checkpoint simulation semantics changed; matching display labels or packet field widths are not compatibility proof. Install the same versioned release ZIP on every participant, with one Rampage folder directly under Interface/AddOns, then safely /reload when ready and out of combat.
Publication and local installation are separate verified operations. No forced reload, external SavedVariables edit or other-PC access. Preserved versioned ZIPs/frozen runtimes remain rollback points; a junction to moving primary main is not an immutable old release.
Real three-second boss warnings
- Every boss now uses 3s patrol +3s locked warning +0.5s impact +3s recovery =9.5s. Warning-to-impact is actually three authoritative game-clock seconds, not a relabelled countdown or hidden earlier seven-second phase.
- Warning origin and lanes remain locked; damage applies once in Model. Shared moving hitboxes, shields, range,100HP,35 boss damage,20 Brawl damage, action/PvP cooldowns, pause and exact checkpoint clocks remain.
- Dodger begins avoidance at2.5s remaining; Smasher/Chaser/Scrapper at2s. Their normal0.3–0.6s decision cadences and legal movement/range/damage rules remain. No AI gains immunity, stronger hits or teleports.
- One newly locked warning requests an early ordinary full-world snapshot through the existing bounded queue. A pending world completes first; capture retries when it drains. There is no separate hazard event, predicted impact, client-side damage or larger transport cap.
Healthy two-client simulation covered80 combinations of four bosses, ground/top-floor starts and five snapshot phases using200ms round trip,20fps ticks,0.5/0.75s reaction and250ms legal repeated input. All escaped; worst warning notice0.8s, minimum margin0.3s, maximum five actions. This is a measured envelope, not a guarantee for slower input, congested/lossy raids or native Blizzard transport. A blackout longer than three seconds can hide the complete warning; the host still applies exactly one authoritative hit and later state must not replay it. Dodge promptly.
Original segmented controls and alignment
- Mouse/Keyboard are equal original112x30 segments with separate indicator, selected fill and border—no bracket/ASCII radio labels. The segment shows the saved preference; separate status text truthfully distinguishes Keyboard active from preferred/inactive.
- Keyboard is the fresh default. Existing valid Mouse/Keyboard settings persist; nil/invalid legacy values migrate to Keyboard. Preference can be changed while idle, lobby, auto-watching or host-watching without admission/action packets, avatar creation or key capture.
- Explicit Join fight arms Keyboard only when the accepted fighter role reaches active play. A full/denied join stays watching with preference preserved and no capture. Mouse remains uncaptured with action buttons. Leave fight releases but preserves preference; explicit rejoin can activate it again.
- Escape, chat/edit focus, modifier/focus loss, interruption, combat, Info/Settings, close, KO and watching release capture immediately without changing preference or automatic re-grab. Ordinary city transitions retain active keyboard routing while clearing held actions until release/fresh press.
- Header buttons, primary action/help row, selectors/mouse actions, crew stats, local HP/bar and footer baselines share consistent spacing. Long status/name and7HP fixtures remain bounded. The duplicate shield badge that overlapped the ground rail was removed; numeric shield health and the single reach label remain.
- Window stays900x660. Fixed mock pools after500 renders:111 frames,1,606 textures and131 font strings. Original facade panes/trim, Info/Settings, confirmed hit feedback, Reduced Motion and optional audio-off-by-default remain.
Multiplayer and recovery limits
R6 remains normal PARTY/RAID within one group: no independent-party bridge, instance-chat transport, external server or competitive anti-cheat claim. Maximum tested world is494 body bytes /3 packets /662 charged bytes, largest216/255. Forty maximum-name admissions took57.0s, queue53. Sustained107.7s mixed play measured684.3 chargedB/s,3.95 host messages/s, queue45 and5.0s worst active display gap. A short admission average can consume the allowed initial burst; it is not a sustained-rate claim.
Host succession remains intentionally conservative. Small graceful handoff measured5.3s. Forty-node graceful loss/reordering measured36.3s including settling with a6,919-byte/40-fragment checkpoint; crash with4.35% recipient loss measured44.5s including convergence using6,933 bytes, then the unique successor advances. Sparse40-native/3-admitted recovery measured38.7s and only admitted members vote.
Recovery is not instant and crashes can roll back uncommitted world, HP and score. Missing matching checkpoints, admitted-voter quorum or safe membership fences pauses instead of running competing authorities. Native roster absence alone does not retire a vote. A true process restart forgets volatile lineage and may require a fresh room, especially with two participants. This is not perfect partition consensus or Byzantine resistance.14s lease,20s host detection,16s election grace,40s election window,35s graceful deadline and120s checkpoint lifetime remain distinct.
Verification and first checks
The settled candidate passes 179 checks:37 model,55 protocol/migration,40 feedback,39 actual-TOC UI and8 real-adapter flow. SavedVariables migration and real idle/watch/lobby/join/full-denial/leave/rejoin preference lifecycles are included in the UI/flow suites, plus separate Lua5.1 grammar and zero dependency audit findings. The release pipeline reruns the complete suite against the final version-bumped runtime before tag or upload. Fengari executes Lua5.3 semantics; grammar parsing and mocks are not native WoW.
The old snapshot scheduler was restored only in memory against the same80-case test and missed two Queuezilla top-floor cases; the bounded warning-onset request passes all80. Exact checkpoint remaining times3/1.37/0.01s pause/resume to one locked impact for every boss. Graceful and crash adoption each preserve1,200 exact AI decisions across24s. All prior delayed-vote/rejoin, fresh-process lineage, asymmetric roster, witness-lock, input safety, automatic-watch consent, hit attribution and stale-effect regressions remain.
Source-derived before/after/watch/fight/solo/Info/Settings/low-HP/long-name/keyboard previews were inspected at native-like scale, but they are strict mocks—not native screenshots. Native fonts/scaling/layering, keyboard focus/taint, optional audio, subjective feel and real two-client/large-raid delivery remain manual. Start with solo plus five AI, then two real clients on the same R6 release before scaling.
v0.5.0
v0.5.0
Changes since v0.4.0.
Features
Brawl flow, safer host succession and varied AI
For WoW Burning Crusade Classic 2.5.6 / Interface 20506. The owner approved publishing the installed b98c93c playtest on October 30, 2026 after positive in-game feedback. This release preserves that gameplay; only the release version and documentation change.
Upgrade every participant together
All players need this R5 release. Published v0.4.0 uses R4 and cannot participate. The reviewed b98c93c candidate already uses the same R5 gameplay, but use the versioned release ZIP for a coordinated installation. Extract its single Rampage folder into Interface/AddOns without double nesting; safely reload when ready and out of combat.
The owner's local installation remains the tested frozen b98c93c candidate during publication; publishing does not relabel or overwrite those files. No forced reload or external SavedVariables edit. The primary checkout advances to the published release. An older rollback junction pointing to that primary checkout therefore follows the updated release, not v0.4.0; preserved v0.4.0 ZIP/frozen files are the actual old-version rollback.
UI and participation
- Compact city-first layout, separate INFO and SETTINGS, and Mouse/Keyboard selectors reflecting actual capture. Opening panels and safety events release keyboard capture without silently taking it back.
- Normal UI and ordinary commands create Brawl rooms. Opening the window may automatically watch an available Brawl room, without an avatar or keys; Join fight requires explicit consent. Leave fight returns to watching; closing retains membership, while explicit Leave suppresses automatic rejoin.
- The legacy Co-op engine remains unchanged for compatibility/testing; normal UI does not create or casually join a Co-op fight or silently convert an existing room.
- Confirmed local damage is YOU; sampled shared damage is TEAM, never an invented remote per-hit combat log. Reduced motion retains static truthful feedback. Same-ID bot replacement entirely between ordinary snapshots remains indistinguishable for cosmetics.
Bosses and AI
- Actual boss cycle is 3s patrol + SEVEN-SECOND locked warning + 0.5s impact + 3s recovery = 13.5s. The future request for a maximum three-second warning is NOT included in this release.
- Five AI automatically mix Smasher, Chaser, Scrapper and Dodger profiles, distinct targets and legal cadences; the fifth Smasher has an eastern objective bias. AI obey ordinary movement, range, damage, vulnerability and cooldown rules. AI can never become host.
- Up to 25 actors including five AI, with up to 40 real participants including watchers. Human fighters replace filler AI first. Real combat safety and optional audio-off-by-default behavior remain.
Host succession and honest limits
Host ordering uses longest continuously admitted real participant, including watchers. Leaving/rejoining gets a new ordinal; changing role or closing the window does not. An ordinary host Leave transfers a complete checkpoint without restarting the match; a promoted watcher need not become a fighter.
Recovery is NOT instant. Measured small graceful handoff: 5.3s. Forty-participant graceful handoff with loss/reordering: 31.5s plus 5s settling = 36.5s. Forty-participant crash: 36.4s plus 8s convergence = 44.4s. Crash adoption can roll back uncommitted world, HP and score. These are deterministic transport measurements, not guaranteed native latencies.
Insufficient matching checkpoints, admitted-voter quorum or safe membership evidence pauses rather than running two authorities. Native roster absence cannot revoke an outstanding vote. A true client process restart forgets volatile lineage and may require a fresh room when too few old members remain, especially a two-person room. This is not perfect partition consensus or Byzantine anti-cheat. Checkpoint evidence expires after 120s.
Verification and first checks
174 automated checks passed: 37 model, 53 protocol/migration, 40 feedback, 36 actual-TOC UI and 8 real-adapter flow; 12 Lua 5.1 grammar checks and zero dependency audit findings. Full tests run again against the final version-bumped runtime before publication. Execution uses Fengari Lua 5.3 semantics, not native WoW.
The 40-node loss test demonstrates a unique unpaused successor advancing its clock. Delayed-vote/rejoin, fresh-process, asymmetric roster and witness-lock regressions pass. Both graceful and crash checkpoints preserve 1,200 exact AI decisions across 24s. Sustained 40-node play measured 677 charged bytes/s and 3.91 host messages/s; initial admission burst averages are not claimed as sustained-rate success.
Owner in-game feedback is positive, but it does not certify two-client/large-raid behavior. Native keyboard focus, rendering/alignment, scaling/taint, optional audio and real PARTY/RAID transport remain manual checks. Start with solo plus five AI, then two clients on the same release before scaling.
Follow-up only: shorter boss warnings, control/radio styling and alignment polish. Blizzard assets or a comparison toggle remain deferred and are not part of this release.
v0.4.0
v0.4.0
Changes since v0.3.0.
Features
Fixes
- Restore readable building windows and facade detail (#9).
Roaming bosses with visible attacks
For WoW Burning Crusade Classic2.5.6 / Interface20506. This publishes the reviewed moving-boss feature from PR #8 plus its narrow pre-publication stale-render cue fix. The owner authorized this release on October29,2026. Unique/different level layouts are later work, not included.
Upgrade both machines together
Every participant needs the same new versioned release. R4 is incompatible with v0.3.0/R3 and older protocols. Use the attached release ZIP, not a head-labelled playtest archive. Extract its single Rampage folder into Interface/AddOns, without double nesting, and safely /reload when ready.
The owner's existing linked checkout is advanced to this approved release and left there. No junction swap, forced reload or external SavedVariables edits are performed. Do not extract over that junction; the other machine installs the same versioned ZIP. Earlier releases and candidate archives remain preserved for rollback.
Boss movement and attacks
- Bosses really patrol ground lanes2–6, at most two lanes in five seconds. A shared authoritative position drives punch reach, AI pursuit and visible location; no stationary3–5 ghost hitbox. After flattening the city, hit the exposed boss on the ground within one lane of its actual position. The gold bracket follows its reach. No body-contact damage.
- Cycle: 5s patrol →7s locked windup →one impact /0.5s attack →5s stationary recovery. Targets and attack origin lock before the warning, never track later dodges. At least four safe lanes remain. Recovery gives players time to catch and punch the boss.
- Crumb Baron: reflected stroll and one-column crumb throw, all heights.
- Permitron9000: two-lane march and adjacent-column beam, all heights.
- Snack Tax: nearest-actor pursuit and adjacent ground stomp. Ground only; climbing can avoid it.
- Queuezilla: alternating strides and three adjacent warned columns striking together, all heights.
- Visible moving shield, patrol/windup/release/recovery poses and pooled original throw/beam/stomp/barrage cues show the actual attack origin. Clients never apply damage from animation.
- Clients smooth only the known patrol segment, stopping at its endpoint and freezing when paused/stale. No future route/attack prediction. A timely confirmed recovery may show short static impact residue at already-known targets, never a late projectile or damage replay.
Building details restored
The earlier warm building detail is back: bright multi-pane windows, crossbars, sills, roof/cornice trim and subtle brick seams. Explicit draw layers keep walls behind panes/trim instead of relying on creation order, and damaged floors keep readable lit windows instead of fading them almost away. This is a bounded visual restoration, not new level themes or gameplay.
Review fix included
An old warning sample could become stale while no frames rendered, then incorrectly show confirmed-impact residue when a delayed consecutive recovery arrived. The UI now checks previous sample age before replacing its timestamp, even without an intermediate render. More than2.5s suppresses late residue and clears the stale visual baseline; normal timely confirmation and the exact2.5s boundary remain unchanged. This is presentation-only; no gameplay/schema/latency change.
Existing controls and multiplayer preserved
- Selected keyboard or mouse mode persists across ordinary level transitions. Held inputs are cleared and require release/fresh press next city. Escape/close/leave/chat/focus/modifiers/real combat still release capture, with no automatic recapture. KO/victory behavior unchanged.
- Default Co-op, explicitly opted-in Brawl,100HP,20-damage punches,35-damage boss impacts,4s KO/respawn and3s spawn immunity retained.
- Host/solo can add/remove up to five AI within25 actors; real humans displace filler AI first. 40 real participants including spectators, separate from AI. Spectators remain read-only and immune. Host combat pauses movement/warnings/recovery; guest protection is reconciled before known damage.
- Optional local BlasterMaster audio remains OFF by default. No copied external audio/art or global volume changes.
Quick start and confidence limits
/rampage solo →Add AI→PLAY. Watch a full patrol/windup/attack/recovery cycle, flatten the city, then chase the moving boss and hit inside its bracket. Start with two clients on the same release in one PARTY/RAID before scaling.
74 automated checks (22 model,26 protocol,26 actual-TOC WoW/UI/input/audio mocks),9 Lua5.1 grammar checks and zero dependency audit findings. The new no-intermediate-render regression was demonstrated failing before the fix and passing afterward. Building checks verify explicit draw layers/sublevels and intact/damaged window visibility; fixed object pools remain stable after500 renders. Independent baseline review also exercised28,000 off-grid world round trips. Execution uses Fengari Lua5.3 semantics, not native WoW.
Authoritative worlds still arrive every1.25s; no prediction. Seven-second warnings exceed the tested4s maximum gap but are not a guarantee under arbitrary network loss. Remote countdowns and hit feedback can lag; dodge early. Some0.5s attack frames can fall between snapshots. This is friendly/nonprecision play, not competitive network fighting. Native rendering/fonts/scaling, keyboard focus/taint, real two-client response, optional audio and large live raids remain manual checks. See QA.md for evidence and limitations.
v0.3.0
v0.3.0
Changes since v0.2.0.
Features
AI monsters, optional Brawl and active boss hazards
For World of Warcraft: The Burning Crusade Classic 2.5.6 / Interface 20506. This publishes the reviewed AI/Brawl build from PR #6, explicitly authorized by the owner after in-game feedback on October 29, 2026. Roaming bosses and unique level layouts are NOT included; those are separate future iterations. Bosses currently stay in their display position while dealing real telegraphed lane attacks.
Everyone upgrade together
Install this same new versioned release on both machines/all participants. Its R3 protocol is incompatible with published v0.2.0/R2. Extract the single Rampage folder into Interface/AddOns and safely /reload when you choose. Do not mix with old releases or head-labelled playtest archives. No forced reload, SavedVariables edits or junction swaps are performed by publishing.
What's playable
- Default PvE Co-op: smash the shared city and four bosses without hurting teammates. Optional Brawl also permits human/human, human/AI and AI/AI punches; JOIN BRAWL is explicit consent. Host chooses before Start/replay only with no other real participants joined.
- Host/solo Add AI / Remove AI, one per click, maximum five AI within 25 total actors. They climb/smash, dodge warnings and scuffle in Brawl using bounded deterministic addon logic, not an LLM/backend or real WoW character automation. Human admission/Play requests vacate the oldest filler AI first.
- 40 real participants including the host; AI does not consume human seats. Example:20 human actors +5AI +20spectators. Spectators have no avatar, attack, health target, score or Start authority.
- 100HP,20-damage adjacent/same-height Brawl punches,35-damage boss impacts, bounded knockback/cooldowns and KOs separate from fame. Four-second KO/respawn, three-second spawn immunity; click PLAY after respawn to recapture keys.
- Four repeated boss lane patterns while shielded and exposed: seven-second warning → one impact →0.5s impact display →three-second recovery. Move out of marked lanes early; all heights are affected. Shared city/four-boss completion and replay remain.
- Clear health/AI/KO/shield HUD, seven pooled danger-lane markers, consistent hover/pressed/disabled/selected buttons, ASCII fallback action labels and corrected stale “Window hidden” text.
- Chosen keyboard/mouse mode now persists across ordinary level transitions, as requested before publication. Captured controls stay selected through intermission without acting; held input is cleared and needs a key release/fresh press next city. Explicit PLAY capture for WASD/arrows/Space; Escape releases keys. Chat/edit focus, combat, hide/leave, modifier shortcuts and interruptions release capture. No permanent keybinding changes. Host combat pauses the world; guest combat protection combines authenticated notification with read-only real roster status.
- Optional Local BM remains OFF by default, using separately installed BlasterMaster mappings. Rare local impact/hurt and major transition cues, provider None/mute respected. No external sound clips bundled or global volume changes.
Quick start
/rampage solo → Add AI → PLAY. For fighting: Leave → BRAWL → Solo practice, or /rampage solo brawl, then Add AI. In a party/raid: Host Lobby → select mode/AI → Start Game; the other machine explicitly Join Co-op / Join Brawl / Spectate.
Verified evidence and limitations
56 automated checks,9 Lua5.1 grammar parses, zero dependency audit findings. The prior55-check candidate was independently reviewed with four supplemental probes; the additional actual-TOC regression covers the requested stage-transition control persistence and safety cancellation. A single AI clears all four bosses in108.8 simulated seconds. A40-real-node loss/reorder test with25 actors including5AI converges through bosses/replay; this is not proof of live40-client WoW transport. Execution uses Fengari Lua5.3 semantics, grammar checking is separate.
Full authoritative worlds remain every1.25s (0.8Hz), no prediction. Remote feedback/countdowns can lag. Seven-second warnings exceed the tested4s maximum world gap, but arbitrary delay/loss can hide a warning; dodge early. Brawl is friendly/nonprecision play, not a competitive network-fighting guarantee. Native keyboard focus/taint, two-client response, new audio and large live raid checks remain manual; see QA.md. Positive owner play feedback does not certify those checks.
v0.2.0
v0.2.0
Initial tagged release.
Features
- FOUR MORE BOSSES arcade with keyboard polish and 25-player co-op (#3) (71c27dd)
- initial Rampage scaffold for Toast raid arcade (8b11bc0)
Rampage — FOUR MORE BOSSES!
First published release for World of Warcraft: The Burning Crusade Classic 2.5.6 (Interface 20506), CurseForge project 1772524. Includes the approved keyboard/graphics/25-player build and the full-lobby admission fix.
Play
/rampage solo, or open/rampagein a party/raid: Host & Start, Join Game or Spectate. Shared city destruction, personal fame and four fictional bosses.- 25 active players / 40 total participants; 15 spectator spaces when active slots are full. Spectators can switch to play when a slot opens. Full total lobbies visibly disable admission; full active lobbies still offer Spectate.
- Click PLAY • GRAB KEYS for WASD/arrows and Space. Escape releases keys. Chat/edit focus, hide/leave, combat, modifier shortcuts and interruptions release capture; compact mouse fallback remains. No permanent keybinding changes. Check key behavior in a safe area first.
- Original warm city/monster graphics, expressive poses, boss health/shield, local highlight, hover roster, pooled dust/rubble/stage/victory effects and fit-to-screen UI.
- Optional Local BM is OFF by default. When enabled it uses your separately installed BlasterMaster sound mappings, including None/mute. No BlasterMaster/game sound files are bundled. Only throttled local impacts and major transitions play, on the SFX channel; no global volume changes.
Upgrade and known limitations
- Everyone must install this same R2 build. Original four-player R1 playtest clients are incompatible. Extract the single
Rampagefolder intoInterface/AddOnsand reload only when safe. - Complete authoritative worlds are sent every 1.25 seconds (0.8 Hz) with bounded addon-message traffic. Animation is smoother, but remote action feedback can lag; no client prediction or low-latency action-game claim. Large simultaneous joins can take tens of seconds (90s bounded timeout).
- Host combat pauses the shared game; guest combat disables that guest's input. No host migration. Host departure ends the session. Switching to spectate removes that avatar's current score; saved personal best remains.
- 38 automated checks, including a lossy/reordered 40-node simulation, plus 9 Lua 5.1 grammar checks. Test execution uses Fengari Lua 5.3 semantics, not WoW's native VM. The requester demonstrated original solo MVP gameplay; new native keyboard/focus/taint, audio and large live raid behavior remain manual checks. See bundled QA.md. Especially test chat, Escape, combat, Alt-Tab/taskbar focus and two-client response before a large raid.
Original geometric/pixel-style art and fictional encounters; not affiliated with the classic Rampage game's owners. No copied classic-game audio/art is distributed.