A standalone class mod focused on making each class desireable in their own right, with unique appeals for each.
Join the Official GlooMeClasses Discord Server for bug reporting and community assistance!
- Vintage Story 1.21.0 or higher
- .NET 8.0 Runtime (for development)
- Download the latest release from the Vintage Story Mod DB
- Place the
.zipfile in yourModsfolder - Launch Vintage Story
# Clone the repository
git clone https://github.com/GlooMeGlo/GlooMeClasses.git
cd GlooMeClasses
# Build the mod (Linux/macOS)
./build.sh
# Build the mod (Windows)
.\build.ps1
# Or build directly with dotnet
dotnet build GloomeClasses.csprojBuild Output: bin/Release/Mods/mod/
- .NET 8.0 SDK
- Vintage Story 1.21.0+ installed
- C# IDE (VS Code, Visual Studio, etc.)
The project auto-detects your Vintage Story installation:
- Windows:
%APPDATA%/Vintagestory - Linux (Flatpak):
/var/lib/flatpak/app/at.vintagestory.VintageStory/... - Linux (Native):
~/.config/VintagestoryData
Override with environment variable:
export VINTAGE_STORY="/path/to/vintagestory"# Full build with JSON validation
./build.sh
# Skip JSON validation (faster development builds)
./build.sh --skipJsonValidation
# Release package (creates zip in Releases/)
./build.sh --target=PackageGloomeClasses now includes comprehensive diagnostic logging to help troubleshoot mod conflicts and issues.
Client-side: Check VintagestoryData/Logs/client-*.txt
Server-side: Check VintagestoryData/Logs/server-*.txt
Look for messages with [GloomeClasses] prefix.
When reporting issues, please include:
- Full
[GloomeClasses]log section from client-debug.txt or server-debug.txt - List of other mods installed (especially character/class mods)
- Game version and whether singleplayer or multiplayer
- Exact steps to reproduce the issue
The diagnostic logging is designed to help identify what's happening on your system.