Search results

Can you tell me when this exactly happens and does it change when you enable some plugins or change a profile? Do you have logs when this happens ?

I am using Arelog without any problems

AntiIdle Update! v1.3.4 Changed: Improved unstucking a bit to try using db navigator first Changed: Improved diablo crash/close detection Bugfix: Should no longer click the start/resume button when it should not to (this fixes the incompatability with radonic profiles + ciggarc plugin)...

did you enable the Auto relog future in config window ?

true this is due to Demonbuddy not compiling + initiating plugins before D3 login .. :( hope this will be fixed soon

Are you sure this is caused by the AntiIdle plugin ? Try using AntiIdle v1.3.2

Update v1.3.2 Added: Costumizable unresponsive timer under settings -> Other stuff (Requested) Changed: Diablo unresponsive timer from 10 to 30 seconds Bugfix: Anti-Ganker settings are now working correctly Some code clean up

You are right I will add this when I get home again..

Lovely :) gj Giles

hmm it does not really start from bottom of the list that is shown ingame ... my list looks like this: Hero1 - HC Hero2 - Normal Hero3 - Normal Hero4 - HC ----------- using a plugin to get the Heroes would get Hero3, Hero2, Hero4, Hero1

Tested this at char selection screen but it does not give the right information... Logging.Write("Num Heroes: " + ZetaDia.Service.GameAccount.NumHeroes); Logger.Write("Max slots: " + ZetaDia.Service.GameAccount.MaxHeroSlots); Logger.Write("Empty slots: " +...

that would be true indeed but this is more a quick fix for it I think DB should handle it :)

It is a plugin should be saved as .cs in the plugin folder in its own subfolder C:/demonbuddy/plugins/startstop/startstop.cs

FileVersionInfo.FileVersion Property (System.Diagnostics) this will work for sure .. so it could look like this: System.Diagnostics.FileVersionInfo myFileVersionInfo = System.Diagnostics.FileVersionInfo.GetVersionInfo(Assembly.GetEntryAssembly().Location)...

Assembly.GetEntryAssembly().GetName().Version mayb this because you call it from a plugin

Demonbuddy.App.ResourceAssembly.GetName().Version or if that is not working mayb this System.Reflection.Assembly.GetExecutingAssembly().GetName().Version .. did not test both myself

there already is a plugin for this AntiGanker ... and AntiIdle could do this also.. http://www.thebuddyforum.com/demonbuddy-forum/plugins/55038-plugin-puffos-anti-ganger.html

So AntiIdle does its job there :) Gl in finding the problem ..

Ok I changed it a bit so it should not be spammy anymore... :) I tested it when I was in one of the crypts with a really simple profile and that seemed to be working

you sure diablo 3 is not frozen when this happens? cause the error message say so... and does this also happen when you just disable AntiIdle? Because it does not look like an issue with my plugin