What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

This Buddystore is a complete mess

Status
Not open for further replies.
Aaaah the good old "i paid for it so It must be available 24/7" logic.
What about Security updates, general technicial issues that need to be solved and sometimes are unplanned and adding functions?
People complain that we take care about the servers and service it delivers. Really?
So you complain if we do not fix issues and you complain if we do. Strange^^

I agree that communication could have been better and we will learn from today but this thread is the most stupid I've seen here for a very long time sorry.

Btw. do you post every wednesday in the Blizz forums if their servers go down that you paid for stuff and that they should stop doing their fixes and updates because you wanna play? omg!
I think the issue is way deeper than what you make it. Basically, we were sold one product and it has evolved into another that takes up more resources from our systems to benefit the parent company. In order for HB to benefit in dollars and cents it instituted a streamed system where things could be rented but not purchased. This means, that we are entirely reliant on them for when this is and is not available and just how much it taxes our connections. Now, can we blame them? No, EVERYONE wants to make a profit anyway they can. All the OP is saying is, it was better before (and it most certainly was, for users). Let him have his say without becoming, erroneously on all points, defensive.
 
What I think that would be nice is if you could make those announcement show up forum-wide so if I am in the honorbuddy forum I can still see that there is a new announcement made, old ones should not appear ofc.

I for one don't check anything outside the honorbuddy forum section so if you guys could make the announcements forum-wide it would be awesome I think vBulletin offers such a functionality to make it show up everywhere.
 
My only issue with the store is having to wait 15 hours + everytime a routine I use is updated. There is no legitimate reason to delay updates like that. Nothing worse than HB being down on a patch day only to have it come back up right before raid time but your routine is still broken with an update waiting to be approved. SVN worked, not sure what we gained from ditching it.
 
There is no legitimate reason to delay updates like that.
Of course there are plenty of since the Staff in charge needs to review the code to:

- Make sure the code is safe to run within WOW
- Make sure there is no malicious code within
- Make sure that the code runs without breaking the bot

Could point out more but guess 3 is just fine.

EDIT:
If you have the SVN option then you could just use it from the SVN rather than the buddystore if that is what you're displeased with as you said the only difference is that the SVN is the latest while the store is yet to be approved as its streamed code rather than offline.

This plus the fact most developers don't offer SVN anymore due to the fact they can now properly have their code hidden and streamed along with HB rather than having to either give you the source or obfuscated DLLs to protect it.

Of course you can see the code but won't get into details on that.
 
Last edited:
Of course there are plenty of since the Staff in charge needs to review the code to:

- Make sure the code is safe to run within WOW
- Make sure there is no malicious code within
- Make sure that the code runs without breaking the bot

Could point out more but guess 3 is just fine.

I've seen plenty of posts stating the staff can't test each and every routine. I don't believe for a second that every single update is tested in a thorough manner. And even if they are, there should be a trusted developer status for those devs who support their routines with frequent updates.
 
I've seen plenty of posts stating the staff can't test each and every routine. I don't believe for a second that every single update is tested in a thorough manner. And even if they are, there should be a trusted developer status for those devs who support their routines with frequent updates.
There is a difference between test and compile the code and what I meant by run is exactly compile it and not actually test each and every product in an attempt to see if it works as they are announced to. If the code cannot run during compilation it break HB startup not sure if they have any protections to exclude broken push like that but if you put a broken plugin for example it will throw errors saying your plugin is bad and will not load it, however I believe with the streaming the process is slight different.
 
Last edited:
There is a difference between test and compile the code and what I meant by run is exactly compile it and not actually test each and every product in an attempt to see if it works as they are announced to. If the code cannot run during compilation it break HB startup not sure if they have any protections to exclude broken push like that but if you put a broken plugin for example it will throw errors saying your plugin is bad and will not load it, however I believe with the streaming the process is slight different.

Thanks for bolding that, think I would have missed it otherwise. My other point still stands, they should have a trusted developer status. Would solve the problem imo.
 
I think the point has been lost here, the original question, is to avoid these issues... go back to svn.
 
Hey devs i have split thoughts too especially after today but i have an idea :p

Why not put up a second auth server that works beside the main server. Many companies does that.
Then u can bring down or have a crash and the other kicks in for safety and stability of your products.
:cool: and also the best reason u dont get forums spammed by 97% of the user community :cool:
 
Thanks for bolding that, think I would have missed it otherwise. My other point still stands, they should have a trusted developer status. Would solve the problem imo.
Well while I do think something like that would or could be a possible solution, that is rather more complicated then it looks like. Having a trusted title is fine the problem is how to label one as trusted and what happens when things go wrong as he/she would literally have access to make it go wrong.
 
Status
Not open for further replies.
Back
Top