Jump to content

rultin

Members
  • Posts

    20
  • Joined

  • Last visited

    Never
  • Donations

    0.00 GBP 

rultin's Achievements

Member

Member (2/3)

0

Reputation

  1. Ok...I just tested something...Admin account was set to level 3. Ra.MinLevel was set to level 3...and I would get the errors I mentioned. Changing the Account to a value HIGHER than 3 and now the functions work. So for whatever reason the Ra.MinLevel has to be exceeded by the account logging into Moble Mangos. Not that I care having my GM account set to 4 or 5...but it would be nice if I set something to a certain level and Moble Mangos recognized it as being that level.
  2. Hmmmm...The account I log into Moble Mangos with IS set to level 3. And I get those errors on my phone. The account I logged into the game was a player account. So it's still not working as it should.
  3. Currently there are no players online. So 'account onlinelist' doesn't report anything while working with the Server Console directly. I logged in one of my test characters and get this ======================================================================================== | ID | Account | Character | IP | GM | Expansion | ======================================================================================== | 2 | RULTIN| Saltychicken | 192.168.0.2 | 0 | 2 | ======================================================================================== If I then go onto my phone and select Online Players in Moble Mangos I get this Account Name: the Online Players Name: access IP address: level ________________________________ Account Name: Command Online Players Name: account IP address: have and then at the bottom of the screen I get that java.lang message.
  4. 10654 - the only modification is the auctionhouse bot...everything else is stock I get Error: java.lang.ArrayIndexOutOfBoundsException
  5. Is there any reason why it doesn't display the online players for me?? Everything else seems to work...except for the Message Player and Online Players.
  6. I am using your current Repo...and AHBuyer is not working. Settings are correct in Database and it is enabled. AuctionHouseBot.Seller.Enabled = 1 AuctionHouseBot.Buyer.Enabled = 1 AuctionHouseBot.Account = 1 AuctionHouseBot.Character = 1530 AuctionHouseBot.Items.Vendor = 0 AuctionHouseBot.Items.Loot = 1 AuctionHouseBot.Items.Misc = 1 AuctionHouseBot.Bind.No = 1 AuctionHouseBot.Bind.Pickup = 1 AuctionHouseBot.Bind.Equip = 1 AuctionHouseBot.Bind.Use = 1 AuctionHouseBot.Bind.Quest = 1 AuctionHouseBot.ItemsPerCycle = 500 AuctionHouseBot.BuyPrice.Seller = 1 AuctionHouseBot.BuyPrice.Buyer = 0
  7. Just me or is the AH Buyer not buying for everyone else?? I've yet to get this to function despite everything that's been going on with AHBot lately...I've pulled a clean Mangos and followed the instructions in this thread...and yet the AH Buyer won't give up the gold!
  8. Awesome...this will help immensely...thanks for doing this!
  9. It would be really nice if your patch file was generic instead of needing specific folder structures. I try your method and Tortoise just complains about the directory. Even when I create a folder structure to match yours...it still doesn't see what it needs to see.
  10. It's not necessary to make it compile with each new commit of Mangos...Are most of us running a new compile every single day? Impossible to get any real testing done if that's the case. Anyways...A weekly update wouldn't be bad...just need something more standard and consistent because this current method of getting it updated is driving me crazy.
  11. This thread is getting way out of control and is getting confusing to follow with multiple people posting patches and telling everyone different ways to apply patches or merge branches... Could we maybe get this thread locked? Have a new thread created by someone who is going to watch and maintain this Core Mod? Provide a rewritten first post with instructions on how to get this code and apply it to Mangos git clone? Perhaps just git pull to merge? (I may be wrong but a simple git clone of mangos followed by a git pull from an AHBot source should be all that's necessary)...Something more clear and concise than what is currently going on. Every day I check this thread there is yet another person providing a different patch and some other way to apply it. Perhaps I'm out of line...but it seems whenever the current "guardian" of AHBot steps away for awhile we've gotten a new thread so that the new person can keep the first thread updated with relevant information.
  12. It should be noted that the Mangos Config file items for AHBot were changed. Everything compiled fine for me...and AHBot started during the Mangos start up. Yet I still had nothing in the AH...so I went and looked at the config file... Just thought I would mention in case some people didn't catch that. The post by vladex is why I though people may need to look into this as a possible reason AHBot is not working despite compiling fine.
  13. Not sure how...but running Trinity with a 2.4.3 client...If horde and alliance are in the same party (allowed by setting the config option)...they can trade with each other (allowed by setting the config option)...Yet when they are not partied it does not let them trade. So the Server must in fact have the ability to override the DBC files. I believe some DBC files simply provide labels or data for whatever is told to the client by the server. They are not necessarily points of data that the client is ONLY allowed to use. If Horde and Alliance was hard coded...then you couldn't set the flag and let them party together.
  14. So because I DO READ the announcements and it was CLEARLY stated in theLuda's post that GIT would be mirrored to SVN and the link in THAT announcement still shows Revision 6767... Come on...you close my topic because the Dev's have failed to come through on something they said would happen??? What gives...perhaps we are now seeing CLEARLY why there has been problems of late with the dev teams. Why the desire to quell and shut people up when they are trying to get some anwers. Quote from Announcements "Greetings, in the light of MaNGOS development switching to Git for version control, many community members have told us that using Git would not be userfriendly or lack system integration under Windows (as there is nothing like TortoiseSVN for Git). In the last few days I have been writing a script that will automatically import all Git commits into the Sourcefourge SVN repository. I am currently testing this with a mirror of the Git repository and a mirror of the SVN repository. Within the next week you can expect so see this going online within the next few days if no major issues show up. Update The Git repository will be mirrored to the old SourceForge.net SVN living on http://mangos.svn.sourceforge.net/svnroot/mangos/. Commits will only go into the trunk/ and only from the master branch on GitHub. Thus development branches on GitHub will not be available on SVN. The mirror will be updated once a day ~ 21:00h CET. " this was posted by TheLuda... If this information has changed then THIS first post should have been updated with the appropriate information. Instead some moderator links to a completely different SVN and tells me that I should have read the announcements. What is wrong with you people. Try being helpful and don't CLOSE every topic because you are afraid to give us some answers. As for using GIT...I will be using GIT...I will learn it at a time of my choosing. When it actually functions with simplicity with an integrated GUI...but as it was designed for Linux users who believe the command prompt reigns supreme this will probably not happen. So in reality the choices of the Mangos Dev have caused the division amongst the community. I can see clearly now the rain is gone. Must make people feel uber that they can close topics and post responses that don't provide any explainations. Seriously...get over yourselves.
  15. What's the deal here? We were told that it would be mirrored for awhile and the SVN is STILL at 6767...so much for keeping their word.
×
×
  • 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