+- Forums - Open Redstone Engineers (https://forum.openredstone.org)
+-- Forum: ORE General (https://forum.openredstone.org/forum-39.html)
+--- Forum: Build Discussion (https://forum.openredstone.org/forum-50.html)
+--- Thread: Why aren't we in 1.8 yet? (/thread-5479.html)
Why aren't we in 1.8 yet? - Phase - 01-05-2015
Seriously, 1.8 has been out for a loooong time, and the ORE can't even allow for 1.8 clients to connect. With Bukkit dead, we need to move on. Spigot is the obvious answer, as it supports Bukkit plugins. There were a few versions of Spigot that were 1.7, but allowed 1.8 clients to connect, so why not use those? We better update soon, cause we want to mess with slimeblocks! :3
Also, the first result is pretty cool: https://www.google.com/#q=redstone+servers
RE: Why aren't we in 1.8 yet? - Xray_Doc - 01-05-2015
Because 1.8 is a vacuum that sucks Microsoft's money dick.
RE: Why aren't we in 1.8 yet? - Phase - 01-05-2015
(01-05-2015, 12:52 PM)Xray_Doc Wrote: Because 1.8 is a vacuum that sucks Microsoft's money dick.
But 1.8 came out before Microsoft bought Mojang.....
and they also own Scrolls.....
RE: Why aren't we in 1.8 yet? - Chibill - 01-05-2015
There is 1.8 bukkit created my spigot but they have to fix the python plugins before they can update so hold your horses..
RE: Why aren't we in 1.8 yet? - Xray_Doc - 01-05-2015
(01-05-2015, 12:57 PM)Phasesaber Wrote:(01-05-2015, 12:52 PM)Xray_Doc Wrote: Because 1.8 is a vacuum that sucks Microsoft's money dick.
But 1.8 came out before Microsoft bought Mojang.....
and they also own Scrolls.....
Please don't ever take me seriously. I haven't really played minecraft in a couple years
RE: Why aren't we in 1.8 yet? - Phase - 01-06-2015
(01-05-2015, 02:26 PM)Chibill Wrote: There is 1.8 bukkit created my spigot but they have to fix the python plugins before they can update so hold your horses..
There is no reason they have to fix them for a 1.7 server. I'm just asking that we allow 1.8 clients to connect, because I hate having to switch my version for only this server.
RE: Why aren't we in 1.8 yet? - Chibill - 01-06-2015
So. The 1.7 version of bukkit had an update that broke pythonloader. The ones with the network patch have the commit that broke it...
RE: Why aren't we in 1.8 yet? - Phase - 01-06-2015
(01-06-2015, 02:04 PM)Chibill Wrote: So. The 1.7 version of bukkit had an update that broke pythonloader. The ones with the network patch have the commit that broke it...
Then maybe we should be like normal people and make our plugins in Java?
RE: Why aren't we in 1.8 yet? - tyler569 - 01-07-2015
(01-06-2015, 11:57 PM)Phasesaber Wrote: Then maybe we should be like normal people and make our plugins in Java?
If you want to rewrite 2 years' worth of code and pay back all our technical debt, be my(our) guest, the rest of us are sane enough to hang on to what we got while it works
RE: Why aren't we in 1.8 yet? - Chibill - 01-07-2015
I got a pat he'd pythonload that works with 1.8 I made that I could pass the current staff.