Our Minecraft servers are offline but we will keep this forum online for any community communication. Site permissions for posting could change at a later date but will remain online.
Why?Please stop with these complaint threads.
So what do you recommend MCG does, just live in the past because it has "better pvp" and never update it to any later versions of Minecraft and miss out on all the other futures that will be added later down the road.
No-one ever said we should never update. That's an argument used by mods in the hope that Chad recognises themthey should have waited until a more stable version came out before updating
Im pretty sure Chad uses the money to support the server...The Hives plugin is a a fully functional 1.7-1.8 server. It requires full 1.8 for some games, and has the cool 1.8 features. Clearly chad is money hungry and wants to go with interesting sounding thing, that will put money in the servers wallet (ultimately his wallet).
I, or other people, have already touched on the other points have been listed in your original post. But I did want to make a comment on this section. Keep in mind I'm no Developer, but I generally understand what's going on.I completely agree with this statement. But it can easily be outdone, and I've seen TheHive do it. Their newest game mode, Deathrun, is only compatible with 1.8. But did they ever upgrade to 1.8? No. All they've done is that the game mode could not be accessed with lower than 1.8, and every single other game mode work with 1.7 and 1.8. Why can't MCSG do that?
We've heard this statement since 2013. It is now 2015, and we're twice the size that we were back then. I definitely don't think that's the definition of "dying".Sorry, but one day you will wake up to the truth that this server was once great to play, for reasons that are now quite obviously out of the reach of developers. The server has grown old, and it is now dying.
Yup, no denying that we're bad at deadlines. But again, it's never a matter of, "Oh, we just got lazy and didn't do anything, which is why we missed the deadline".The update to 1.8 was inevitable, but your argument for the leaderboard update has been left alone, MCSG has pretty bad punctuality lol
Hahahaha I love your posts.I, or other people, have already touched on the other points have been listed in your original post. But I did want to make a comment on this section. Keep in mind I'm no Developer, but I generally understand what's going on.
When you describe the dual-version usage of 1.7 and 1.8 (dual protocol) for the gamemodes of that other community, that's basically what we've been using prior to February 3rd. But that proved to be an issue for us, since now we had to provide for (i.e. code updates and changes for) two different versions of Minecraft, effectively doubling our work. On top of that, we couldn't take advantage of some of the back-end functions that 1.8 offers, so we were basically running at a 1.7-less developed level. When we pushed 1.8, got both a single platform to play with plus some back-end functionality to use.
The way that other community did it isn't truly 1.8; it's a dual protocol hack, and admittedly a clever one. But that really isn't an update, since if it's forcing users to use 1.8 but only running 1.7-level code. So what they have right now is a system that thinks it's running 1.8 but is really running 1.7; it's stable, but it's not an upgrade. And that means that once the 1.7 code becomes depreciated, they'll have to do their own full 1.8 update as well. They didn't early adopt 1.8 like we did, they simply slapped a band-aid over the version gap to make it last a little longer (before they have to go through the same arduous update process we did).
We've heard this statement since 2013. It is now 2015, and we're twice the size that we were back then. I definitely don't think that's the definition of "dying".
I'll admit that our community, like every community, has its flaws. But just because you don't like the way things are now doesn't mean that we're doomed.
Yup, no denying that we're bad at deadlines. But again, it's never a matter of, "Oh, we just got lazy and didn't do anything, which is why we missed the deadline".
Usually, it's always a matter of, "OH MY GOD THERE IS SO MUCH STUFF THAT NEEDS TO GET DONE- AND ALL THIS OTHER STUFF THAT CAME OUT OF NOWHERE. SO MUCH CODING AND TESTING THAT STILL NEEDS TO GET DONE. HOW DID WE EVER THINK WE COULD MEET THAT DEADLINE? Well, that's just apologize for the delay and get back to work."
That's basically the Dev chats all day, every day.