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.