With help from @Kaiziieee , I made a plan good for BCSN, with the future of it hidden. STEP 1: Fix every single bug currently on BCSN. In these four threads you can see what these bugs are. I would prioritize Creative, followed by Forums, then Minigames, and lastly, Survival, based on the popularity. http://bcsn.us/forum/index.php?threads/current-buildcraftia-creative-bugs.3250/#post-38312 http://bcsn.us/forum/index.php?threads/current-buildcraftia-forum-bugs.3251/#post-38334 http://bcsn.us/forum/index.php?threads/current-buildcraftia-survival-bugs.3252/#post-38315 http://bcsn.us/forum/index.php?threads/current-buildcraftia-minigame-bugs.3253/#post-38319 STEP 2: Finish API. The dubbed "Penguin API.1337" has been in the works for just under a year, and honestly, it's getting old. Most people (Including Myself) feel as if this portion of the server has been abandoned, and that it's underdone. I feel as if the API is done, but it's not released, so I suggest this- Fix ALL the possible bugs in it before inserting it into the server. Once it is on the server, spend about a month paying close attention to forums, and making it FIRST PRIORITY to fix any bugs as soon as they arise. Do not add any more maps, suggestions, minigames, etc during this time. STEP 3: Factions. 3 Months ago, we were told that we're getting Factions. Since then, no new news has been release, nor has anything been seen Player-Side. But here's what I suggest. If you are almost done making the minigame, finish it, bug squash it, release it, and follow the same format as you did with the API. If it isn't nearly done, make a thread regarding what is being done on it, and push it to the side for a few weeks until the rest is finished. STEP 4: Staff Team. Currently, the staff team is in shambles. Moderators have gone off saying they don't have enough power, and few have even suggested bringing back Sr. Mods. I'm not sure what should be done to fix this, maybe by the time we reach this stage we'll need Moderator Nominations/Applications again. STEP 5: Maps. Currently one of the biggest struggles on BC is the Map-Making/Accpting, and most players get mad when all their time & effort go to waste. Here's what I suggest. Make a criteria for what a DTC/PB/PK map MUST have, as well as have a system where a map can be accepted by any staff, and make it easy for a map to be impletmented. Once again, fix all bugs with all maps IMMEDIATLY before going to the next step. STEP 5.5: If you have not already, add Factions, and bug-fix it. STEP 6: Work on suggestions. Add Suggestions/Minigames, fix any bugs as soon as they arise. If a bug arises, do not add any more Suggestions/Mingames until it is done. Take it 1 step at a time. Step 6 goes on for Infinity, but this is my idea for BC. Please suggest your ideas!
API's dont work that way. Saying that we should fix all the bugs now and then implement the API is like saying 'Okay, let's fix the TV before buying a new one'. It's a waste of recourses.
i'm kind of afraid that factions will be a hype at first but then gets abandoned after a while like survival :/
I like the plan, but I have to agree with what Olo said, however, I also understand your way of thinking. You're saying that before we release the new API, we have to make sure that all of the bugs, or at least majority of the bugs are done and over with, as to not cause problems in the future. Yes, this plan is taken in baby steps, but a little goes a long way. Thank you for putting your input
I agree with Olo: It's better to focus on the new one rather than waste time on our current one by fixing it. Initially, I'd like to state that I think our primary goal is to get some new and creative incentive by evolving the staff team. Recently, there has been a lot of hype over MacMeBenny (in addition to the minor server scare- Quicksteve didn't have access to the renew the lease this morning, risking BC's closure) in a negative way, but this is yet again, wasting time. Some of us are trying to be proactive and thinking of new ideas but we really do need a creative owner who can take BuildCraftia forward. I think that staff should look at the player base and select some people to come together and think of ideas. We're not moving forward at the moment. BuildCraftia can change that.
See, at the moment, were all struggling to get about. It's like when you put a brick in between ants when they're in a line; they scatter randomly. They have no order. That's how we are right now. Everyone is going to have a different point of where we should start on repairing the server overall, for example, I believe we should strive to make BCSN bug-free before adding anymore, as Kai said, "Fix little bugs before they become massive problems". You, however, believe that the first step towards a clean BCSN is by first updating the Staff Team, fixing the bonds with them and the players. It will ultimately be up to staff (Probably Leo and AZZA) to decide which path to take first: Bugs, Staff, or API.
I believe getting a solid staff team again is probably our priority. Getting a solid staff team will make developing the API easier , because things like ban reports or map requests wouldn't have to be taken care of by the owners only. (at least, if we give some more well-needed permissions to mods/admins)
I think honestly our first priority is to fix the clusterfuck that is currently staff team. Get a good hierarchy, more staff who are active, and quality staff as well. That in itself is a tall order. IF we can complete this then we must move on to the API, finish that. After that we still have a lot of work to do, and so many ways to go about it. Probably the wisest idea after staff and api is to expand our player base. Obviously we can't just say that we will expand our community and then tada, it's bigger. No. We need to advertise our server on those mc server websites, all of us in the community need to reach out to friends and get them. And that is also going to be one hell of a task. So in essence, I agree with what needs to be done, but not necessarily the order.
So basically: STEP 1: Fix the staff team (TBD how) STEP 2: Finish/Release API STEP 3: Bug-Fix Everything
Not quite. Player base is #3. Honestly we have bugs but it's not distracting so those can be fixed later tbh
Well, I think that 1 or 2 bugs should be first priority, such as the PB Joining Bug (too which you cant pick a team/kit), the vanish bug, and the books bug. Though the last 2 are probably out of our reach, we can try. Fix the first one, at least.
Staff? New Staff? What are you on about lmao All the decent candidates for staff have either Come and gone Retired Currently are staff Left BC Got banned Got the boot from Matty and still hate BC for it (lets not go into detail about that here) And any decent people who could be staff who don't follow the criteria above don't want to do it.
Anyways, we can't even fix the vanish bug or the books bug, as Leo and other staff members have said MULTIPLE times.
