[FREE] [Rep][Ach] TheBrodieman's Profile Compendium

I'm sorry it was in SMV. It was running the profile then stopped in one spot. I don't know how to get my current location. I switched to nagrand and its currently stuck there.

Now I remember how to get location. In Nagrand it's stuck at 2961.79, 4549.41, 162.51

Similar message, moving to hunting ground waypoint 2992.987, 4577.881, 193.1877

No viable mobs

 

HB -> Dev Tools, there are 2 buttons there that can generate the location. Local Player Info's refresh, and Generate Hotspot. You can grab it from that. But what I need is more a visible location of where you are. I can tell from the profile that you are in SMV, but rather than grab a test char and run to that location to test the mesh, I was hoping you could say where you are standing.

 

Updated my post. Currently I'm in nagrand.... I'm on my mount at the base of a hill. I can see the node on the other side of the hill on my mini map. I apologize, I hope my info helps.

The one in SMV I was on the water on my azure mount there were some of those purple fungus looking mobs. Sorry not a better description

 

Today im getting this Error when trying to get into the Plugin Menu

 

Hey Brodie,

Wondering if you can take another look at the farming of Direhorns on the Isle of Giants. The bot chooses to kill Dinomancers as a priority over killing the actual dinosaurs. Also, it chooses to kill the smaller ones over the larger Primal ones. There is a point where while looking for dinos, it does a circle on a piece of wood. I've also noticed that when the bot needs to sell/repair, it tries to swim across the ocean. That is prolly not a problems with your profile and prolly a problem with my bot setup. I know I should provide a log, but I'm not sure the first 2 issues really require it. Perhaps the 3rd issue, but that's prolly just my bot being messed up. If you need a log, I can post one. I know you're working on other things, so this is prolly lower priority, but it might be good for a little tweaking...

Thanks!

Dave

 

Hi Brodie,

First thanks for the pluggin it's really amazing.

I have the same problem as Tumbum this morning (it was working fine yesterday morning). Maybe you can help me with this.
I can't go in the TBMC menu.

Here is my log :

View attachment 17068 2015-03-09 05.37.txt

 

There was a change to the settings within the core of the plugin this update. Please delete "HB\Plugins\BrodiesPlugin" and restart hb.

 

there wasnt all garrison apex quests in your plugin, right?

 

Currently, Anzu and Iron Siegeworks are not supported. I have Anzu done but can't test it as some bugs in test release are making it behave poorly. Awaiting fixes before definitively releasing. missive support coming soon (2/12 done so far, easy addition just started late last night)

 

ever seen this issue? happened when i enabled the plugin.

[19:13:23.306 D] Plugin TheBrodieMan's Compendium threw an exception in 'OnButtonPress'! Exception:
[19:13:23.306 D] System.TypeInitializationException: The type initializer for 'BpGlobalSettings' threw an exception. ---> System.ArgumentException: The settings file does not match the type that is being loaded! Root name is "BPGlobalSettings", expected "BpGlobalSettings".
Parameter name: root
at Styx.Helpers.Settings.LoadFromXML(XElement root)
at Styx.Helpers.Settings.Load()
at Styx.Helpers.Settings..ctor(String settingsPath, String oldSettingsPath)
at BrodiesPlugin.BrodiesPluginUi.BpGlobalSettings..ctor()
at BrodiesPlugin.BrodiesPluginUi.BpGlobalSettings..cctor()
--- End of inner exception stack trace ---
at BrodiesPlugin.BrodiesPlugin.OnButtonPress()
at Styx.Plugins.PluginWrapper.OnButtonPress()

 

Please see:
https://www.thebuddyforum.com/thebu...ofile-compendium-post1886713.html#post1886713

 

thanks for being awesome! i had looked on the first page for the solution at first lol

 

hi,

when i click tbmc menu nothing happens. it used to work until today. this is not paid version maybe that's why?

 

Please see:
https://www.thebuddyforum.com/thebu...ofile-compendium-post1886713.html#post1886713

 

Menue Error (different than most?)

Hey Brodie,

Sorry I know you're being bombarded about this. Having the same issue with the menu not working. However I have the purchase made via BotHaven and have uninstalled everything and reinstalled honorbuddy, the bothaven manager and your plugin and am still getting the error. View attachment 8396 2015-03-09 16.46.txt

 

This is the same issue as I mentioned above. Make sure you delete the HB\Plugins\BrodiesPlugin folder (to delete the settings) before opening HB.

I do see however that you are running this from the BHM. I haven't tested it in a while, but the error is stemming from BHM's accessing file (the .cs in the BrodiesPlugin folder). I would uninstall from BHM first, then delete the folder, then reinstall from BHM.

 

Ive done that multiple times and its still not working. Could the bothaven manager settings or log saves be interfering?

 

The issue is that old settings files (from version 3.1.1.73 and older) are incompatible with the new version (name changes and code cleanup). Those settings need to be purged before the menu will open (its trying to access a name that doesn't exist, throwing an error).

 

Okay so just made a new folder. Extracted a fresh install of Honorbuddy, Extracted fresh BotHaven Manger into plugins then ran HB. From there was able to install a fresh install of your plugin (version ...1.74) , closed HB and reloaded it as propted by the fresh installation of TBPC, reloaded and boom no menu. Close HB --> delete brodies plugin log back in --> reinstall --> reload and boom still no menue. All of this was done in a brand new folder will all fresh installations of everything involved so that there could be no old settings.

Is anyone else with the BotHaven manager having issues?

View attachment 10400 2015-03-09 17.06.txt

Fresh log from fresh install.

And sorry for the hassle Brodie, you have the patience of a saint.

 

Could be that something didn't make it to BH that was supposed to. I'll need to resubmit tonight. Hold out for the evening and I'll get a fix out by end of day. Hopefully by tomorrow this issue will be corrected.