Complete Roblox Tycoon: Plots, Passive Income, and Upgrades

# www.prompthubai.com.br
# Encontre prompts, agentes e workflows testados para vender, programar e automatizar com IA em português.

# Complete Roblox Tycoon: Plots, Passive Income, and Upgrades

## Cabecalho
- Tipo: Conteudo
- Categoria: Games
- Modulos: 0
- Agentes: 0

## Escopo
Generate a robust, production-ready Tycoon system for Roblox Studio, centralizing land ownership, economy, periodic income generation, and progression through upgrades on the server. The prompt requires a configurable architecture that adapts to the names, folders, buttons, and RemoteEvents already existing in your project.

Ideal for developers who want to create scalable tycoons without trusting the client for money, item purchases, or plot ownership. The requested response includes a complete, commented Luau Script, with anti-exploit validations, cleanup when the player leaves, support for multiple plots, and practical installation and testing instructions.

## Prompt Principal
Act as a senior Roblox developer, specialized in Luau, server-authoritative architecture, anti-exploit security, and scalable Tycoon systems. Generate a single complete Luau Script for the server that implements plot purchasing and management, automatic money generation, cash collection, and income upgrades.

SCRIPT TYPE AND LOCATION: deliver a Script (not a LocalScript and not a ModuleScript) to be inserted into ServerScriptService, with a suggested name such as `TycoonService.server.lua`. The script must be self-contained and organized into clear sections: configuration, hierarchy discovery/validation, in-memory data control, plot ownership, economy, production, purchases, cleanup, and event connections. Use only standard Roblox APIs, with no external dependencies. Do not generate local UI code; purchase interaction must work through the server using ProximityPrompt or ClickDetector present on the map's physical buttons. If my context already has a UI/RemoteEvent system, integrate it only as an optional visual update layer, without transferring authority to the client.

Before writing the code, consider and respect the context of my game below. If I leave out any data, do not ask follow-up questions: create configurable values at the top of the Script, document assumptions in comments, and implement safe fallbacks.

=== MY GAME CONTEXT (I WILL FILL THIS IN BEFORE SENDING) ===
- Plot folder in Workspace and internal structure of each plot:
- How to identify each plot (attribute, name, ID, etc.):
- Initial land purchase part/object:
- Part/object used to collect accumulated money:
- Folder or objects for the upgrade buttons:
- Format of each upgrade (Attributes, IntValues, names, costs, and effects):
- Existing leaderstats/currency (currency name and where it is located):
- Existing RemoteEvents/RemoteFunctions and their respective locations:
- Existing DataStore system, if any:
- Desired rules for initial price, base income, production interval, cash limit, and multipliers:
- Other relevant details:
=== END OF CONTEXT ===

MANDATORY FUNCTIONAL REQUIREMENTS:
1. When the player joins, find a free plot, assign ownership exclusively on the server, and update an `OwnerUserId` attribute or equivalent mechanism. If no plot is available, report it safely via warn and/or optional RemoteEvent.
2. Plot purchase must require sufficient balance. The server must validate the player, plot, reasonable distance from the player to the trigger, currency value, current ownership state, and anti-spam cooldown before deducting money. Never accept price, UserId, money amount, plot, or upgrade sent by the client as truth.
3. After purchase, enable the tycoon elements for that owner. Unlockable items must start hidden/inactive when applicable, while upgrade buttons can only be used by the plot owner. Preserve a configurable strategy for object transparency, collision, and prompts.
4. Implement automatic money generation per plot at configurable intervals. Income must consider a base income, droppers/income upgrades, and multipliers. Accumulate the value in a plot cash variable, expose it in a configurable Attribute/IntValue for visual integration, and allow collection only by the owner.
5. Implement configurable upgrades via a table at the top of the code, including at least: base income increase, production multiplier, and cash capacity increase. Each upgrade must have initial cost, cost growth, maximum level, and effect per level. The server must validate balance, level, ownership, and cooldown before applying any change.
6. When the player leaves, release the plot, stop or invalidate processes linked to it, zero out accumulated money according to configuration, and restore the initial visual/functional state. Also handle CharacterAdded to maintain interaction security. Do not use uncontrolled infinite loops per player; use `task.spawn`, `task.wait`, and state checks for cancelable production loops.
7. If there are RemoteEvents in the context, rigorously validate `typeof`, instances, ancestry, plot ownership, distance, numeric limits, and frequency before any action. RemoteEvents may notify the client about collected balance, accepted purchases, or failures, but they may not grant currency, buy upgrades, or define ownership without full new validation on the server.

QUALITY AND DELIVERY: use idiomatic Luau, `--!strict` when viable, `WaitForChild` carefully, `Attributes`, types when they improve clarity, and small functions with a clearly defined responsibility. Comment on critical security decisions and the points I need to adapt in the Explorer. Avoid pseudocode, omitted sections, fictional functions, and dependencies not provided. The code must be entirely inside a single markdown code block ```lua. After the block, provide clear instructions for installing the Script, configuring the expected structure in the Explorer, testing with two players using Start Server/Start Player mode in Roblox Studio, and validating common exploit attempts.