Random name generator (3-column) always creates "minifig<ID>" characters

[theo7791l]

I used AI to write this because I'm French and my English is too poor to explain it properly, sorry 😅

Environment

• Server Image: ghcr.io/darkflameuniverse/darkflameserver:latest (v3.0.0, compiled Feb 23 2026)
• Database: MariaDB 10.11 (external, shared with web backend)
• Config: SQLITE_DATABASE_PATH=resServer/dlu.sqlite, DATABASE_TYPE=mariadb, CLIENT_NET_VERSION=171022
• Client: Official DarkflameUniverse client with cdclient.fdb (41 MB, Firebird format, SHA256: 875d887f...)

Issue Description
When creating a character using the 3-column random name generator (Prefix + Middle + Suffix) in the LEGO Universe client, the character is always created with the name minifig<bigint_id> instead of the selected name (e.g., CandidLaserReindeer).

Creating a character with a manually typed name works perfectly.

Server Logs

[06-04-26 10:08:48 UserManager.cpp:347] AccountID: 4 is creating a character with predefined name: INVALID
[06-04-26 10:08:48 Character.cpp:81] Loaded xmlData for character minifig1152921504606850578 (...)

What We've Verified
cdclient.fdb (41 MB, Firebird) is present and valid on the VPS
CDServer.sqlite (16 MB) is present and valid in /app/resServer/
general.ini contains allow_random_name = true
SKIP_ACCOUNT_CREATION=0 is set
CLIENT_NET_VERSION matches client (171022)
MariaDB connection works (accounts/characters persist correctly)
Manual name entry works → bug is isolated to predefined/random name flow only
Same client works correctly on other public DLU servers

What We've Tried (Without Success)
Placing cdclient.fdb in /app/resServer/ → server uses CppSQLite3DB which expects SQLite, not Firebird
Attempted to locate an official cdclient.fdb → SQLite conversion script in this repo, but did not find one explicitly documented
Downloading dlu.sqlite/CDClient.sqlite from GitHub releases → only server binaries are provided, no database files
Using CDServer.sqlite as dlu.sqlite → file does not appear to contain any obvious name validation tables

Questions for Maintainers

1. Which SQLite file is expected by the Docker image for name validation: dlu.sqlite, CDClient.sqlite, or another?
2. Is there an official/pre-converted SQLite file containing the name tables (e.g. valid_name_prefixes, valid_name_suffixes, Objects) that we can/should use?
3. Is the predefined name: INVALID → minifig<ID> behavior a known issue in v3.0.0, or is there a configuration step I'm missing?
4. Does the random name generation rely on server-side validation, client-side data, or both?

Workaround
Players can create characters by typing names manually — this works reliably.

Additional Context
This is a private server project (Universe Reborn) with a separate Flask/React web backend sharing the same MariaDB instance. All other functionality (auth, gameplay, dashboard) works correctly. The issue appears isolated to the predefined name flow in this specific Docker setup.

I also noticed discussion #1470 mentioning “make predefined name unique when the name files are not provided”, which seems related to this behavior (predefined name logged as INVALID then falling back to minifig<ID> in my case).

[EmosewaMC]

It is required that the res\names folder exist with the minifig_* file names in it, the database is not relevant here, only whether or not the files exist. If you're seeing names with those unique IDs, then it sounds like those files are empty for some reason. Please confirm those files have text in them and that the client you are using to connect with the server also has those exact same files in it. You are also on a very old version of DLU (3.0.0) so its possible that bug is fixed on a future release. We will make sure to update the releases so you can pull that down and check it.

[EmosewaMC]

I also have no idea what "Universe Reborn" is or many of the terminologies used here. Darkflame Universe is only meant to be used with the Nexus Dashboard backend.

[EmosewaMC]

to directly answer the questions
1 none
2 no
3 Odds are the answer to number 4 will help more
4 the files minifigname_first.txt, minifigname_middle.txt and minifigname_last.txt must exist and be the exact same on the server and client.