The community does not decide what the priority of the developers is.
I see what you mean and I don't disagree, however no community = no business = no bot. The same can be said of devs so it is a paradox. I can't think of another software company that take the attitude of 'to hell with what the community thinks, I do what I want' and ended up successful. There was a small game dev company here in Australia where the manager had that approach and they didn't last. I am not however implying the same of Honorbuddy, it is mealy simple project management. Identify the stakeholders and gather the requirements then produce the product. It's not really rocket surgery.
"'to hell with what the community thinks, I do what I want"
What?
![]()
This a direct result of what the community thinks, over 200 bugs fixed since we implemented this system.
Bugs were reported then lost in communication and things weren't fixed when they were supposed to.
We now have a way to document all of our bugs, know its priority, see what was fixed, and see when it will be in a release.
Lot of focus was placed on Questing (which has become pretty stable) and fixing core functions.
Dungeonbuddy has been getting bugfixes, but no one has had time to write the scripts for the last part of SoO, which I plan on starting soon.
We listen to what you want and we listen to what you report for bugs, but ultimately priorities are set based on what we think needs more work to be stable.
why dont we see Tripwire on the poll. single most efficient, necessary item on the agenda.
if the EYE OF SAURON can see me, I want HB to shit itself and shutdown immediately.
Very good job to the devs on responding in this thread, we like to hear from you once in a while.
why dont we see Tripwire on the poll. single most efficient, necessary item on the agenda.
if the EYE OF SAURON can see me, I want HB to shit itself and shutdown immediately.
Very good job to the devs on responding in this thread, we like to hear from you once in a while.
This should be default for every commercial software project of the size of HB. And what do you mean by "now". Didn't you have a "bugzilla"/"jira" from the beginning of your development? Wow... just wow......
We now have a way to document all of our bugs, know its priority, see what was fixed, and see when it will be in a release.
...
This should be default for every commercial software project of the size of HB. And what do you mean by "now". Didn't you have a "bugzilla"/"jira" from the beginning of your development? Wow... just wow...
I am pretty sure there was a time where you forced your users to report bugs via ticketing system. That was hilarious. Using the user base as a test factory.
Thebuddyteam has never been very professional, don't expect things to change lol.
Thebuddyteam has never been very professional, don't expect things to change lol.