How t3rius/t3_winemakerjob works
Main Components
• Client Component: Represented by the code in the "client" folder (client/main.lua). This part handles in-game UI and interactions, such as displaying menus (boss menu), handling user inputs, and managing local game events.
• Server Component: Shown as the "server" folder (server/main.lua). It processes the core logic such as validating job actions, synchronizing state, handling business logic (harvesting, wine production steps), and communicating with the client.
• Configuration & Manifests: Include the shared configuration file ("config.lua") and the resource manifest ("fxmanifest.lua"). These files set up how the mod is loaded by the game runtime and provide key settings needed by both the client and server.
• Locales: The "locales" folder contains several language files (cs.lua, en.lua, et.lua). This represents the internationalization (i18n) layer to adapt in-game texts for various languages.
• Database/SQL: Include the "t3_winemakerjob.sql" file which likely sets up database schema or data required for tracking job progress, inventory items, and persistence of records.
• External Dependencies: Explicitly note external libraries (ox_lib and ox_target) as supporting components, which provide additional functionalities like target interactions and utility methods.
Relationships and Data Flows
• Directional Communication:
Important Architectural Patterns
• Separation of Concerns: The clear split between client-side and server-side logic improves modularity.
• Configurable and Internationalized Design: The presence of a central configuration file and dedicated locales support an adaptable system.
• External Integration: The use of external modules (ox_lib, ox_target) indicates a plugin-friendly design.