MC1 Update
The reason MC1 has not updated yet is not due to my laziness. It's due to the laziness of a man that is known as DiddiZ. This man is the creator of LogBlock, which has failed to meet the burden of updating in time for me to sack up and get around to updating the server. This means we will have to wait until even a dev build is made for 1.2.5. I will be checking daily, however I have no prediction as to when a dev build will be released. I am, however, contemplating switching to another tool, such as BigBrother. I know it's not the most popular option, but it's the most rational option at this time (until LogBlock updates properly).
MC1 has updated to 1.2.5!
If you notice any bugs, please comment below and I will add them to the list (and attempt to fix them).
- BUG LIST:
- Minecart Mania does not work
Not Fixed
Fixed
- Banana937's blog
- Login or register to post comments
If you switch, look into hawkeye before bigbrother.
HawkEye isn't updated either.
Big Brother is apparently dead.
Exactly why we haven't updated yet.
Pffft, lies, you're just lazy ;D
Bugs:
GM change at relog.
Fire charges usable by all ranks. (Mods only?)
Fire charges can be put in a dispenser and shot by any player i believe.
I am unsure if it's fire is different, will check.
Thats all,
_ONLYUSEmeBOW ;D
An owner should unsticky this...
The GM change on log in still needs to be fixed :L


The reason I just figured it out today is because of my ridiculous workload that teachers tried to force upon me before break (as well as extracurricular activities). Immediately after school every day I have track until 5, which, on Tuesday, Thursdays, and Fridays, is immediately followed by baseball until 7. Thursday I had two assignments--a history paper and a math project--that I needed to get done; Friday I had a Spanish test. Due to this, I had been busy with work this entire week, ending at 7:00 PM EST last night. This was when I finally got around to attempting the upgrade, which was shot down when DiddiZ became a lazy fuck.
But....didn't you just find out the plug-in wasn't updated today? Wouldn't that mean you wouldn't have looked for it before today...?