Moderizing code is no easy task. Updating your own code that you wrote is one thing. Updating someone else's code is a nightmare. ... So no, you don't need to consider proposed improvements at this time. I completely agree with them prioritizing the functionality of the current model before trying to improve anything else. Trying to work in improvements at this stage will just make functionality testing even more complicated.
No friend, I don't agree with you here. I'm not sure how the codebase looks like, but from what I can gather and the fact that Justin did the mobile app, it is clear that there is a separation between the frontend, backend and engine parts of the game. Which is how it should be. So you can take this big part and split it in smaller problems that you can tackle.
Engine should be the most complex to rewrite, but I would argue that just re-writing it with no architecture changes would not help. Making architectural changes afterwards would be as complicated as making them now. It just adds delay.
You can easily have automated tests that check the results from one engine with the other and figure out if your changes break / change things or not.
However, UI and backend API changes should not be as complicated and can be worked separately.
Of course, it all boils down to the amount of resources available to do this in paralel.
Now it would be nice for a little update here and there. But then again, they just gave one and you STILL complained. If I were them, why bother?
And no, it's a bad idea to tease anything that isn't 100% going to be in the final version. Lest you get "You promised..."
I'm not sure at what update you refer. The only update that we got is that they have no update.
They are talking about some mockups for UI, but nothing.
As a general rule of thumb, working like crazy in the basement of your house with the expectation that everybody will love what you built is a very bad way of developing products.
If I was in their shoes, I would do the following:
- get someone to be community manager here, gather feedback, provide updates once per month
- put together a developer blog where you guys can share with us what you are doing, interesting findings , interesting bug fixes and such
- split the project into multiple phases, tackle them one by one. identify the biggest need and focus on that ( as it's clear that you have a small team)
- think about how you could make part of the APIs open to developers and open the environment for outside help (buzzer-manager site is very helpful and it was not built by BB team).
The way they are going about it at this point raises a lot of questions and risks (even for their company not just the game). If you plan on working 2 years to update a 20 year old engine without any communication or updates in the meantime, you might find that after 2 years there are 100 players left. or maybe in the meantime some new competition appears and your game is obsolete even with the newly coded engine.
So yeah, sorry if maybe my messages seem aggressive, I just want what's best for the game as I still enjoy it. and success of the game is tied to company, so in the end I do what's best for the new owners as well. But to me this lack of communication and not tapping into this valuable resource (the users) it's baffling.
Last edited by therin at 7/21/2025 5:58:37 AM