madmax

Confirmed as still an issue.

[IMG]https://www.getmangos.eu/attachment.php?attachmentid=305[/IMG]

Fixed by commit - [url]https://github.com/mangosone/server/commit/231128df3519fe53d68ac14aca7e38798894c863[/url]

@antz any update on this?

Reopening as its not clear in the messages if this issue is fixed or not. Will need someone to confirm.

Issue marked as completed and closed.

Merged and closed.

Should check skype chat! there was a message about the wrong eluna sub-module connected, it should be ok now.

Ok, This is working as intended on the test server.

Just make sure you don't start this quest via gm command else he wont attack you.

[quote=antz]Did you try this after reloading the database with the scripting table fix ?[/quote]

Same result with the sql applied. This is a script issue.

Managed to get this working under a GM character (With GM mode set off). I did ".damage 1" to get the NPCs attention.

When the quest is grabbed he is supposed to flag red and attack whoever took it, this does not happen.

During testing on covenant-wow.com the NPC remained green after grabbing the quest and does not attack.

Has to be windows.

[quote=Chucksta]
the damn Gremlins that haunt my PC are the issue :mad: bad, bad gremlins![/quote]
[IMG]https://sciencegremlin.files.wordpress.com/2013/08/spongebob-wikia_gremlin.jpg[/IMG]

This has been confirmed by myself and antz. [U]In future please don't change my issue status[/U], if I set it to confirmed it is confirmed for a reason, in this case has been seen and commented on by users in the dev channel of skype.

Made some progress and got some source code to come up for the crash from ace.

Just putting this link here for antz - [url]http://stackoverflow.com/questions/1702172/terminating-a-thread-gracefully-not-using-terminatethread[/url]

Closing with Ctrl+c gives this error:
[IMG]https://www.getmangos.eu/attachment.php?attachmentid=180[/IMG]


From visual studio output:
[QUOTE]The thread 0x10e4 has exited with code 0 (0x0).
The thread 0x1040 has exited with code 0 (0x0).
First-chance exception at 0x74F422CB (KernelBase.dll) in mangosd.exe: 0x40010005: Control-C.
[/QUOTE]

Fixed in commit - [url]https://github.com/mangos/realmd/commit/15df5d42ae03cabe9cebfbd7534df8af4f739ecb[/url]

Commit that removed this function found by antz: [url]https://github.com/mangos/realmd/commit/548d6fca80a3fe3e276cf4e7d240eeb8fb99c6d6[/url]

[url]https://github.com/mangos/realmd/commits?author=lfxgroove[/url]

Exact commit: [url]https://github.com/mangos/realmd/commit/3938060ca040a12a5acd6736b913b2552f3754f6[/url]

Presuming this commit is still in there? Must need fixing/reviewing.

[quote=Xenithar]This is not the case for me. Is this just a Windows thing?[/quote]

Must be.

[quote=antz]I believe this command should use the value from
MaxPlayerLevel in mangos.conf

But should gm's be allowed to skip past this check ?[/quote]

Maybe have an additional setting in the conf to allow GMs to bypass max level check?

If they try adding levels above the max level and the check says they have to abide by it then only level to the max allowed. If on the other hand they can bypass it then allow it to level up to 255? (Which i think is a client limit?)

[quote=antz]@Madmax - Xen is right, move to dropdown is blank[/quote]
Not implemented by the creator yet. Issues can be moved by admins just let me or antz know.

#admin note: issue moved from database to server.

Would you mind looking into this on Zero and if possible One as well?

If we can figure that out it will make migrations script between the cores much easier.

- removed by admin -

Hm is the realmid correct in the mangosd.conf and is the correct version number being shown in the realms table for that realm?