Well, ever since the latest DB version (both Stable and BETA) came out many people have been getting this error over and over and over again, posting threads in both in the support, trinity and in general about this problem trying to get some help. However, whenever someone have had THIS issue, admins have always answered them with the same routine answers.
- Post log (Will not care to answer something els like we are aware of this issue ect)
- Use BETA (if using Stable build)
- Use Stable (if using BETA build)
- Run only Trinity/QuestTool plugin.
- Are this happening on all Profile.
- Remove/Install C++.
When I posted this issue at the very beginning when the latest DB came out, the admin first said that it was a Trinity problem and that I should post it in Trinity section but rrrix quickly replied that it was a demonbuddy software issue. I posted this asnwer in my thread in the support sectio but nothing. They "act" like this issue is user-related and not software related. So, whenever I saw people posting this problem in the support section, instead of them having to listen to the same routine answers, I gave them a answer that actually fixed the problem (Use a earlier version of the demonbuddy which works) but that ended with the admin blocking me from posting anything in the support section. Ignorance?
I was getting this error all the time on EVERY bot I was running on EVERY machine I was running it on (I have 5 machines available) so I was kinda frustrated because I knew it was not user related at this point....
I might be out of line trying to help people to actually use demobuddy by recommending them to use a working older version, but I also feel that the developers should at least post something that they are aware of this issue and that they are looking into it. I know that the admin has said at some rare occasion that the developer will look into the problem on some of the threads in the support section but when a new user post a new thread in the support section about THIS problem, its the same answerd all over again instead of saying something like this:
Hi
We are aware of this issue that are occurring to many users and we are currently looking into a fix, you can meanwhile use a older version of 392 as there have been reports that this problem dont occur on here. If you want to troubleshoot yourself you can try to remove every plugin except of trinity and questtool and just running x profile. ect
- Post log (Will not care to answer something els like we are aware of this issue ect)
- Use BETA (if using Stable build)
- Use Stable (if using BETA build)
- Run only Trinity/QuestTool plugin.
- Are this happening on all Profile.
- Remove/Install C++.
When I posted this issue at the very beginning when the latest DB came out, the admin first said that it was a Trinity problem and that I should post it in Trinity section but rrrix quickly replied that it was a demonbuddy software issue. I posted this asnwer in my thread in the support sectio but nothing. They "act" like this issue is user-related and not software related. So, whenever I saw people posting this problem in the support section, instead of them having to listen to the same routine answers, I gave them a answer that actually fixed the problem (Use a earlier version of the demonbuddy which works) but that ended with the admin blocking me from posting anything in the support section. Ignorance?
I was getting this error all the time on EVERY bot I was running on EVERY machine I was running it on (I have 5 machines available) so I was kinda frustrated because I knew it was not user related at this point....
I might be out of line trying to help people to actually use demobuddy by recommending them to use a working older version, but I also feel that the developers should at least post something that they are aware of this issue and that they are looking into it. I know that the admin has said at some rare occasion that the developer will look into the problem on some of the threads in the support section but when a new user post a new thread in the support section about THIS problem, its the same answerd all over again instead of saying something like this:
Hi
We are aware of this issue that are occurring to many users and we are currently looking into a fix, you can meanwhile use a older version of 392 as there have been reports that this problem dont occur on here. If you want to troubleshoot yourself you can try to remove every plugin except of trinity and questtool and just running x profile. ect
Last edited:
