WoWDatabaseEditor: an IDE for Smart Scripts and databases on TrinityCore servers

An emulator admin tool, not a game

The project describes itself as an integrated development environment and an editor for Smart Scripts, known as SAI or smart_scripts, for TrinityCore based servers, with a 3D view built using OpenGL and a custom ECS framework. The README shortens it to an IDE for Smart Scripts and database editing for TrinityCore based servers. The audience is narrow and specific: the people who run World of Warcraft emulator servers, which are the open source server implementations used for private and community game servers, and who write the scripts that drive everything from quest behaviour to vendor logic. Those people normally edit a table in a MySQL database, a script in a text file, and a DBC or map file, in three different places with three different tools, and this project puts all of it behind one window. The project is MIT licensed, the primary language is C#, the framework is Avalonia, and the last push to the repository was on 2026-08-16.

A rewrite of Visual SAI Studio, and why that matters

The project is a continuation of Visual SAI Studio, but rewritten from scratch, and the acknowledgements section says the editor began as an internal tool at Atlantiss. That origin explains the emphasis on the 3D view and the map renderer, because a tool born inside a company that runs its own emulators would be shaped by what those teams needed. The README is unusually blunt about the current state, saying that smart script and database editing is already in good enough shape to use it on a daily basis, and that there is still a lot to do in the IDE. The repository topics reflect a project in active development rather than a finished product, with azerothcore-tools, cmangos, trinitycore, smartscript and hacktoberfest2022 among them, and the description itself says Cmangos support is work in progress. The top level entries show the scale: a DBCD directory for the client data files, a Dock and Rendering directory for the 3D side, an Updater directory, and then a long list of WDE.* modules covering the actual functionality, from WDE.SmartScriptEditor and WDE.DatabaseEditors through WDE.Conditions, WDE.EventAiEditor, WDE.MPQ, WDE.SQLEditor, WDE.PacketViewer, WDE.MapRenderer, WDE.Blueprints, WDE.Spells and WDE.Solutions.

Smart Scripts, databases, DBC files and a 3D map view

The feature set maps onto the artefacts an emulator administrator actually juggles. The Smart Script editor handles the SAI scripts, and the Event AI editor, in a couple of named modules, covers the event scripting side, with a CMaNGOS variant present as its own directory. The database editors work against the server's MySQL tables, and there is a separate SQL editor module, plus a Parameters module for the server's configuration values. The DBC directory handles the client data files, with a separate database tester for exercising the tables. The Rendering directory and the map renderer provide the 3D view, which is the feature that distinguishes this from a plain database GUI, since a server's geometry and the placement of creatures on it are far easier to reason about visually than from coordinates in a text file. There is also an MPQ reading module, a packet viewer, a solutions module for sharing configurations, and a source code integration editor.

Running it needs the .NET 8 runtime, and updates arrive on their own

The download section is direct about the requirement. To run the editor you need the.NET 8 Runtime for your operating system, and the application is compatible with macOS, Linux and Windows. It ships as three zips, one per platform, with the Windows build linked from the AppVeyor artifact service and the Linux and macOS builds coming from the GitHub releases. The README asks you to use the version from GitHub Releases and update via the application for those two, because the application has a built-in auto updater, so you do not have to redownload a zip to upgrade. There is an important asymmetry there, because the Windows artifact is a build output from CI while the other two are release assets, and the instructions for each differ. The tagged releases are named by build number, and the release titles themselves say the application will autoupdate to the latest version, which is how a tool that publishes infrequently still keeps users current.

Building it yourself, with submodules and a specific start project

To build rather than download, you need the .NET 8.0 SDK, and if you want to use Visual Studio you need Visual Studio 2022, because older versions do not support the required .NET version. The project uses git submodules, so after cloning or pulling you have to initialise them, and the README is explicit that this step is not optional.

git submodule update --init --recursive

You can then open the solution in Visual Studio or any other C# or .NET IDE and build it. One detail catches people: you start the LoaderAvalonia project, and the README flags this part as important. Producing a distributable build means running one dotnet publish per platform, each writing to its own output directory and targeting a runtime identifier.

-- Windows version
dotnet publish -c Release --self-contained false -f net8.0 -o bin/wowdatabaseeditor-avalonia-win/ LoaderAvalonia/LoaderAvalonia.csproj -r win7-x64

-- MacOS version
dotnet publish -c Release --self-contained false -f net8.0 -o bin/wowdatabaseeditor-avalonia-mac/ LoaderAvalonia/LoaderAvalonia.csproj -r osx-x64

A Linux target follows the same shape with the linux-x64 runtime identifier. The --self-contained false flag is what produces the smaller build that still needs the .NET 8 runtime installed, which matches the download instructions.

Which server versions are actually supported

The supported versions list is the shortest and most useful thing in the README for anyone deciding whether this tool fits their server. The supported database versions are TC 3.3.5, TC 4.3.4 which the README calls the preservation project, TC master which is 10.0.x, and AzerothCore 3.3.5. The supported DBC versions are 3.3.5, 4.3.4 and 10.x. So the coverage is not the full spread of emulator forks and client versions, and the two lists are not identical, which means a combination can be workable for the database and not for the client files. TrinityCore gets three lines including master, AzerothCore gets one, and Cmangos is in the description as work in progress rather than in the supported list. For an administrator running a fork that is not on that list, the tool is not usable as shipped, and there is no statement in the README about what happens when you point it at an unsupported schema, so that is the first thing to check on a copy of your own database before trusting an edit.

Where WoWDatabaseEditor is the wrong choice

Three limits stand out. The first is the release history. The tagged releases are 2021.3.01 from January 2022, build2397 in December 2023 and build2659 in March 2024, and while the repository is pushed to as recently as August 2026, the tagged artefacts people download are old, and a project whose own release titles promise auto-update is relying on an updater that can only ship what CI produces. The second is the Cmangos gap, which the description labels work in progress, so if your server runs Cmangos you are testing something the project does not claim to support. The third is the platform of the emulator itself. Every supported target is a TrinityCore or AzerothCore server, and if you are a retail player, a server developer on another emulator, or someone who wants a general purpose database GUI, this is a tool with no purpose for you. The alternative worth naming is the combination it replaces: a MySQL client for the tables, a text editor for the scripts, a separate DBC and map tool, and a separate 3D viewer, which is more tools but each one is general, well maintained and independently replaceable. What you buy here is the integration, and what you pay is that the integration is locked to a specific emulator family and a specific set of versions.

Editorial conclusion

Adopt WoWDatabaseEditor if you maintain a TrinityCore or AzerothCore private server and want a single tool for Smart Script authoring, database tables, DBC files and a 3D view instead of editing SQL and text files by hand. Do not adopt it if you need Cmangos support, which the project description marks as work in progress, or if you want a maintained release cadence, since the newest tagged build is from March 2024 while the repository itself is pushed to more recently. Verify first that the emulator version and database schema you run are in the supported list, and plan on building from source rather than downloading a zip.

Frequently asked questions

Official sources

1. BAndysc/WoWDatabaseEditor on GitHub
2. Issues
3. License: MIT
4. README
5. Releases