Data Folder Guide
TazUO Data Folder Guide
Section titled “TazUO Data Folder Guide”:warning: This was generated with AI and mildly proof read by a real human.
Overview
Section titled “Overview”The Data folder in your TazUO installation contains all user-specific settings, configurations, and saved states. This guide explains what each file does and which ones you may want to backup, copy, or customize.
Location: Data/ (in the same directory as the TazUO executable)
Table of Contents
Section titled “Table of Contents”- Quick Backup Checklist
- Database Files
- Configuration Files
- Profile System
- Client Data Files
- File Structure Reference
Quick Backup Checklist
Section titled “Quick Backup Checklist”Essential Files to Backup (contains all your settings and character data):
Data/Profiles/- All character profiles and settingsData/settings.db- Global application settingsData/legionvars.db- Python script persistent variablesData/items.db- Item database for search/loot features
Optional Files to Backup:
Data/Language.json- UI language customizationsData/GridHighlightSettings.json- Grid highlight property definitionsData/DiscordSettings.json- Discord integration settingsData/lscript.json- Python scripting configuration
Safe to Skip:
Data/Client/- Static game data (regenerated if missing)Data/*.db.1,*.db.2,*.db.3- Automatic backup files
Database Files
Section titled “Database Files”settings.db
Section titled “settings.db”Purpose: SQLite database storing global application settings (not character-specific)
Contains:
- Window positions and sizes
- Global UI preferences
- Application-level configurations
Backup Priority: Medium (settings can be reconfigured, but saves time)
Automatic Backups: Yes - creates settings.db.1, settings.db.2, settings.db.3 automatically
When to Restore:
- Migrating TazUO to a new computer
- Recovering from corrupted settings
- Reverting problematic configuration changes
items.db
Section titled “items.db”Purpose: SQLite database caching item information for fast search and filtering
Contains:
- Item IDs, names, and properties seen in-game
- Used by grid loot system and item search features
- Built dynamically as you encounter items
Backup Priority: Low (regenerates automatically during gameplay)
Notes:
- Deleting this file is safe - it will rebuild as you play
- Larger file = more comprehensive item database
- Useful to copy if you want another character to have same item recognition
legionvars.db
Section titled “legionvars.db”Purpose: SQLite database storing persistent variables for Python scripts
Contains:
- Variables saved by scripts using
PersistentVarsAPI - Supports global, server, account, and character scopes
- Critical for scripts that maintain state between sessions
Backup Priority: High (if you use Python scripting)
Scopes:
- Global: Shared across all characters and servers
- Server: Shared across all accounts on a specific server
- Account: Shared across all characters on a server/account
- Character: Specific to one character
When to Restore:
- Script data is missing or corrupted
- Transferring script configurations between installations
- Recovering script state after reinstallation
Configuration Files
Section titled “Configuration Files”Language.json
Section titled “Language.json”Purpose: Customizable UI text and localization strings
Contains:
- Button labels, menu text, tooltips
- Error messages and notifications
- All user-facing text in modern UI elements
Backup Priority: Low-Medium
Customization:
{ "TazUOWiki": "TazUO Wiki", "TazUODiscord": "TazUO Discord", "CommandGump": "Available Client Commands"}Notes:
- Auto-regenerates with default values if deleted
- Edit to create custom translations or modify UI text
- File is updated automatically when new UI elements are added
GridHighlightSettings.json
Section titled “GridHighlightSettings.json”Purpose: Defines item properties available for grid container highlighting
Contains:
- Property names (e.g., “Damage Increase”, “Hit Chance Increase”)
- Resistance types (Physical, Fire, Cold, Poison, Energy)
- Negative properties (Antique, Brittle, Cursed, etc.)
- Slayer types (Demon Slayer, Dragon Slayer, etc.)
- Rarity tiers (Minor Artifact, Legendary Artifact, etc.)
Backup Priority: Low (rarely customized)
Customization Use Cases:
- Adding custom property names for specific shards
- Removing properties not relevant to your server
- Organizing properties in a preferred order
Example Section:
{ "Properties": [ "Damage Increase", "Hit Chance Increase", "Swing Speed Increase" ], "Slayers": [ "Dragon Slayer", "Demon Slayer" ]}DiscordSettings.json
Section titled “DiscordSettings.json”Purpose: Discord Rich Presence integration configuration
Contains:
- Discord application ID
- Rich presence settings
Backup Priority: Low
Notes:
- Only relevant if using Discord integration
- Auto-generated if missing
lscript.json
Section titled “lscript.json”Purpose: Python scripting system configuration
Contains:
- Script editor settings
- Script execution preferences
- Legion scripting system configuration
Backup Priority: Low-Medium (if customized)
Profile System
Section titled “Profile System”Directory Structure
Section titled “Directory Structure”Data/Profiles/├── lastcharacter.json # Last played character reference├── default.json # Default profile template└── [account-name]/ └── [server-name]/ └── [character-name]/ ├── profile.json ├── gumps.xml ├── macros.xml ├── AutoLoot.json ├── grid_containers.json └── ...Profiles/lastcharacter.json
Section titled “Profiles/lastcharacter.json”Purpose: Remembers which character was last played
Backup Priority: Low (convenience only)
Profiles/default.json
Section titled “Profiles/default.json”Purpose: Template for new character profiles
Backup Priority: Medium (if you’ve customized default settings)
Use Cases:
- Set preferred default settings for all new characters
- Quickly configure new characters with your preferences
Profiles/[account]/[server]/[character]/
Section titled “Profiles/[account]/[server]/[character]/”Purpose: Character-specific settings and configurations
Backup Priority: CRITICAL - This contains all your character customizations
Files in character/ Folder:
Section titled “Files in character/ Folder:”profile.json
Section titled “profile.json”Contains:
- Window positions (paperdoll, skills, containers, etc.)
- Video settings (resolution, FPS, graphics options)
- Audio settings (volume, music, sound effects)
- Macro definitions
- Game options (tooltip settings, filters, UI preferences)
- Grid highlight configurations
- Cooldown bar settings
- Nameplate preferences
- Combat and spell settings
Backup Priority: CRITICAL
Auto-Backups: Creates .bak1, .bak2, .bak3 automatically
Notes:
- This is the most important file per character
- Contains EVERYTHING about how your character’s client is configured
- Loss of this file means reconfiguring all settings from scratch
gumps.xml
Section titled “gumps.xml”Contains:
- Positions and states of all UI windows
- Which gumps (UI windows) were open/closed
- Window anchoring and grouping
Backup Priority: High
Recovery: Deleting resets all window positions to defaults
macros.xml
Section titled “macros.xml”Contains:
- All macro definitions
- Keybindings and hotkey assignments
- Macro sequences and actions
Backup Priority: High (if you use custom macros)
Sharing: Can copy this file to share macros between characters
AutoLoot.json
Section titled “AutoLoot.json”Contains:
- Auto-loot rule configurations
- Item filters for automatic looting
- Loot priority settings
Backup Priority: High (if configured)
Auto-Backups: Creates .backup1, .backup2, .backup3
grid_containers.json
Section titled “grid_containers.json”Contains:
- Grid container configurations
- Item highlighting rules per container
- Grid layout preferences
Backup Priority: High (if customized)
Auto-Backups: Creates .backup1, .backup2, .backup3
OrganizerConfig.json
Section titled “OrganizerConfig.json”Contains:
- Item organizer agent configurations
- Rules for organizing items between containers
Backup Priority: Medium (if configured)
Auto-Backups: Creates .backup1, .backup2, .backup3
journal_filters.json
Section titled “journal_filters.json”Contains:
- Journal/chat filter rules
- Message filtering preferences
Backup Priority: Medium (if customized)
Auto-Backups: Creates .backup1, .backup2, .backup3
skillsgroups.xml
Section titled “skillsgroups.xml”Contains:
- Skill grouping configurations
- Custom skill organization in skills gump
Backup Priority: Low-Medium
TileMarkers.json
Section titled “TileMarkers.json”Contains:
- Map markers and waypoints
- Custom tile markers placed on the world map
Backup Priority: Low-Medium
infobar.xml
Section titled “infobar.xml”Contains:
- Info bar configuration
- Which information to display in the info bar
Backup Priority: Low
nameoverhead.xml
Section titled “nameoverhead.xml”Contains:
- Nameplate/overhead display settings
- Custom nameplate configurations
Backup Priority: Low-Medium
Character-Specific Data Folders
Section titled “Character-Specific Data Folders”[character-name]/
Section titled “[character-name]/”friends.json
Section titled “friends.json”Contains:
- Friends list for this character
Backup Priority: Medium
Auto-Backups: Creates .backup1, .backup2, .backup3
Client Data Files
Section titled “Client Data Files”Location: Data/Client/
These files contain static game data definitions that rarely change:
Static Data Files:
Section titled “Static Data Files:”cave.txt- Cave tile definitionschair.txt- Chair/furniture tile IDs for sit macrocontainers.txt- Container gump definitionslightshaders.txt- Light shader configurationslights.txt- Light source definitionsseasons.txt- Season tile variationstree.txt- Tree tile definitionsvegetation.txt- Vegetation tile definitions
Backup Priority: Very Low
Notes:
- These files are regenerated from embedded resources if missing
- Safe to delete if corrupted
- Rarely need customization unless modifying game rendering
Client/JournalLogs/
Section titled “Client/JournalLogs/”Purpose: Game journal/chat logs organized by date
Backup Priority: Low (unless you want to preserve chat history)
Asset Overrides (Loose Files)
Section titled “Asset Overrides (Loose Files)”TazUO can load loose game assets that add to or override the client’s archives, without
repacking .mul/.uop files. Place them in the client folder:
- Static art —
Art/Statics/<id>.art(referenced by the static graphic id). - Land tiles —
Art/Land/<id>.art(referenced by the raw land id, a 2024-byte tile). - Gumps —
Gumps/<id>.gump. - Sounds —
Sounds/<id>.wav(22050 Hz, mono, 16-bit WAV).
Clilocs.txt
Section titled “Clilocs.txt”Purpose: A plain-text cliloc override file placed in the client folder. Each line has a
cliloc number, whitespace, then the text; # starts a comment. Use it to add or
override cliloc strings without editing the .cliloc files.
Backup Priority: Low-Medium (if you maintain custom strings)
XmlGumps Folder
Section titled “XmlGumps Folder”Location: Data/XmlGumps/
Purpose: Custom XML-based UI gumps from servers
Contains:
- Server-provided custom UI elements
- Usually empty unless server uses XmlGumps system
Backup Priority: Low
File Structure Reference
Section titled “File Structure Reference”Data/├── settings.db # Global settings database├── global_settings.json # Machine-wide settings (WASD movement, circle of transparency, sound/music, etc.)├── items.db # Item database cache├── legionvars.db # Script persistent variables├── Language.json # UI text/localization├── GridHighlightSettings.json # Grid highlight properties├── DiscordSettings.json # Discord integration├── lscript.json # Script configuration│├── [ServerName]/│ ├── server_settings.json # Per-server settings (e.g. turn delay)│ └── [Account]/│ └── account_settings.json # Per-account settings (e.g. bandage distance)│├── Profiles/│ ├── lastcharacter.json│ ├── default.json│ └── [account]/│ └── [server]/│ └── [character]/│ ├── friends.json│ ├── profile.json # CRITICAL│ ├── gumps.xml│ ├── macros.xml│ ├── infobar.xml│ ├── nameoverhead.xml│ ├── skillsgroups.xml│ ├── AutoLoot.json│ ├── grid_containers.json│ ├── OrganizerConfig.json│ ├── journal_filters.json│ ├── hotkeys.json│ └── TileMarkers.json│├── Client/│ ├── cave.txt│ ├── chair.txt│ ├── containers.txt│ ├── lightshaders.txt│ ├── lights.txt│ ├── seasons.txt│ ├── tree.txt│ ├── vegetation.txt│ └── JournalLogs/│ └── [date-based logs]│└── XmlGumps/ └── [server-provided gumps]Common Scenarios
Section titled “Common Scenarios”Backing Up Before Major Changes
Section titled “Backing Up Before Major Changes”Recommended to backup:
Data/Profiles/(entire folder)Data/settings.dbData/legionvars.db(if using scripts)
Migrating to New Computer
Section titled “Migrating to New Computer”Copy these:
Data/Profiles/(entire folder)Data/settings.dbData/legionvars.dbData/Language.json(if customized)Data/GridHighlightSettings.json(if customized)
Sharing Configuration with Friend
Section titled “Sharing Configuration with Friend”For same settings across characters:
Data/Profiles/[account]/[server]/[character]/profile.json- Adjust paths as needed, some settings are server/character specific
For sharing macros only:
Data/Profiles/[account]/[server]/[character]/macros.xml
For sharing auto-loot rules:
Data/Profiles/[account]/[server]/[character]/AutoLoot.json
Recovering from Corruption
Section titled “Recovering from Corruption”- Check for automatic backups (
.bak1,.bak2,.bak3,.backup1, etc.) - Restore most recent backup by renaming (remove
.bak1suffix) - If no backups available, delete the corrupted file to regenerate defaults
Testing Experimental Settings
Section titled “Testing Experimental Settings”- Create backup of relevant files first
- Make changes
- If issues occur, restore from backup
Tips and Best Practices
Section titled “Tips and Best Practices”-
Regular Backups: Copy
Data/Profiles/folder regularly if you heavily customize settings -
Cloud Storage: Consider placing
Data/Profiles/in cloud storage (Dropbox, Google Drive, etc.) for automatic backups -
Version Control: Advanced users can use Git to track changes to configuration files
-
Multiple Characters: Each character has separate settings, but you can copy settings files inside character folders to copy settings over
-
Automatic Backups: TazUO creates automatic backups for most critical files (look for
.bak1,.bak2,.bak3,.backup1,.backup2,.backup3) -
Fresh Start: To reset everything to defaults, delete the
Data/folder and restart TazUO (it will regenerate with defaults) -
Per-Setting Reset: Delete individual files to reset just those settings (e.g., delete
macros.xmlto reset only macros)
Troubleshooting
Section titled “Troubleshooting”Settings Not Saving
Section titled “Settings Not Saving”- Check file permissions on
Data/folder - Ensure TazUO has write access
- Look for error messages in logs
Lost Macros/Settings After Update
Section titled “Lost Macros/Settings After Update”- Check automatic backup files (
.bak1,.bak2,.bak3) - Restore from backup by renaming
Corrupted Database
Section titled “Corrupted Database”- Delete the
.dbfile to regenerate - For
items.db: Safe to delete (rebuilds automatically) - For
settings.db: Use backup or reconfigure - For
legionvars.db: Restore from backup if you have script data
Profile Not Loading
Section titled “Profile Not Loading”- Verify folder structure matches:
Profiles/[account]/[server]/[character]/ - Check that
profile.jsonis valid JSON (use JSON validator) - Try using automatic backup:
profile.json.bak1
Summary
Section titled “Summary”Most Important to Backup:
Data/Profiles/- All character settingsData/legionvars.db- Script data (if using scripts)
Everything Else: Either regenerates automatically or is less critical
Best Practice: Periodically backup the entire Data/ folder for complete peace of mind