MoP Premium Repack

[Parzival]

Ich habe ein Problem. Ich starte den Server, aber er schaltet sich immer an dieser Stelle ab:


Emucoach 5.4.8 Rev: 7.0 Release Hash: b63112eec24e0c9029b1cd7517c8f7f79c7efe13 (Win64, Little-Endian) (Worldserver Daemon) bereit...

708 Spieler-Bot-Bedingungen geladen (176 ms)
688 Spieler-Bot-Aktionen geladen (31 ms)
Reisedaten des Spieler-Bots geladen (37 ms)

Es scheint, als würden die Bots nicht richtig geladen.

 

[Amasov]

Tridu, ich denke hier gibt es keinen deutschen Support.

(english: Tridu, I think here is no german support.)

 

[Parzival]

I have a problem. I start the server, but it always shuts down at this point:


Emucoach 5.4.8 Rev: 7.0 Release Hash: b63112eec24e0c9029b1cd7517c8f7f79c7efe13 (Win64, Little-Endian) (Worldserver Daemon) ready...

708 player bot conditions loaded (176 ms)
688 player bot actions loaded (31 ms)
Player bot travel data loaded in 37 ms

It seems like the bots are not being loaded properly.

 

[Parzival]

How can I make sure that the bots are loaded correctly now?

 

[Kneuma]

Hey Parzival — quick thing: your log actually shows the bots DID load fine (conditions, actions, travel data all loaded with timings). So it's not a bot-loading failure — the worldserver is crashing right after playerbot init.

I ran into this exact thing on my own Premium server (you're Rev 7.0, I'm 7.1 — same issue family). It's a known PlayerBot crash: the bots kick in on boot and the server falls over. What stopped it for me, in worldserver.conf:
• PlayerBots.PlayerbotEnableWorld = 0
• Lower PlayerBots.PlayerbotAmount (I use 100; try 30 if it still crashes)
• Restart the worldserver after

That keeps LFG/BG/Arena/alt bots working — it just stops the open-world bot spam that triggers the crash.

It's a core bug in the repack, not something we can fully fix as users — there's already a bug report for it (#18805 in the Mists of Pandaria Reports section) so the devs are aware. If that doesn't stop it, post the actual last lines of that crash .txt you attached + your DBErrors.log and I'll take a closer look.

 

[Parzival]

Leider funktioniert es immer noch nicht. Hier sind die Absturzprotokolle nochmals.

 

[Kneuma]

@Parzival thanks for the log. Honest read: this one looks different from what I expected. The crash is a C0000005 inside MSVCP140.dll (_Thrd_yield), which does NOT match the signature of the known PlayerBot GUID-overflow crash — that one crashes via a deliberate null-write through the creature/ObjectMgr path and prints a specific line to the console/Server.log first. So I don't want to wrongly tell you "it's that one"; this dump alone can't confirm it (and the worldserver addresses aren't symbolicated).

The one thing that pins it down: check your Server.log / console window at the crash time. If you see `ASSERTION FAILED: ... Creature guid overflow!`, then it IS the known GUID crash and the `PlayerbotEnableWorld=0` workaround applies. If there's no such line, it's likely something else and we shouldn't assume.

To help whoever digs in (ExO's collecting these): roughly how long was the server up before it crashed — seconds after startup, or hours? Do you run playerbots, and how many? Any worldserver.conf changes? What was happening in-game?

(Nebenbei: ich spreche auch Deutsch — erklär ruhig auf Deutsch wenn's einfacher ist; den Thread halte ich auf Englisch, damit Staff & andere folgen/suchen können.)

 

[Parzival]

wenn er hier ist
============================================
Initialisierung des eingebetteten LLM...
Modellname aus der Konfiguration: tinyllama-1.1b-chat-v1.0.Q4_K_M.gguf
KI-Modell gefunden: tinyllama-1.1b-chat-v1.0.Q4_K_M.gguf
LoadModel wurde mit folgendem Pfad aufgerufen: ./ai_models/tinyllama-1.1b-chat-v1.0.Q4_K_M.gguf so kommt der Absturz so 5 Sekunden beim Start

 

[Parzival]

Habe hier auch noch mal die DBErrors und Server Log

 

[Parzival]

Habe hier auch noch mal die DBErrors und Server Log

 

[Kneuma]

@Parzival your log nails it — the crash is at the embedded-LLM load (Initializing embedded LLM → LoadModel ./ai_models/tinyllama…gguf → crash ~5s in). So it's not the GUID overflow (matches what I said before — the dump didn't fit that signature). It's the repack's optional PlayerBots AI-chat feature (self-contained llama.cpp).

Workaround to get you running: in worldserver.conf set PlayerBots.AI.Enabled = 0 (around line ~3641, default 1) and restart the worldserver. That stops the embedded LLM loading entirely, so it skips the LoadModel step that's crashing for you — bots still work, you just don't get AI-generated chat.

Honestly, fwiw I keep it off on my own server on purpose: I work with LLMs every day and it's a genuinely cool system, but bot chat is only ever as good as the model you give it, and it costs resources. Neat feature, but for a stable server I personally prefer it disabled — so you're really not losing much by turning it off.

Why the LLM load itself crashes on your machine I can't tell from here, and that embedded LLM is an EmuCoach-specific addition (not in the open core), so the crash itself is one for the devs — worth dropping that Server.log snippet (the LLM init lines + the ~5s crash) into the bug thread #15847 / to ExO so they can look at the LoadModel crash. The PlayerBots.AI.Enabled=0 is just to get you playing now.

(Kurz auf Deutsch: der Absturz passiert beim Laden des eingebetteten LLM — optionales KI-Chat-Feature für Bots. Workaround: in worldserver.conf PlayerBots.AI.Enabled = 0 setzen und Worldserver neu starten — dann wird das LLM gar nicht geladen, der Absturz an der Stelle entfällt. Bots laufen normal weiter, nur ohne KI-Chat — meiner Meinung nach kein großer Verlust. Warum das LLM-Laden selbst abstürzt, müssen die Devs anschauen.)