Comments on: Yes, I am aware Minecraft is now on 1.7

By: Archer665

Archer665 — Fri, 01 Jul 2011 16:19:49 +0000

++++++++++1

By: EagleRock

EagleRock — Fri, 01 Jul 2011 14:53:02 +0000

As Tim said, updating is not the issue. Updating with no way to roll back the update is the issue. Almost incessantly, I would get people bitching at me that they can’t play on the server anymore and they want me to update ASAP. So, update all you want…as long as you have the backup. Check out this post:

http://web.eagleworld.net:8000/minecraft/?p=321

By: Tim (SpaceNinJA)

Tim (SpaceNinJA) — Fri, 01 Jul 2011 14:46:17 +0000

I updated, and hmm. I can still play on eagleworld. doesn’t mean I have SNS, you just need to learn to backup your files

By: Jbkarate9

Jbkarate9 — Fri, 01 Jul 2011 00:31:28 +0000

Lol anyone who updates has SNS Syndrome.

By: EagleRock

EagleRock — Thu, 30 Jun 2011 21:29:46 +0000

It’s supposed to, but then again, he wanted to bring out the modding API back in 1.6. It keeps getting pushed back. I remember a tweet where Notch was saying how much more fun it is to develop cool new items rather than the API…that told me everything I needed to know about the priority the modding API has.

So, long story short…I am not holding my breath.

By: SanctusTerra

SanctusTerra — Thu, 30 Jun 2011 21:09:22 +0000

doesnt the modding api come out next update?

By: ljdarten

ljdarten — Thu, 30 Jun 2011 18:54:17 +0000

I have NO problem with waiting as long as you want to update. we already know this is beta stuff. I don’t know why people would want to make the problem worse by having bleeding edge stuff.

if someone really needs to play with the latest toys, they can look up how to switch between versions and play single player or other servers. much easier than what you will need to do to update the server.

Am I understanding correctly that updating the client will cause it not to work on eagleworld? if yes then I feel bad for those who can’t join. not much we can really do about it, would be nice if notch and co would let people download the last couple versions. seems to me that is common practice for software that is updating often.

By: openminded

openminded — Thu, 30 Jun 2011 17:39:54 +0000

DO………….NOT………….UPDATE…. I will have to redo all My TNT traps around moosecreek and the one I put under eagle manor. Wait, I mean “The other traps I left in other non specific, unlabeled places.”

YOU are not allowed to 1.7 Ever.

That is all.

By: EagleRock

EagleRock — Thu, 30 Jun 2011 17:37:19 +0000

Well, the best thing Notch could do to assist this is to create a modding API that plugin developers can use. The problem is the Bukkit team has to create a server wrapper to produce this API. The wrapper basically needs to hook in to all the different functions in the Minecraft server application to provide additional features, such as warps, iConomy, etc. The problem is every version, the functions in the Minecraft application change slightly, just enough to break Bukkit from working. They have to redo the API to work with all the functions again, which changes the API slightly, just enough to cause most plugins to stop working. Then, plugin developers need to redo their application to work with the new API.

Notch has taken a “it doesn’t matter that much” approach to the modding API, which means we have to follow the same approach every upgrade. Once we have a full-fledged server API, plugins will not necessarily break every update, and will usually only need to be updated to take advantage of new game features (such as new items, monsters, etc.). That will take a lot of steps out of this and make it very streamlined to upgrade the server safely and in a stable manner. Until then, we get to follow the same rigamarole every time.

By: SanctusTerra

SanctusTerra — Thu, 30 Jun 2011 17:24:04 +0000

i wish notch would take the same approach