I'm glad people still use it, even if it's far from perfect As you said, it was kinda hard to synchronize the chars the way it was done. For the new version, I used services to make multiple HB instances able to communicate with each other, so instead of relying on timers and other chars position (which make it work 'randomly'), each char is actually notifying other HB instances (which are running the plugin) his current state (Like Questing, Waiting for other chars, Turned in and waiting for everyone before starting to quest again etc). Chars with also notify each other about which exact quest they are trying to turn in, this should reduce the numbers of "deadlocks", like when turning in a class/race specific quest that other chars don't have. They will also be able to tell if one of them for an uknown reason stopped, and they will all stop so the bugged char is not left behind.
Code: try { if(!Partied) { Logging.Write(Colors.Orange, "[RAF Questing] - You need to be in a party to run this plugin. Stopping bot."); TreeRoot.Stop(Name); } ShouldIWaitOrShouldIGo(); } catch (Exception ex) { Logging.WriteException(ex); } What exactly is the error you are catching here?
Well, this code was my first glance at HB plugin dev, so this catch was mostly here for me during testing, to catch whatever exception was thrown during the execution flow. Nice ninja edit tho ahah still saw what you writted and I agree As said earlier, don't even bother looking at this code, I'm rewriting a completely different plugin atm.
Hello. Just wanted to report the only problems I found and if changed would probably make it work really well. First off, for escort quest when one character starts it, the other character doesn't accept the quest and waits until npc respawns. Second, you would want the experience to be as close as possible to eachother and a script that walks to the other character when they are 100yards apart would be sweet. (had trouble one being a bit ahead and when lvled he went somewhere different and got ahead by alot(probably need to be aware of character trying to sell/mail/repair aswell)) and last which also ties in with my second point, it should check if the other character have already turned in the quest before it starts to wait for raf partner to be close. I'm not great with plugin coding and got no idea if these can be achieved , just wanted to let you know these were the only problems I ran in to at 1-90.
im getting this error on one of my accounts trying to run it Compiler Error: C:\Users\Josh\Documents\Honorbuddy\Plugins\RaFQuester\RaFQuester.cs(70,30) : error CS0115: 'Main.Initialize()': no suitable method found to override
Gnjax's RAF Questing\gnjax's RAF Questing.cs(16,22) : error CS0234: The type or namespace name 'Database' does not exist in the namespace 'Styx.CommonBot' (are you missing an assembly reference?) Dont work with HB3.
Compiler Error: E:\Honorbuddy\Plugins\Gnjax's RAF Questing\gnjax's RAF Questing.cs(16,22) : error CS0234: The type or namespace name 'Database' does not exist in the namespace 'Styx.CommonBot' (are you missing an assembly reference?) Compiler Error: E:\Honorbuddy\Plugins\MasterBaiter\MasterBaiter.cs(400,106) : error CS1503: Argument 4: cannot convert from 'out Styx.WoWPoint[]' to 'out System.Numerics.Vector3[]' Compiler Error: E:\Honorbuddy\Plugins\MasterBaiter\MasterBaiter.cs(402,108) : error CS1503: Argument 4: cannot convert from 'out Styx.WoWPoint[]' to 'out System.Numerics.Vector3[]' so its there ( my problem to login )