If it isn't going to get implemented, why keep escalating it?
Escalating doesn't mean it's going to or not going to be implemented, it means that the staff member that escalated it brought it to the attention of those in senior management concerned.
Looking at everything developers have done for CubeCraft in the past 5 years I can assure you this isn't even 50% of their hardest tasks. If there really is a reason why this hasn't been implemented yet it must be that the management team underestimated the priority which is completely their fault.
From my own personal experience, features that appear "simple" to implement most of the time are not, if I was to implement it, I'd create a whole new table in a database for the kits if it doesn't exist and associate the kit ID to the player ID in a relational database, so when a player logs in his prefered kit would be linked to him and thus set as the default choice if he chooses to join a game. This would represent a good 8 hours of work (in PHP), and that's ignoring all the constraints linked to the massive data structure that cubecraft certainly has.
As much as I'd love to see this feature, implementing this would certainly take time, time that cubecraft also needs to share with a big list of tasks.
There is no way of knowing where this task stands on that list, or if it is on that list at all. We mods bring up to senior management what we think is cool, useful or needed. It is not our job to know or choose what tasks are to be handled or their priority.
Ladies and gentlemen, cubecraft management in a nutshell.
You suggestions are heard! We promise!
Your suggestions are heard.
