Data Folder Guide

TazUO Data Folder Guide

:warning: This was generated with AI and mildly proof read by a real human.

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

• Quick Backup Checklist
• Database Files
• Configuration Files
• Profile System
• Client Data Files
• File Structure Reference

---

Quick Backup Checklist

Essential Files to Backup (contains all your settings and character data):

• Data/Profiles/ - All character profiles and settings
• Data/settings.db - Global application settings
• Data/legionvars.db - Python script persistent variables
• Data/items.db - Item database for search/loot features

Optional Files to Backup:

• Data/Language.json - UI language customizations
• Data/GridHighlightSettings.json - Grid highlight property definitions
• Data/DiscordSettings.json - Discord integration settings
• Data/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

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

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

Purpose: SQLite database storing persistent variables for Python scripts

Contains:

• Variables saved by scripts using PersistentVars API
• 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

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

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

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

Purpose: Python scripting system configuration

Contains:

• Script editor settings
• Script execution preferences
• Legion scripting system configuration

Backup Priority: Low-Medium (if customized)

---

Profile System

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

Purpose: Remembers which character was last played

Backup Priority: Low (convenience only)

---

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]/

Purpose: Character-specific settings and configurations

Backup Priority: CRITICAL - This contains all your character customizations

Files in character/ Folder:

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

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

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

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

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

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

Contains:

• Journal/chat filter rules
• Message filtering preferences

Backup Priority: Medium (if customized)

Auto-Backups: Creates .backup1, .backup2, .backup3

---

skillsgroups.xml

Contains:

• Skill grouping configurations
• Custom skill organization in skills gump

Backup Priority: Low-Medium

---

SpellBar.json & SpellBarSettings.json

Contains:

• Custom spell bar configurations
• Spell button arrangements

Backup Priority: Medium (if you use custom spell bars)

---

TileMarkers.json

Contains:

• Map markers and waypoints
• Custom tile markers placed on the world map

Backup Priority: Low-Medium

---

infobar.xml

Contains:

• Info bar configuration
• Which information to display in the info bar

Backup Priority: Low

---

nameoverhead.xml

Contains:

• Nameplate/overhead display settings
• Custom nameplate configurations

Backup Priority: Low-Medium

---

Character-Specific Data Folders

[character-name]/

friends.json

Contains:

• Friends list for this character

Backup Priority: Medium

Auto-Backups: Creates .backup1, .backup2, .backup3

---

Client Data Files

Location: Data/Client/

These files contain static game data definitions that rarely change:

Static Data Files:

• cave.txt - Cave tile definitions
• chair.txt - Chair/furniture tile IDs for sit macro
• containers.txt - Container gump definitions
• lightshaders.txt - Light shader configurations
• lights.txt - Light source definitions
• seasons.txt - Season tile variations
• tree.txt - Tree tile definitions
• vegetation.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/

Purpose: Game journal/chat logs organized by date

Backup Priority: Low (unless you want to preserve chat history)

---

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

Data/
├── settings.db              # Global settings database
├── 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
│
├── 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
│               ├── SpellBar.json
│               ├── SpellBarSettings.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

Backing Up Before Major Changes

Recommended to backup:

• Data/Profiles/ (entire folder)
• Data/settings.db
• Data/legionvars.db (if using scripts)

Migrating to New Computer

Copy these:

• Data/Profiles/ (entire folder)
• Data/settings.db
• Data/legionvars.db
• Data/Language.json (if customized)
• Data/GridHighlightSettings.json (if customized)

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

1. Check for automatic backups (.bak1, .bak2, .bak3, .backup1, etc.)
2. Restore most recent backup by renaming (remove .bak1 suffix)
3. If no backups available, delete the corrupted file to regenerate defaults

Testing Experimental Settings

1. Create backup of relevant files first
2. Make changes
3. If issues occur, restore from backup

---

Tips and Best Practices

1. Regular Backups: Copy Data/Profiles/ folder regularly if you heavily customize settings

2. Cloud Storage: Consider placing Data/Profiles/ in cloud storage (Dropbox, Google Drive, etc.) for automatic backups

3. Version Control: Advanced users can use Git to track changes to configuration files

4. Multiple Characters: Each character has separate settings, but you can copy settings files inside character folders to copy settings over

5. Automatic Backups: TazUO creates automatic backups for most critical files (look for .bak1, .bak2, .bak3, .backup1, .backup2, .backup3)

6. Fresh Start: To reset everything to defaults, delete the Data/ folder and restart TazUO (it will regenerate with defaults)

7. Per-Setting Reset: Delete individual files to reset just those settings (e.g., delete macros.xml to reset only macros)

---

Troubleshooting

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

• Check automatic backup files (.bak1, .bak2, .bak3)
• Restore from backup by renaming

Corrupted Database

• Delete the .db file 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

• Verify folder structure matches: Profiles/[account]/[server]/[character]/
• Check that profile.json is valid JSON (use JSON validator)
• Try using automatic backup: profile.json.bak1

---

Summary

Most Important to Backup:

1. Data/Profiles/ - All character settings
2. Data/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