How berezaa/vesteria works
Project Type and Purpose
• This is a Roblox-based, full-stack game project (Vesteria MMORPG).
• It uses Rojo/VsCode for local development and synchronizes Lua scripts with Roblox’s hierarchy.
• Core purpose: provide client-server game logic, GUI, assets, shared modules, and persistent data services.
High-Level Architecture Components
a. Client (Player’s Device)
• StarterPlayerScripts & StarterCharacterScripts – local controllers, animations, input.
• StarterGui – UI screens (inventory, chat, quest log, etc.).
• ClientChatModules & ChatScript – client-side chat UI and command handling.
• RemoteEvents/RemoteFunctions – network layer to communicate with server.
b. Server (Roblox Servers)
• ServerScriptService
– contents/manager_* – gameplay managers (combat, quests, crafting, chat, etc.).
– analytics/GameAnalytics – external analytics integration.
– modules – reusable server modules (e.g., damage, economy, pathfinding).
• ChatServiceRunner – server side of chat system.
• DataStoreInterface – abstraction over Roblox DataStores for persistent player data.
c. Shared / Replicated Data
• ReplicatedStorage
– modules – shared libraries (utilities, events, physics, network).
– lookup tables – itemData, monsterLookup, statusEffectLookup, etc.
– temporaryEquipment, accessoryLookup, dialogue, sounds, assets.
d. External Services
• DataStores (Roblox built-in) for persistent storage.
• GameAnalytics (third-party) for telemetry.
Relationships & Data Flow
• Client → Server via RemoteEvents/RemoteFunctions
• Player inputs, interactions, chat messages go to server managers.
• Server → Client
• State updates (health, position, inventory), UI updates via RemoteEvents.
• Both → ReplicatedStorage
• Shared modules & lookup tables loaded locally on client & server.
• Server ↔ DataStoreInterface
• Persistent reads/writes (player progress, economy).
• Server → GameAnalytics
• Event tracking for analytics.
Important Architectural Patterns
• Modular Managers: each manager_* handles a distinct domain (e.g., manager_quest, manager_chat).
• Shared Module Library: utilities under ReplicatedStorage/modules to avoid duplication.
• MVC-like separation:
• Model: lookup tables & DataStore data.
• View: StarterGui, Chat UI.
• Controller: manager scripts & client scripts.
• Chat subsystem as microservice: Chat modules in src/Chat and ChatServiceRunner.
Including Submodules
• Under Client & Server, group related scripts and name submodules (e.g., manager_chat, manager_quest).