prmsye

Point taken, DaViper - I'll go with Trinity until the dust settles. Thanks for the input.

UnkleNuke, you are correct to an extent - as I said in n earlier post, I've been patiently waiting for Mangos developers to come up with a DK quest chain that works. Again, the client code has been essentially in place for the past 18 months, yet what progress I have tracked with Mangos code development has been lacking in dealing with a number of basic quest chains in WotLK, and the formative quest chain that one associates with WotLK is the one for the Death Knights. And the status of Eye of Acherus on a day-to-day basis reminds me of addons AHBot's and PlayerBot's on again/off again working status. After a while, one gets frustrated building/rebuilding and breaking/unbreaking (or the converse). Looking back at Mangos release 2.4.3.8606 Burning Crusade release, I rate this release (comparatively speaking) as "the gold standard" - this release allows one to essentially develop a character of any class, profession, etc without dead ends, with quest chains essentially pure, blizz-like and working. Also, seeing as this is a Mangos release (and I've screwed around with all the other crap releases of Ascent, ArcEmu, etc... and databases up the kazoo - none have the simple elegance nor the solid working state of the Mangos release in my estimation), I guess I'm a bit disappointed with the relatively slow rate of progress being made on the Mangos WotLK development effort. Obviously, it is a work in progress. Blizzard can testify to this as they roll out releases on an ongoing often basis. But come on, at least let's insure the DK quest chain works. And I don't think that Trinity release is necessarily a kluged patchwork of unstable code - I've experienced no crashes running the latest version for the past 4-5 days. But at the same time I'm not running it interactively with 100 other players from a dedicated server. As said earlier, plain and simple, I'm a user, and the way I measure quality is in what appears to work with functionality that poses a challenge. And "work" means that I'm not constantly having to restart an application that crashes, or rebooting due to a BSOD. So maybe Eye of Acherus has the hooks in place, but why in blazes does it not work most of the time?

Since I've never subscribed to Blizzard I can't say for certain that Trinity's Eye of Acherus is truly blizzlike. However, the versions I have been able to run in Mangos (when this quest works, that is, which for me has been probably one in ten compiles and database builds) run pretty much the same way the Trinity version runs. Also, emphatically I will state that no Mangos version I have ever built has run as many quests in the DK chain as Trinity's current version, and the quests in the Trinity build appear to me to be challenging and interesting - there are no "copout" quests as I've found in other databases, none of which I've ever been able to complete anyway, because they were still broken at some quest before the end quest allowing the DK (non-GM) to transition from Scarlet Enclave to another continent to continue his/her battle. Bottom line - I don't care whether Trinity's Eye is truly blizzlike or not. I enjoyed working through this quest, and for me at least this is all that counts. Enjoyment factor along with a reasonable challenge is all I want from WOW. Thanks for listening.

Thanks to Vladex, I assembled/built Trinity database with all updates to present and found Eye of Acherus operational - haven't proceeded beyond this quest yet, but this seems to be the main obstacle in the DK chain (though as previously mentioned never have been able to complete the chain as sooner or later encounter a broken quest).

I have a few questions about this, and a few negative comments stemming from the frustration that I've experienced over the past year and a half relating to this quest and other related DK quests. Is there a patch that works with the latest mangos compile, using database YTDB? I've only seen patches that (when they reference any database) state compatibility with UDB. And these don't work for me most of the time. Additionally, these patches clearly do not work with YTDB. So far, I've never been able to advance a DK through the quest chain originating in Ebon Hold, even when Acherus works - there's always been some quest that doesn't work. I've tried databases Silvermoon, UDB, and YTDB, and none of these has ever completely worked (along with either mangos or arcemu). Many of the patches, when they "work", actually just bypass problem quests, so any "Blizzard" feel to advancing through the DK quest chain is really in my estimation a big negative. It's been about 18 months since WOTLK initial release. What's the problem? Is the code just too difficult to emulate? Thanks for listening (and sorry for the gripes - if I had C++ coding experience, I'd be using more than my mouth to address this).

First off, I've been following this mish-mash for some time, and have to agree that this addon should not be left in the hands of patch jockeys - it is in my opinion of enough value to merit core integration for once and for all. I like the idea of using an internal NPC as owner of auction items. It helps to eliminate many startup problems potential users have. Also, for those purists who don't wish to use AHBOT, by retaining relevant options in the mangos.cfg file there should be no complaints. Of all addons currently available AHBOT definitely has the most appeal and value, especially to players in single or small group configurations. So, in this spirit I pose a few questions: - is Vladimir (or other "core gurus") still interested in integrating AHBOT into the core? - if so, is there anything the rest of us do to prepare the addon for core integration? Note that I would be willing to help but am not a C++ person (hardware design background with lots of experience but essentially none in software coding).

Hello once again, I was finally able to rerun new AHBot patch successfully and it appears that the recent conflict with master has been fixed.

Hello, I'm having problems incorporating the latest AHBot change into my existing 322A master version with working AHbot (from previous patch install). Since I already have your previous patch installed, the scripts listed at the beginning of this post do not work - and I would like to be able to include the latest AHBot so I can continue to merge in new 322A master changes as they are released. I am NOT a git expert, nor skilled at C++, so please try to exercise some care in explaining what steps I need to go thru to add this patch mod. Thank you for for your time and patience. This is the superlative website for WOW server development (IMHO)!!

Thanks ROL1983 for your fix - I had to search around for a few hours before finding it in this fantastic forum. It amazes me that this bug's been around since Microsoft released their SDK 3.5 SP1 pack back in April (and I've definitely updated all changes made since then to 8/22/09), and as you may be aware there have been a number of other folks on this forum that reported having the same problem. Anyway, thanks again!!