Jump to content

HSC_Dev3

Members
  • Posts

    86
  • Joined

  • Last visited

    Never
  • Donations

    0.00 GBP 

Posts posted by HSC_Dev3

  1. phpBB-Registration-Bridge.png

    Where do I download the bridge ?

    The file can be found here

    Okay I've got the file, now what's next ?

    * Extract the contents into phpbb_root/includes/auth/

    * Edit the line that says

    $conn = new mysqli("host", "username", "password", "logondb");

    to your own details

    * Upload the new file if this was a local folder if not go to step 3

    * Go into your admin panel

    * Go to General->Client Communication->Authentication

    * From the topmost dropdown select Wow

    * Click submit

    * Go to Permissions->Group Permissions

    * Select the registered users group and click submit

    * Click on advanced permissions

    * Click on the profile tab

    * Set "Can change password" and "Can change email address"

    * Click apply all permissions

    * Login with any account that's in your MaNGOS database and it will be logged in and added to the forums.

    Features

    • * Checks for bans
      * Password changes on the wow server work on the forum
      * All phpBB features will work

    If you have any questions, remarks or comments, don't hesitate to reply to the thread.

    Verified and working with 3.0.6... I will soon be re-releasing a version of Bruno's Minimanager with integrated phpbb3 and centralized config.. just want to work on making the minimanager skin look more like a CMS first.

  2. hey all.. I am looking for a login bridge that works preferrably for a free forum software like phpbb or smf... or even better some form of portal that connects all three.. ofc it needs to support 333a not 332

    if anyone has any clues let me know, i have searched the site and i have spent countless hours scouring the net.. the only thing i have found so far is mangoswebenhanced and it doesnt support 333a. (also the forum software included with it is so basic its retarded..

  3. I have one, however you will more than likely want to edit the displays since i changed all the output code to reflect our server name rather than the standards (such as MangChat has started >> DarkIce Chat has started) will push a patch on pastebin shortly

  4. just wanted to report i have playerbot working better than ever with ahbot, vehicle, anticheat, and dozens of other modifications compiled under visual studio 2008 and 2010 without making any changes to the playerbot system personally as of rev 10049! excellent work as always blue!

  5. they want it stable for the core, they did the same thing to dual-spec when it was implemented.

    i dont personally find this to be a valid excuse ... if you keep changing the core's fundamental properties every time the mdoficiation *IS* stable to a given core so that the modification is no longer stable, then it isnt the mod thats unstable its the core's changes.

    for instance, I have the last revision of vehicles running without any errors that were not present in the modification the last time it was updated (around 10019 i believe) my core is now 10049 btw.. however when building my core i intentionally skipped over 10030 because at that commit mangos decided they would change the m_target/Spellproto system radically causing vehicles to no longer function. If you look at the commit comments you will see that this change was intentional for a security reason, the old method was actually easier to debug which vlad openly agreed with, but it was said that they did so because they felt that in the future it could lead to better security.. THATS ALL. Personally, call me a conspiracy theorist if you like but I think that it was a direct attempt to thwart other modifications from working with the core and nothing else, but thats me.

    the point is... the modification will never be stable with mangos if mangos intentionally changes the properties of the core to disrupt the modification, and thus they will always have the excuse not to implement it. If they implemented it @ a time in which its functionality matched the core at the same revision then THEY would be undeniably responsible for the errors generated when they changed the core's properties to break the mod and they would in turn fix the problem themselves internally. One might argue that vehicles isnt 100% complete so they refuse to implement it until it is.. if that were the case however then mangos wouldnt produce commits at all since it is not 100% compatible with the current revision of the game itself.

  6. error LNK2019: unresolved external symbol "public: void __thiscall Vehicle::Dismiss(void)" (?Dismiss@Vehicle@@QAEXXZ) referenced in function "public: void __thiscall boss_malygosAI::DespawnCreatures(unsigned int,float,bool)" (?DespawnCreatures@boss_malygosAI@@QAEXIM_N@Z)

    what's the problem vehicle patch?

    no its a bad call in the scriptdev2... thats why we have that section disabled (commented out) in the darkice/darkrulerz scriptdev system

  7. lol we're all impatient, but it will be ready whenever he figures it out... i have tried to tackle it several times myself but it just wont go for me (even considered commenting it out but that would kill trading among the bots.. sigh

    anyway... I am sure that when he does get it it will work just as great as his repo has shown to do since he picked it up...

  8. no i suppose not viper... its just very irksome when you make an earnest comment and some nitwit tries to downplay said comment by quoting something out of context to look like the last hundred nitwits like him/her who have done it before...

  9. thank you very much traponinet I will see if that will work.... currently have taken a different tack altogether

    Curious... playerbot isnt offilike in that you cannot have bots.. true.. what you seem to be missing here is that I only suggested that vehicles had its own forum section LIKE they are doing now for playerbot. They are doing it to avoid a post with 50+ responses that people have to weed through in order to get answers. So yes, I *do* think that vehicles should have its own subforum somewhere, where it can be discussed and developed in a more rational enviroment. THUS, no, I wasnt off topic at all.. my comment was about furthering the development of vehicles, THIS topic is about furthering the development of vehicles.. LEARN TO READ

  10. completely and utterly untrue .. i am ashamed of you viper.. HACKING by definition is to take a pre-existing system and modify it to suit one's own purposes (be those purposes negative or positive). Thus **NOT** all hacks are for breaking.

    insofar as prmsye, i have to solidly agree, mangos *has* been dragging thier heels when it comes to implementing WotlK especially in concerns to the death knight. They can claim this or that being the reason, I disagree... ok lets put it out there.. they say that the "hacks" are bad code, are they? ok.. so then that would say they know how to do it RIGHT wouldnt it? i mean, if the hacks are WRONG, then the only way to prove that is to show that he work right?

    you made excellent points about 2.43 as well..

    personally I do not see trinity as being the answer... they have too many devs in control of everything which leads to one dev overwriting another devs fixes consistantly.. thats why you can commonly find spirithealers getting a tan in durotar and other flaws that change on a day to day basis there.. Mangos is the best, i wont take that away from them... but the excuses they make for taking so long to produce anything viable for wotlk are just that..excuses

  11. you are obviously better at voicing your mind than reading..

    read eevrything i wrote before saying "wrong topic" I merely referred to what is being done for the playerbot modification should be done for the vehicles modification.. that is a forum devoted to it.. READ before you POST

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy Terms of Use