Roblox Wave System with Progressive Difficulty
ESCOPO
Generate a robust enemy wave controller for Roblox survival, tower defense, arena, or dungeon experiences. The result is a server-side Luau Script prepared to control the full cycle: preparation, staggered spawning, monitoring living enemies, wave completion, and a pause before the next round.
The prompt first requests the technical context of your project — Explorer hierarchy, enemy models, spawn points, attributes, RemoteEvents, and existing integrations — so it can return code compatible with your real structure. The implementation prioritizes server authority, scalability, validations, and useful comments for professional maintenance.
Conteudo
Prompt principal
Act as a senior Roblox Luau developer, specialized in server-authoritative multiplayer systems, performance, and scalable gameplay architecture. I will provide my game context below; use it as the source of truth and generate a single complete Luau Script for an enemy wave system with progressive difficulty. Before writing the code, analyze the context and mentally identify missing dependencies, path inconsistencies, or multiplayer risks. If an essential piece of information is missing, ask at most 5 objective questions before generating the script. If it is possible to assume a safe convention, briefly state the assumption and proceed. Do not invent RemoteEvents, modules, or objects if I have provided equivalent existing ones; reuse the exact names and paths provided. ## Context of my game (I will fill in below) - Desired location of the wave controller: - Folder/Model that contains the enemy templates: - Where active enemies should be parented: - Location and format of the spawn points (Folder, Parts, tags, or Attributes): - Required structure of each enemy (Humanoid, HumanoidRootPart, attributes, AI scripts, etc.): - Enemy types and their base values (health, speed, selection weight, reward, if applicable): - How enemy death/destruction is identified: - Existing RemoteEvents/RemoteFunctions and their paths: - Existing UI/scoreboard system that needs to be updated: - Initial number of enemies, interval between spawns, preparation duration, and maximum simultaneous enemies: - Formula or preference for difficulty progression: - Special waves/bosses and desired frequency: - Match end, defeat, or restart rules: - Other mandatory ModuleScripts, services, or conventions: ## Required deliverable Generate ONE file of type **Script** (not LocalScript and not ModuleScript), to be placed in **ServerScriptService**, unless my context explicitly indicates another location. The code must be valid and complete Luau, ready to paste into Roblox Studio, presented in full in a single Markdown block with the language `lua`. Do not deliver pseudocode, incomplete snippets, code omitted by ellipses, or fictional dependencies. Implement a clear state machine on the server, for example: `Waiting`, `Intermission`, `Spawning`, `ActiveWave`, `Completed`, and `GameOver` when applicable. The system must control the wave number, planned total quantity, spawned enemies, living enemies, time until the next wave, and current state. Use a well-documented configuration table at the start of the script to make balancing easy without changing the core logic. Difficulty must progress in a configurable and predictable way: increase quantity, health, and/or speed with multipliers and maximum limits; allow selection weights by enemy type; and support a configurable boss wave without breaking the normal flow. Spawn gradually by interval, respecting `MAX_ALIVE_ENEMIES` to prevent performance spikes. If the limit is reached, wait before continuing. Choose spawn points safely, with fallback and useful warnings if there are no valid points. Perform safe cloning of templates and validate that each clone has the required components before activating it. Track deaths through `Humanoid.Died` and also handle unexpected removal/destruction of the Model so the wave never gets stuck because of incorrect counters. Avoid double counting by using identifiers or controlled connections. Disconnect events and clean up resources when ending a wave or restarting the match. Do not use infinite loops without `task.wait()` or an exit condition, and prefer `task.wait`, `task.spawn`, and `Random.new()` appropriately. Security is mandatory: all logic for spawning, health, wave progression, reward, victory, and defeat must occur exclusively on the server. Never accept damage, currency, inventory, wave completion, or unrestricted spawn requests from the client. If I provide RemoteEvents for UI or restart requests, validate argument types, permissions, basic limits/rate limiting, and current state on the server before acting. RemoteEvents must be used only for visual communication or validated requests; the client is never authoritative. Include professional comments explaining important decisions, configurable paths, validations, progression formula, and safe integration points with AI, UI, and rewards. Use `game:GetService` for services, `WaitForChild` only for required dependencies, and clear diagnostic `warn` messages for invalid configuration. Do not use obsolete APIs. After the code block, write: (1) a short list of the objects and Attributes that need to exist in the Explorer; (2) numbered instructions to install and test in Roblox Studio with Test > Start Server and simulated players; (3) a quick adjustments section indicating which constants to change to balance waves; and (4) limitations or assumptions adopted. Respond in Brazilian Portuguese.
