What an embarrassing response, @
TheBoredom, definitely not the way you should represent yourself or BAW as it comes off as defensive and irrational mainly because your argument doesn't make a lot of sense. Arguing against applications is completely illogical as applications would rid BAW of many of the problems it presents. For one, there would be less reason to complain about not being picked by those who want to join the team. By having everyone go through the same process it won't just be staff picking from a limited "list of people who were in RBI" but instead allowing the entirety of the community, which you've emphasized so much in your argument, to have a fair chance at participation.
Secondly, applications could also stem to a series of articles introducing BAW members at the start of a season after applications are closed and a team is chosen. Having a "BAW team showcase" of each team would use elements submitted from applications (i.e. room screenshots, room competition wins the user is most proud of, favourite furni line, a building tip or trick, etc.). By having these elements in an application it would allow for the community to see how and
why each user has been chosen. As a result there would be fewer complaints because many of the accusations of favouritism and nepotism would be proven invalid. The community could see the dedication and creativity a team member has, which could be helpful in cases where a user doesn't keep rooms up or unlocked.
Finally, I just don't see the logic in
not having applications in terms of staff workload. Proper application processes can streamline the amount of time and effort staff would have to put in to their selections. They wouldn't have to comb through a selection of users, try and piece together their talent level by seeing random rooms the users have or may not be especially proud of. If a BAW team member recommends a user for the next season, staff would easily be able to pull up their application and see exactly what the user is capable of rather than listening to a biased or quick recommendation from a user.
As it stands, BAW, like RBI, is a flawed system, and by being apart of the first couple rounds, current team members should be looking at the community's feedback as insightful and beneficial, rather than attacks. You guys should be coming on forums and building off our ideas instead of getting defensive and completely rejecting them. I for one don't care who's on the team, as long as I can see
why they've made it on the team. That's why we need applications and more publicity and showcases of the BAW team. If you won't take the community's advice about applications and revamping the selection process, then at least take my advice right now and act a little more level-headed; you aren't above the community by being on BAW, rather you simply have a chance at bettering a facet of it that right now is flawed. Accept BAW as a fluid concept and work to offer staff feedback on how to develop and change it to benefit the experience of users interested in this aspect of Habbo.