-
Posts
181 -
Joined
-
Last visited
-
Days Won
3 -
Donations
50.00 GBP
Content Type
Profiles
Bug Tracker
Wiki
Release Notes
Forums
Downloads
Blogs
Events
Bug Comments posted by Meltie
-
-
@D Q There are two authors to this commit, Fyre and I. Just never got around to fixing the issue yet and just being busy outside of the project.
Feel free to make a PR with the fix and will get it pushed out.- 1
-
Confirmed on WoTLK (M2).
* Need to check if the issue exists on Vanilla (M0) and TBC (M1).
Working as intended on Cataclysm (M3) from the initial PR from Vanilla (M0).
From thinking on this, another issue could be at play here outside of the line of code reported in the post above. -
Changed Status to Comfirmed
Changed Implemented Version to 22.xx (Current Master Branch)
Changed Milestone to Unset
Changed Priority to New
-
This bug does not exist in M3 (Cataclysm). Appears to exist only in M0 (Vanilla).
-
Changed Status to Confirmed
Changed Implemented Version to Unset
Changed Milestone to Unset
Changed Priority to Normal
Changed Sub-Category to Minor
-
Changed Status to Completed
Changed Implemented Version to 22.xx (Current Master Branch)
Changed Milestone to Unset
Changed Priority to New
-
Changed Status to Confirmed
Changed Implemented Version to Unset
Changed Milestone to Unset
Changed Priority to Urgent
-
Changed Status to Confirmed
Changed Implemented Version to 22.xx (Current Master Branch)
Changed Milestone to Unset
Changed Priority to High
-
Changed Status to Completed
Changed Implemented Version to Unset
-
Changed Status to Completed
-
Changed Status to Completed
Changed Implemented Version to Unset
Changed Milestone to Unset
Changed Priority to New
Changed Sub-Category to Show Stopper
-
Changed Status to Completed
-
Awesome work! Did some research on the tracker and found similar issues with this. Hopefully this gets merged soon.
-
Changed Status to Duplicate
-
Changed Status to Confirmed
Changed Implemented Version to Unset
Changed Milestone to Unset
Changed Priority to Normal
Changed Main Category to Realm Daemon
-
How to reproduce this issue as shown above on any client locale. Not restricted to French Locale.
- Set your RealmZone other then 0.
- Start your Realm Daemon.
- Login to any account and view the RealmList window. (If you only have one realm, nothing will appear)
-
This looks like the issues I temp fixed some months ago, which wasn't fully fixed. The use of .server shutdown 0 or .server restart 0. This is from the server unable to use the call function from 0. As I recall, I believe this is on all cores.
Tips: Try using a high number then 0 -
Arcemu has something like this already. I recommend you looking on Arcemu side for it.
-
[quote=Talendrys]Hi Titan, can you try this bug fix and provides feedback ? :-)
[url]https://github.com/Warkdev/server/commit/69982e8767d9f65d60e0bc8a2b85cb48f21a8ae3[/url]
Thanks.[/quote]
Talendrys, this posted fix, is hacky.. Shouldn't call exposed data like that.. Plus is fix was taken from Silverpine Project, which no credits were given. -
This is included by default. I can use SOAP in Zero just fine on Unix. Reason of the message, because it's most likely not turned on via config file.
-
Looks like a tags are changed around.
-
This is a minor issue.. I'll look into this when I get that chance.. From map updates before Rel19, could have broken the system for LoS and Movement. This is confirmed on both windows and unix systems, where the reading of the tiles are not fully loaded during start-up. As of right now, its [u]not a required function[/u].
-
Make sure all the database queries are correct and matching what the core has.. This is the first step you should always do..
Second, is all the opcodes correct? Sometimes, this makes the client none talk-able to the server. Many things can make the bank not work. -
This is an confirmed bug in the Rel19. Still looking for a proper fix for it.
All spells buyable from class trainer
-
-
-
-
-
in Tasks (Two)
Posted
@D Q I have pushed a PR out on the original repository where the fix was initial committed too.