Core Concepts
Understand the architecture and key concepts behind the ProStudios multiplayer ecosystem.
Ecosystem Overview
ProStudios connects multiple platforms and communities under one hub. You access everything from the central site at prostudios.net, which links to the official store, roleplay platforms, and Discord servers. This structure lets you move between services without leaving the ecosystem.
All official links route through prostudios.net or store.prostudios.net. Always verify you are on these domains before logging in.
Platform vs Community Distinction
You interact with ProStudios through two main layers: platforms and communities. Understanding the difference helps you navigate faster.
Platforms are the technical services you connect to. Examples include LFSPro at lfspro.net and the ProStudios Store. These handle game servers, accounts, and purchases.
Communities are the social spaces built around those platforms. Discord servers like LFSPro, Brasília Roleplay, and FivePRO provide support, events, and player interaction.
Roleplay Communities Explained
Roleplay communities form the core of ProStudios activity. Each server focuses on a specific theme:
- LFSPro: Focuses on racing and simulation roleplay.
- Brasília Roleplay: Centers on urban Brazilian scenarios.
- FivePRO: Covers FiveM-based GTA roleplay.
You join these servers through their dedicated Discord links. Moderators enforce rules and run events that keep the experience consistent across the ecosystem.
Support and Moderation Model
ProStudios provides 24/7 support through both platform staff and community moderators. You can reach support directly in any official Discord or via the store ticket system.
Moderators monitor chat, approve roleplay applications, and handle disputes. All reports go through verified channels listed on each Discord server. This layered approach keeps response times under one hour during peak periods.
Connecting to the Ecosystem
Use this example configuration when setting up your client for LFSPro:
{
"server": "lfspro.net",
"port": 7777,
"username": "your_prostudios_account",
"auth_token": "YOUR_API_KEY"
}
Replace YOUR_API_KEY with the token from your store dashboard. This same pattern works across other ProStudios platforms with minor port adjustments.
Last updated today
Built with Documentation.AI