Because everyone wants to know — 1.4.6 Status

I’m not even going to bother telling people not to update right away because.. because… oh crap, I just did. Ignore that. (and the update)

Downgrade Guide

So what’s holding up the things and the what-not. Well, the what-not is fine. So don’t you worry. But here’s the things… First, Craftbukkit hasn’t been updated yet to support 1.4.6. That’s not all that concerns me, because some plugins have yet to be updated to be compatible with breaking changes the Craftbukkit guys made in the lastest 1.4.5 builds. In fact, one of the guys defending one of the breaking changes is the author of our main plugin that’s still broken and un-updated! Oh, the sweet succulent irony has a bitter aftertaste. I was going to update to 1.4.5 R1.0 today in preparation for 1.4.6 builds; however, I had to hold off because too many things broke — and that’s after updating 11 other plugins that needed it.

Until PhysicalShop is updated (and hopefully RecipeManager) I’m not sure it’d be wise to move to the new builds of Craftbukkit. And only then can we consider updating to 1.4.6.

4 comments on “Because everyone wants to know — 1.4.6 Status

    1. PseudoKnight Post author

      I’m still waiting for plugins. I’ve appealed to the plugin developer, but I’ve heard nothing back. It might be a plugin I should replace later. Unfortunately I don’t have the time to do it right now and by the time I was done there’d probably be an update. Since it’s a critical plugin, I don’t want to use it in its broken state on 1.4.5 R1 or later.

      I really wanted to get it done before Christmas, but it looks like I’ll have to settle for New Years Eve as the new goal.

  1. PseudoKnight Post author

    So, I’m planning on updating to 1.4.6 later today. I’m doing my last testing, so I thought I’d update on the details.

    I went through the code for PhysicalShop to determine how dangerous it was to use. It turns out that it breaks 3 features: redstone trigger (which can be disabled), showcase (which I already have disabled, and auto-disables anyway), and enderman protection (which causes spam in console, but otherwise is protected by worldguard anyway). I might disable Endermen temporarily, I’m not sure. It’s pretty spammy.

    Also, I’m using a 3rd party update for RecipeManager temporarily, as it only needed to be built against 1.4.6.

    Group names won’t be supported on Deadbolt signs anymore, with the exception of [Everyone], because we coincidentally used the same word as his hard-coded everyone access.

Leave a Reply