AI Skill Report Card

Building Anime RNG Roblox Game

A-83·Nov 19, 2026·Source: Web
13 / 15

This skill produces a two-tab web application:

  1. Tab 1 — Playable 3D Prototype: React + Three.js + Tailwind, rendering a low-poly anime floating island with a working roll/gacha loop.
  2. Tab 2 — Luau Code Exporter: Copy-button panel with 4 production-ready Roblox scripts.

Start by building the data model first (rarity table), since both tabs consume it — the web prototype for live rolling/VFX, and the exporter for generating RarityConfig.lua.

TypeScript
// Single source of truth — define once, drive both tabs from this array interface AuraTier { id: number; name: string; nameEn: string; oddsOneIn: number; // e.g. 1500 means "1 in 1500" class: "Low" | "Heroic" | "Mythic" | "Singularity"; colorHex: string; secondaryHex: string; goldPerSec: number; luckBonusPct?: number; goldBonusPct?: number; cutsceneTier: 0 | 1 | 2 | 3; // 0=none, 1=flash+spin, 2=impact frame, 3=global event vfxDescription: string; }
Recommendation▾
Add 1-2 more concrete examples showing actual Luau code snippets or full rarity table entries rather than only describing the changes abstractly
14 / 15
Progress:
- [ ] 1. Define the 12-tier rarity table as a shared TS/Luau-mirrored constant
- [ ] 2. Build Three.js scene: floating island, sakura trees, altar, character placeholder, particle system
- [ ] 3. Implement core loop: Roll button → weighted RNG → VFX tier dispatch → inventory/gold update
- [ ] 4. Implement Mana Awakening bar: spawnable crystals, click-to-charge, Overdrive state (2x speed, 3x luck, timer)
- [ ] 5. Implement Guild Shop (luck/speed/gold upgrades) and Alchemist Forge (duplicate → potion crafting)
- [ ] 6. Implement weather events: Golden Harvest, Blood Moon (sky color lerp, demonic variant unlock)
- [ ] 7. Build cutscene VFX system with 3 escalating tiers (screen flash → impact frame + camera shake → global sky/hologram event)
- [ ] 8. Build Tab 2 exporter UI: one-click copy for each of 4 Luau files
- [ ] 9. Write RarityConfig.lua mirroring the web rarity table exactly (same odds, colors, bonuses)
- [ ] 10. Write ServerRNGManager.server.lua: weighted roll, luck multiplier stacking, leaderstats, DataStore
- [ ] 11. Write CutsceneClient.client.lua: TweenService camera work, ColorCorrectionEffect/BloomEffect flashes
- [ ] 12. Write GenerateMedievalMap.lua: procedural altar, rune circle, bridges, islands, sakura trees, crystals
- [ ] 13. Polish UI chrome: gold-bordered RPG panels, button hover/press animations, rarity-colored glows
- [ ] 14. QA pass: verify odds sum logically, no runtime errors in either tab, copy buttons work
Recommendation▾
Show a bad vs good example (e.g. a common pitfall actually manifesting in broken code) to reinforce the 'Common Pitfalls' section with contrast
  • Odds must be stored as weight = 1 / oddsOneIn for cumulative-weight RNG; never loop-compare floats directly — use integer weight pools scaled to a common denominator (e.g. total weight = 500,000,000 to match the rarest tier) to avoid float precision bugs at extreme odds.
  • Map oddsOneIn to cutsceneTier with fixed breakpoints: <1500 → 0, 1500–49999 → 1, 50000–9999999 → 2, ≥10000000 → 3. Drive VFX intensity purely from this derived field, never hardcode per-aura VFX logic.
  • Every tier needs: unique hex color pair (primary glow + secondary particle), a one-line VFX description, and a gold/s value that roughly 4-5x's the previous tier — keep progression curve exponential, not linear.
  • Use low-poly primitives (icosahedrons, cones, flattened cylinders) with MeshToonMaterial or flat-shaded MeshStandardMaterial — never PBR-realistic materials; it breaks the anime aesthetic.
  • Particle systems: use THREE.Points with custom shader or sprite billboards for sakura petals, mana motes, and impact sparks — don't instantiate thousands of individual meshes.
  • Sky: implement as a lerp-able uniform color/gradient (shader material or Sky addon tint) so weather events (Golden Harvest, Blood Moon) and Tier 3 cutscenes can animate it with gsap or manual requestAnimationFrame lerp over 1-2s.
  • Camera shake: offset camera position with decaying sine noise over a fixed duration (e.g. 0.4s for Tier 2 impact), never permanently mutate the base camera transform — always restore to saved origin.
  • Character "levitation" pose (rarity ≥1500): tween Y position with sine bob + trail particles spawned behind movement vector.

Tier 1 (1:1,500 – 1:49,999): screen dim overlay → 8-point star flash in aura color → 360° camera orbit (~1.5s) → reveal.

Tier 2 (1:50,000 – 1:9,999,999): mute SFX bus → black & white full-screen flash (impact frame, 2-3 frames) → vertical light beam from sky → ground crack decal with glowing runes → sword-slash name reveal UI → camera shake (high amplitude, fast decay).

Tier 3 (≥1:10,000,000): global sky recolor to aura theme (all clients if multiplayer) → giant holographic aura symbol above player visible map-wide → expanding shockwave ring VFX across terrain → extended camera hold (3-4s) before reveal UI.

Always gate: higher tier cutscenes must contain lower tier beats (Tier 3 includes the Tier 2 impact frame, etc.) for visual consistency.

  1. RarityConfig.lua: pure data module, return { Auras = {...} }. No logic, no RNG, no Instance creation. Must include Weight, Color3, GoldPerSec, LuckBonus, CutsceneTier per entry.
  2. ServerRNGManager.server.lua: owns all RNG (Random.new(), never math.random reseed per-call), reads RarityConfig, applies player's active luck multipliers (base + upgrades + potions + awakening), fires a RemoteEvent to the roller's client only with the result, handles leaderstats.Gold accrual via Heartbeat/while task.wait() loop, and autosaves via DataStoreService:UpdateAsync wrapped in pcall with retry.
  3. CutsceneClient.client.lua: listens to the RemoteEvent, branches purely on CutsceneTier (never on aura name), drives TweenService for camera and Lighting:FindFirstChild("ColorCorrection") / Bloom effects, restores Lighting to defaults after cutscene via tween-back.
  4. GenerateMedievalMap.lua: idempotent — wraps build in if workspace:FindFirstChild("ValoriaMap") then it:Destroy() end, parents everything under one Folder named ValoriaMap, uses Instance.new + batch property sets, groups islands/bridges/trees into sub-folders for organization, and anchors all parts (Part.Anchored = true).
14 / 20

Example 1: Input: "Add a new rarity tier between Lunar Eclipse Mage and Abyssal Monarch" Output: Insert into the shared array with oddsOneIn between 50,000 and 250,000 (e.g. 120,000), recompute all weight denominators in both the web RNG function and RarityConfig.lua, assign cutsceneTier: 2 (falls in Tier 2 range), pick a color distinct from neighbors, and regenerate the exporter output — no other files change.

Example 2: Input: "Player clicks Roll during Overdrive mode" Output: Server multiplies effective luck by 3x and halves roll cooldown; client shows Overdrive aura overlay (fire particles) layered under whatever cutscene tier the roll result triggers; both systems read a single IsAwakened boolean rather than duplicating the multiplier logic client-side.

Recommendation▾
The description is good but slightly long — tighten it to lead with the single most common trigger phrase a user might type
  • Keep the rarity table as the single source of truth — generate the Luau RarityConfig.lua string by templating directly from the same TS array used in Tab 1, so they can never drift out of sync.
  • Use integer-weight cumulative RNG (not nested float probability checks) for correctness at 1:500,000,000 scale.
  • Separate "what tier was rolled" (data) from "what VFX plays" (derived from tier) — keeps cutscene code reusable and the aura list easy to extend.
  • Make map generation scripts idempotent and re-runnable without manual cleanup.
  • All monetary/luck math happens server-side in the Luau version; client only renders what the server tells it.
  • Don't hardcode per-aura VFX branches (12 if-statements) — derive VFX tier from odds via breakpoints instead.
  • Don't use math.random() with float probability chains for rare tiers — precision errors will skew 1-in-500-million odds.
  • Don't let the client compute or trust its own roll result in the Luau version — always authoritative server RNG + RemoteEvent push.
  • Don't forget to restore Lighting properties and camera CFrame after cutscenes — leaving tweened values applied breaks subsequent gameplay.
  • Don't use photorealistic materials/lighting in Three.js — it contradicts the low-poly anime art direction.
  • Don't regenerate the map script without clearing the previous ValoriaMap folder first — causes duplicate geometry on repeated runs.
0
Grade A-AI Skill Framework
Scorecard
Criteria Breakdown
Quick Start
13/15
Workflow
14/15
Examples
14/20
Completeness
18/20
Format
13/15
Conciseness
13/15