Tycoon Prestige System with Permanent Bonuses
ESCOPO
Generate a robust prestige system for Roblox tycoons: when a money requirement is reached, the player can reset their base and receive scalable prestige levels with permanent bonuses. The result prioritizes server authority, reliable persistence, and flexible integration with the existing architecture in your game.
The prompt first requests the project’s Explorer context, objects, modules, and RemoteEvents to avoid invented names and broken dependencies. It is intended for developers who already have a functional tycoon and need to add an advanced progression layer that is safe and production-ready.
The expected output includes complete Luau code, commented and ready to paste into Roblox Studio, plus a practical step-by-step guide for setup and testing in both local and published environments.
Conteudo
Prompt principal
Act as a senior Roblox Luau developer, specialized in secure tycoon systems, persistence with DataStoreService, and server-authoritative architecture. I want to implement a prestige/reset system for my tycoon, where the player resets the current base progress upon meeting a money requirement and receives scalable permanent bonuses. Before writing the code, read and use strictly the context I will paste below. Do not invent object names, Explorer paths, module APIs, RemoteEvents, or data structures that are not provided. If any essential information is missing, first make a concise list of technical questions; only after I reply, generate the solution. If the context is complete, proceed directly to the code. MY GAME CONTEXT (to be filled in): - Where the player’s money is stored and the exact name of the Value/attribute/leaderstats: [PREENCHER] - Structure and path of the tycoons in the Explorer, including how to identify the owner of each base: [PREENCHER] - How the current base reset works, if it exists (functions, ModuleScripts, BindableEvents, or destroyed/recreated objects): [PREENCHER] - Existing RemoteEvents/RemoteFunctions and their respective paths: [PREENCHER] - Existing prestige UI, if any, and the path to the button/labels: [PREENCHER] - Current saving system, DataStore modules, and profile format: [PREENCHER] - Initial money requirement, requirement growth per prestige, and desired bonus formula: [PREENCHER] - Which permanent bonuses should exist (e.g., income multiplier, starting cash, build speed, discount): [PREENCHER] - Maximum prestige limit, if any: [PREENCHER] - Any other rules, restrictions, and required names: [PREENCHER] Generate the main implementation as a server Script to be placed in ServerScriptService, with a suggested name such as PrestigeService.server.lua. If my context requires UI communication, use only the RemoteEvents already existing; if no suitable RemoteEvent exists, instruct exactly how to create a RemoteEvent in ReplicatedStorage with a suggested name and make it clear that it is only used to request a prestige attempt. Do not delegate any decision about balance, requirement, bonuses, inventory, reset, or saving to the client. The Script must implement: loading and saving the number of prestiges and permanent bonuses; centralized and configurable calculation of the requirement for the next prestige; a clear public or local function to obtain player multipliers; prestige attempt triggered by RemoteEvent or integration with the informed flow; validation of Player, loading state, money value, base ownership, money requirement, prestige limit, and prevention against repeated/spam requests; deduction or reset of money according to the provided rule; safe base reset by calling the real integration described in the context; atomic prestige increment; immediate update of replicated attributes/Values needed for UI; and success/failure notification using only the channels existing in the project. Use DataStoreService with pcall protection, keys by UserId, safe updates with UpdateAsync when appropriate, limited retry attempts, and saving in PlayerRemoving and BindToClose. Avoid overwriting data loaded by another system: if I provide a ProfileService, DataStore wrapper, or existing data module, integrate with it instead of creating a parallel DataStore. Handle loading failures conservatively: a player whose data is not confirmed loaded cannot prestige. Do not use DataStore in loops, do not yield inside critical callbacks, and do not use arbitrary waits as a synchronization mechanism. Follow Roblox security strictly: the client may only request an attempt; the server recalculates the requirement and confirms all real state. Never accept money value, prestige level, multiplier, tycoon name, bonus amount, or indication that reset was completed from the client. Apply rate limiting per player for the RemoteEvent and clear state tables when the player leaves. Protect calls to external modules with validations and useful warn messages for development, without exposing sensitive data to the client. Deliver the response in this order: 1) a brief summary of the architecture and assumptions adopted; 2) a list of prerequisites and objects I need to create or connect; 3) the full, functional, and commented Luau code, mandatorily inside a single markdown ```lua block; 4) an integration section indicating the exact points where I should adapt calls to my tycoon reset and income multiplier application; 5) detailed instructions to test in Roblox Studio, including testing with Start Server/Players, enabling API Services only in a published test experience, verifying DataStore, button spam, and player reconnection. Do not deliver pseudocode, incomplete snippets, critical-logic placeholders, or insecure client code. Whenever there is an unspecified dependency in the context, mark it in a comment with "ADAPT TO YOUR PROJECT" and explain precisely what to connect, while keeping the rest of the Script executable and coherent.
