Search results

This does not support multiple CRs/plugins/botbases in the same DLL (Weischbier had a problem with this here: https://www.thebuddyforum.com/threads/multi-class-support-and-combatroutine-overrides.401924/). I suggest you change it to at least support the common case of multiple CRs, one per...

This wouldn't help. If the build is leaked then it can be *****ed and looked at early by *****ers. All I'm urging you to do is to spend a little more time when you open your issues -- attach logs, give us easy repro (for example profiles, step-by-step), etc. I just bluntly told you that...

All good points. Where did you hear this? That's much easier said than done. We don't have infrastructure to support this. Sorry, but you generate a lot of feedback, and most of it is not of high quality. You report a lot of issues where you have not spent 10 minutes looking at solutions...

The changelog for the beta builds show the changes between the current release and the beta. So those are still the changes. The only additional change is that Demonbuddy now should work on Windows 10 insider preview builds. I'll put that into the next changelog. EDIT: Also a newer version...

The beta version will prefer using old names, so if you only use 1 simultaneous Demonbuddy you should be able to get by with just two exceptions, as it will switch between those names.

Hahaha, thanks for the laugh. At least try running the code you share before you share it, and see if it will have the effect you think. This does nothing to the process name. Perhaps you should pick up a book on Windows. Maybe one that was about how process handles work.

The sym link is relative, not absolute. If you want the technical reasoning for the bug it is this Windows bug: https://support.microsoft.com/en-us/kb/2987926 The current DB beta (605 and up) should not have the problem, so you can use that with as many renames as you'd like.

Thanks for the steps! I can reproduce it with this. We will look at getting this fixed for the next release.

Sorry, but that's a wrong assumption. The renaming is not as straightforward as just changing the name of the file. If you did this before you were not safer than anyone else, and you're not safer if you do it now. The way the safety is achieved is not visible in the way you are looking at it.

Ok, great.

I think I see then. Is D: an USB drive? If it is you might need to reformat it with a different file system than FAT-32 to use Demonbuddy stored on this. For example NTFS.

If you open a CMD window as administrator and type "mklink Demonbuddy.exe dgayrjvbms.exe", what happens? Where is your bot folder stored?

Can you retry with the one attached? My French is not very good. :rolleyes:

Can you please try running the .exe in the .zip I have attached? Place it in the same folder as Demonbuddy. Make sure you run it as administrator, and report back with the results.

A new Demonbuddy beta is now available that should resolve this issue. You can download it here: http://updates.buddyauth.com/GetNewest?filter=DemonbuddyBETA Can you please try this and verify that it works?

Please attach a log. https://www.thebuddyforum.com/honorbuddy-forum/honorbuddy-guides/35945-guide-how-attach-your-log.html

The issue has been identified and we are working on a fix.

Can you PM me your Skype so we can try a fix that doesn't require workarounds?

Routers, switches, firewalls and so on. I'm assuming you are not managing this entire network yourself, so you probably need to find some of the network admins and ask for support. Do you have any other devices you can try the same tests on? For example a laptop. That will rule out any...

It looks like there are devices along the way that are filtering or firewalling you from getting a reliable connection to our server (as evidenced by the several request timeouts). Unfortunately this is not something we can easily help you solve - I do see there are several devices along the way...