roblox game

Prompt

Create a complete, playable Roblox Studio place file named ThrowForStrikers.rbxmx for a polished distance-collector game called THROW FOR STRIKERS. Deliver the actual Roblox model/place XML—not a design document, pseudocode, or a list of scripts. The file should open in Roblox Studio with the core gameplay loop ready to test.The game’s loop is: train throwing power, time a soccer-ball throw, travel as far as possible, scout a striker based on the landing distance, equip up to three strikers at a training facility, earn Coins, and use those Coins to unlock better soccer balls and progress farther. Keep the experience readable and approachable for younger players, with an obvious next goal at all times.Build a focused, fully playable MVP rather than attempting every live-service feature. Include: A compact school-pitch environment with a throwing lane, a visible training station, distance markers, and gates for the first four scouting tiers: 25 m, 100 m, 300 m, and 750 m. A training interaction that increases Arm Power, with a simple rhythm or timing bonus. Include clear feedback and a sensible cooldown so training cannot be exploited by rapid remote calls. A throw meter from 0 to 20. Support desktop keyboard/mouse and mobile touch controls using Roblox UI. Releasing between 18 and 20 triggers a “FLOW” throw with a distance bonus; other releases still throw, with especially low values producing a weak—but never completely failed—throw. A distance calculation that uses Arm Power, the equipped ball’s multiplier, the release timing, and equipped-striker bonuses. Show the resulting distance prominently and update the personal record. Three permanent, purchasable ball options: Training Ball, Puzzle Ball, and Egoist Ball. Each should have a displayed price, distance multiplier, and luck multiplier. Buying a ball unlocks it permanently; equipping it does not consume it. A scouting reveal after each throw. The landing distance determines the eligible tier, while ball quality influences rarity odds. Include at least six configurable striker entries inspired by the supplied concept, with names, tier requirements, rarity, income, and passive bonuses stored in one easy-to-edit data module. A collection index showing discovered and undiscovered strikers, distance requirements, rarity, and whether each is equipped. Duplicates should convert into Ego Shards instead of being wasted. A three-slot striker formation at the player’s base. Equipped strikers generate Coins over time and provide their listed bonuses. Include a simple facility-income collection interaction and a clear display of the current formation and earnings. A clean HUD showing Coins, Ego Shards, Arm Power, equipped ball, personal-best distance, current throw distance, and the next gate. Use a compact scouting/reveal panel and clear purchase, equip, training, and collection feedback. Basic persistence for player stats, unlocked balls, collection, equipped strikers, and record. Use server-side DataStore logic with safe pcall handling and sensible defaults. If persistence cannot be tested in Studio without API access, keep the game playable in the same session and provide a clear in-game fallback. Server-authoritative validation for rewards, purchases, training, scouting, and equipment changes. Create and validate all RemoteEvents/RemoteFunctions; never trust client-submitted Coins, distance, rarity, or ownership. Basic sound and visual feedback using built-in or generated effects where possible. Do not require external asset IDs for the core game to function. Use a polished sports-broadcast visual style: deep navy, cobalt blue, electric cyan, white, and restrained gold accents. Make the interface angular and legible, with large distance numbers, clear rarity colors, and responsive layouts. Use simple, original geometry and effects rather than relying on external models or decals.Organize the implementation into sensible Roblox services and reusable modules, such as server-side game logic, shared configuration, and client-side UI and controls. Add concise comments where they help future editing. Ensure all referenced instances, scripts, folders, remotes, and UI elements are created in the file, with no missing dependencies or placeholder code. Test the logic for common edge cases, including insufficient Coins, duplicate scouts, invalid remote requests, empty formation slots, and player rejoining.Treat Blue Lock as inspiration only. Make the experience clearly unofficial and do not use official logos, copied artwork, or story text. Put character names and descriptions in a configurable data table so the owner can replace them with original characters before any public or commercial release.Output only the complete .rbxmx XML file contents. Do not wrap the XML in Markdown fences, add explanations, or omit sections with phrases such as “code continues here.” Ensure the XML is well-formed and that embedded Luau script source is encoded correctly for Roblox Studio.