How k073l/s1-furnituredelivery works
Project type and purpose
• This is a Unity-based game mod written in C#, loaded via MelonLoader.
• Purpose: extend the in-game “deliveries” system by adding new furniture, equipment, curios, and weapons as shop items.
File structure
• Top level
• FurnitureDelivery.csproj – C# project file targeting .NET for Unity (IL2CPP and Mono builds)
• MainMod.cs – entry point for MelonLoader
• Patches.cs – Harmony or similar patches into game methods
• Helpers/ – builder classes and common utilities
• Interop/ – optional integration with the “More Guns” mod
• Shops/ – one class per shop, each declares a list of items
• assets/ – images (e.g. listing.png) for README or in-game UI
• build/ – MSBuild props and targets steering IL2CPP vs Mono packaging
README
• Confirms it’s a MelonLoader mod for a game with a “deliveries” app
• Lists four delivery services (“Dan’s Furniture”, “Oscar’s Equipment”, etc.) and their items
• Notes dependency on More Guns mod for some weapons
Main components and their relationships
a. Game Engine (Unity)
↳ MelonLoader injection layer
b. FurnitureDelivery Mod (loaded by MelonLoader)
• MainMod: mod metadata and bootstrap
• Patches: apply runtime hooks to game’s delivery UI and item registry
• Shop modules (Shops/*.cs): define and register each store’s offerings
• Helpers: builder patterns to construct shop items, logging, utility functions
• Interop: detects and integrates More Guns mod when present
c. External Services & Assets
• More Guns mod (optional)
• assets folder for UI sprites
Data flow:
Game startup → MelonLoader loads MainMod → Patches hook into delivery system → Shops classes invoke Helpers to build item definitions → Game’s delivery UI displays new items → (if installed) Interop augments with More Guns items
Architectural patterns and principles
• Plugin/Mod architecture: decoupled from game code via MelonLoader
• Builder pattern (DeliveryShopBuilder, LandVehicleBuilder) for item instantiation
• Conditional integration (Interop) for optional dependencies
• Separation of concerns: MainMod vs Patches vs Shops vs Helpers
Essential details
• Shop class under a “Shops” sub-component
• Call out Patches applying to game namespaces/methods
• Distinguish between pre-build (build/ folder) and runtime (MainMod/Patches)