Xenithar

Currently I know all Horde leaders are two-shot kills with a rogue. Have not checked Alliance leaders.

Fresh clone and build from scratch today. Here you go. [code] mangos>server shutdown 10 CLI command under processing... Table `command` overwrite for command 'honor show' default security (2) by 1 Table `command` overwrite for command 'modify honor' default security (1) by 2 Server is shutting down in 10 Second(s). Command: server shutdown 10 [Account: 0 from Console] mangos>[Thread 0xb18f2b70 (LWP 10992) exited] Network Thread Exitting Network Thread Exitting [Thread 0xb08f0b70 (LWP 10994) exited] [Thread 0xb10f1b70 (LWP 10993) exited] [Thread 0xb20f3b70 (LWP 10991) exited] Program received signal SIGSEGV, Segmentation fault. 0x08551fa3 in Eluna::OnShutdown (this=0x0) at /home/---/zero/src/server/src/game/LuaEngine/HookMgr.cpp:367 367 EVENT_BEGIN(ServerEventBindings, WORLD_EVENT_ON_SHUTDOWN, return); (gdb) backtrace #0 0x08551fa3 in Eluna::OnShutdown (this=0x0) at /home/---/zero/src/server/src/game/LuaEngine/HookMgr.cpp:367 #1 0x08547b16 in Master::Run (this=0x8c9a7d0) at /home/---/zero/src/server/src/mangosd/Master.cpp:352 #2 0x08547204 in main (argc=1, argv=0xbffff314) at /home/---/zero/src/server/src/mangosd/Main.cpp:214 [/code] Still happens under 32bit Linux. Have not tested on 64bit Linux.

I did not realzie this was a spell. When testing the beta I assumed this was all server-side. Would be great to have it just to mess with my fiance though!

Yes, sorry. I can reproduce it by starting my server, idling for five minutes, then doing "server shutdown 10". Ten seconds later it begins to go down and crashes.

I never run ANY server process on Windows. I do have a 2008 R2 license somewhere, but I'd need hardware to plop it onto. so yes, this is Linux, but I cannot test Windows.

Your router does not even come into the picture if you're playing on the PC your server is on. Try disabling the Windows Firewall and trying again. If this fixes it, I would actually recommend you turn it back on, go to "Allow a program or feature through firewall", click "Add Program...", select magosd.exe, and do the same for realmd.exe! That should fix it permanently and leave you safe.

I wanted to update this issue. Eluna caused a new crash just now during shutdown. [code] Program received signal SIGSEGV, Segmentation fault. 0x08551fa3 in Eluna::OnShutdown (this=0x0) at /home/---/zero/src/server/src/game/LuaEngine/HookMgr.cpp:367 367 EVENT_BEGIN(ServerEventBindings, WORLD_EVENT_ON_SHUTDOWN, return); (gdb) backtrace #0 0x08551fa3 in Eluna::OnShutdown (this=0x0) at /home/---/zero/src/server/src/game/LuaEngine/HookMgr.cpp:367 #1 0x08547b16 in Master::Run (this=0x8c9a7d0) at /home/---/zero/src/server/src/mangosd/Master.cpp:352 #2 0x08547204 in main (argc=1, argv=0xbffff314) at /home/---/zero/src/server/src/mangosd/Main.cpp:214 [/code] The code at #0 is the crash.

Thanks, Foereaper and Talendrys! Maybe we should close this bug now?

I do remember having this issue early this year. The problem was a firewall. My DNS server (yes, I run servers in my home for those who do not know me) was down for an upgrade from Debian 6 to Debian 7 so I was using my ISP DNS servers. Due to this, when I attempted to access my Zero server, my external hostname resolved to my router IP address. Normally it would resolve to my internal address. What this means is that my client went out of my router, to my ISP, back to my router, and died because I did not have port 8085 allowed through my router and forwarded to the server. I basically sat at the character screen for ages. Again, if you run your server on your game system (the same system you play on), try disabling any firewalls you may have and try again. If you have a separate system hosting your server, how about telling us the specs of your server, such as OS, network IP and subnet, and any firewall software you're running. It would also help to show us how your realm database is configured.

The "Invalid creature" bug means to [b]clean your cache[/b]. The inability to call them was due to a bug that Talendrys already fixed. I do not know if this fix is in the R20 branch yet.

You work fast, I admire that. I just now got to sit down and check the forum/tracker. I kind of miss the days of working at a retail store and having loads of time off, but I couldn't afford a $42,000 vehicle back then! Thanks for your hard work!

Heh, my fiance forgot to wipe the WDB folder after I went from R17 to R19. She couldn't tame ANYTHING. I chuckled and eventually laughed. She was not amused. I cleared the folder and she gave me the stink-eye because she KNEW she was told to do it. Thanks for the fix. I will be doing a fresh clone and build tonight. Does this also fix the voidwalkers and other warlock pets not having names?

So you can loot the same chest with two players at the same time? Are the contents of the chest the same for both players? This sounds like something I should play with this weekend when I have some time!

Don't sweat it. I can check the forum and tracker easily, but my job takes full days from me. I literally go in around 0800 and work some days until 2200. That is why this is a hobby for me. It keeps me from stressing over it.

You're right, and that is what I instill in my employees. Do it right the first time. And yes, I am fortunate. I have three 98SE systems (all matched hardware), five XP systems (matched), and two Windows 7 Pro systems (again, matched) in my lab. You can play any game from DOS games to modern ones at my place. It was my dream to have this setup when I got a well-paying job, and I have it. Now for more servers! Now, on to the important things. When you say they're not Blizzlike, does that mean you're having the issue I am experiencing? Members get to roll on chest items?

I had this issue on Zero, One, and Two years ago. I mean before I ever even became a forum member. I am thinking 2007 or 2008. I left MaNGOS alone and updated a week or two later and it was fixed. Have not seen it since and I cannot reproduce it. I will attempt to create a One server later this week and see if I can reproduce the issue. It is not happening on my Two server or Zero server. Things to check: IP address in the realm DB, route to said address if it isn't on your local system, firewall (yes, it can block you even on the same system), and settings in your configuration files.

This also happens with the orc peons in "The Valley of Trials" in Durotar. Some will be asleep like they're supposed to be. Others will be awake but doing nothing. It as if something half-processed. Not sure what happens with these guys.

I imagine you do. I just assumed everybody is not an IT geek with an actual lab in his home to test things. I can multibox and control five characters at once if I want to, making things easy to test. I was curious as to whether there was a built-in way to do it. Kind of like spawning a bot to help you in UT or something. Let me know what your test results are though.

How will you validate it without a group? Is there a way we can test group things solo? I have never tried so forgive my ignorance.

Mind you, the case I was stating was tested in R19 and it happens every time. However, I have not allowed anybody on the R20 server due to bugs that worry me may cause hours of labor lost, such as the pets not spawning. I would HATE to have my mom lose her pet after hours and hours of raising it. Same for my fiance. Therefore, I have not tested this in R20. I am available to connect to another server and test with you if you need my assistance though.

It has been this way since before the split. In fact I remember doing this in 2008. How is setting a number to 255 going to cause a stability issue? The only thing I can see even remotely possible is that one aura from a talent tree may adversely affect an aura from another tree, but during the beta there was a week or two where they did just that: Grant everybody all talents. Also, this is something to be used by GM's. I had spoken with Luda or Salja about keeping the level data from WoTLK in Zero and One so the GM would be mega-buff when going above 60 and was told that it was a simple matter of bringing the level data from WoTLK into the databases for One and Zero. Never was it mentioned that this would be an issue. If it is an issue, you can tell it to my pally who has been 255 for eons and never brought down a server. If this is such an issue, I vote we put a setting in the configuration file that defaults to 60 but allows a GM to raise his/her level up to whatever the value is set to, or a max of 255. This way the server admin is in charge of how buff the GM's can be.

If group loot works, does setting the loot level for rolling work? In other words, if I set group loot and choose blue or better, will greens be rotated like whites as it should be, or will we still have to roll on greens? Also, does any of this fix the "never happened in a million years in official" issue where if I open a chest, the entire group must roll on items? Normally the group would do "/roll 100" and whomever had the highest roll got to open and loot the chest. However, in R19 (not sure about R20 yet) when I open a chest, my entire group gets to roll and win the items inside. Not Blizzlike at all.

That should be normal. After all, we only have stats data for 1-60 in Zero, and 1-70 in TBC, etc etc. I played as a lv255 paladin for a while messing with friends (Horde) while killing Cairne. He still kicked my bottom because I had level 60 stats, just a bunch of extra talents! The normal cap is 60 for players. GM's can go above and beyond, up to 255 which is the max for an unsigned char. Seems fine to me. Also, it does not crash anything.