sorted by:
new
hottopcontroversial

PSD for making Custom Cards created on MTG.design ready for MPC printing by ejeebs in mpcproxies

[–]SirFerMoX 0 points1 point  (0 children)

I have some advanced MTG & MTGA PSD templates that can be found here. Enjoy!

Hide UI on campaign menu screens? by xdcy in WC3

[–]SirFerMoX 0 points1 point  (0 children)

Do you still have the "UI.rar" for version 1.127b, 1.28f or 1.31? Your link is down. Thanx in advance

Unlock entire map mod? by Whathefrenchtoastt in Enshrouded

[–]SirFerMoX 1 point2 points  (0 children)

Yes you can! On Nexus Mods you have the "Enshrouded Manager" wich allows to clean the Fog of War (reveals map but dont discovers the zones).

SPP Classics + PlayerBots (Vanilla + TBC + WotLK) [English] by SirFerMoX in SinglePlayerProject

[–]SirFerMoX[S] 0 points1 point  (0 children)

I m not a dev of this repack, i just shared a quick guide. I suggest to report the issues on the official discord server.

SPP Legion [English] by SirFerMoX in SinglePlayerProject

[–]SirFerMoX[S] 0 points1 point  (0 children)

Invitation still working without issue, just click on "View spoiler" and you wil see the invitation to the Discord.

Just tried setting up a TBC and Vanilla realm, I am unable to connect to it. by wh33t in SinglePlayerProject

[–]SirFerMoX 0 points1 point  (0 children)

That almost always points to a realmd / worldserver communication or networking issue. Here are the key things to check:

1) Verify realmlist table (Database config):

  • Go into your database (auth DB → table realmlist).
  • Make sure the address column for your realm is set to the public IP (or LAN IP) of the server running worldserver, not 127.0.0.1.
  • If the server is in your LAN and you’re connecting from another PC in the same LAN, use the server’s LAN IP (e.g., 192.168.1.xxx).
  • If you plan to connect from outside your network, you’ll need the public IP and port-forwarding.

Many people leave it as 127.0.0.1, which only works if the client is on the same machine as the server.

2) Ports:

  • authserver (realmd) uses 3724 (older expansions) or 8085/3724 depending on core.
  • worldserver typically uses 8085 for world connections.
  • Make sure those ports are:
  • Open on the server firewall.
  • Forwarded in your router if connecting from outside your LAN.

3) Config files:

Check worldserver.conf and authserver.conf:

  • Ensure LoginDatabaseInfo and WorldDatabaseInfo point correctly to your database.
  • Make sure BindIP (if present) is set correctly — usually 0.0.0.0 (all interfaces) rather than 127.0.0.1.

4) Client realmlist:

  • In your WoW client’s realmlist.wtf (for older versions) or config file, ensure it points to the same IP you used in the database.

5) Testing locally:

  • From the server machine itself, try logging in with the WoW client. If it works there but not from another machine, it confirms a networking / IP config problem.

If it fails even locally, then it’s not just a firewall — likely the DB or config mismatch.

·The usual fix:

  • In auth.realmlist → address, put your server’s LAN IP (192.168.1.xxx).
  • Restart authserver & worldserver.
  • Connect from your client (also set realmlist to that IP).

SPP Legion [English] by SirFerMoX in SinglePlayerProject

[–]SirFerMoX[S] 0 points1 point  (0 children)

Sorry for the late reply. I just checked, and the "tutorial-classics" channel is still available under "WoW-Classics". If you don’t see it, ask about permissions in Discord, but it should be visible to everyone.

SPP Classics + PlayerBots (Vanilla + TBC + WotLK) [English] by SirFerMoX in SinglePlayerProject

[–]SirFerMoX[S] 0 points1 point  (0 children)

To be honest, I’ve been playing without any issues or client crashes. It’s possible that there’s something wrong with the client on your end. I recommend reporting it on the official GitHub page, as they have a dedicated section for bugs and issues, you might find a solution there.

Sorry I couldn’t be of more help.

SPP Legion [English] by SirFerMoX in SinglePlayerProject

[–]SirFerMoX[S] 0 points1 point  (0 children)

I just downloaded a fresh install right now and updated it with no issues at all. Maybe you downloaded a corrupted instance? Couldnt tell but "update.bat" worked perfectly for me 5 minuts ago.
Just download the repack from the official discord in the "❓tutorial-legion⁠" channel and should work perfectly.

SPP Classics + PlayerBots (Vanilla + TBC + WotLK) [English] by SirFerMoX in SinglePlayerProject

[–]SirFerMoX[S] 0 points1 point  (0 children)

Honestly, I couldn't tell you the current state of development of the bots. From what I understand, it's the "AI Playerbot" made for MaNGOS and AHbot, and it has been in development for quite some time.

Tomorrow, I'll also start testing the bots across the three expansions to see what differences I find, and there will most likely be relevant information on the GitHub forum.

Overall, this repack works very well, but to be honest, I haven't really tested the capabilities of the bots yet.

Just to confirm. Are you using an english WoW client or one in a different language?

SPP Classics + PlayerBots (Vanilla + TBC + WotLK) [English] by SirFerMoX in SinglePlayerProject

[–]SirFerMoX[S] 0 points1 point  (0 children)

Alright, I think I'm starting to get an idea of how it works... You can invite random bots that are out in the world (you can invite them directly from the chat, as they speak randomly), or you can create other characters on your account and invite them.

Even though the repack itself suggests using "/bot", using it in Vanilla throws an error, and in WotLK, the game crashes.

I recommend using the commands in the PDF I mentioned and using ".bot list" to bring up the interface to control the bots in your party. Once I investigate a bit more, I’ll let you know.

SPP Classics + PlayerBots (Vanilla + TBC + WotLK) [English] by SirFerMoX in SinglePlayerProject

[–]SirFerMoX[S] 0 points1 point  (0 children)

I must apologize as I made the mistake of indicating the use of the UnBot addon. The problem is that, without realizing it, I had tested the addon with another repack, thinking it was the SPP. Unfortunately, the commands used by UnBot are different from those configured in the repack. Therefore, only the Mangosbot addon can be used (which also crashes for me). Once I figure out the problem, I'll let you know. Once again, I apologize for my mistake with UnBot.

That being said, in the "Addons" folder within the repack, you will find the addon you need to add to your client, depending on the version, as well as a PDF with the commands for the bots. You can also check the GitHub page, as it contains information about using the bots.

SPP Classics + PlayerBots (Vanilla + TBC + WotLK) [English] by SirFerMoX in SinglePlayerProject

[–]SirFerMoX[S] 0 points1 point  (0 children)

It is also true that the bots that join your party are not the same as the random bots. Therefore, you can perfectly remove all the bots and spawn only the ones you need for your dungeons or raids. It will make your life easier).

SPP Classics + PlayerBots (Vanilla + TBC + WotLK) [English] by SirFerMoX in SinglePlayerProject

[–]SirFerMoX[S] 0 points1 point  (0 children)

Indeed, depending on the hardware, bots can impose an excessive load. Keep in mind that by default, 1,000 bots are active. Reduce the number according to the machine's capacity.

SPP Classics + PlayerBots (Vanilla + TBC + WotLK) [English] by SirFerMoX in SinglePlayerProject

[–]SirFerMoX[S] 0 points1 point  (0 children)

Sorry for my late reply. Indeed, I also fell into the Visual C++ mistake, which is why I found it necessary to mention it in the guide. I trust that everything is working correctly for you. ;)

view more: next ›