You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@Gjum I have seen mineflayer, but it is just not as well thought out as Spockbot and the bots that people have made with it aren't as good as the one that people have made with Spockbot. Also, will you just update to 1.10, or will you go all the way to 1.11?
The difference between 1.10 and 1.11 is minimal in terms of the protocol, so if I get it to 1.10 it'll be easy to also make it work in 1.11. My personal use case is for 1.10 though, so I will focus on that primarily. If possible I will keep 1.11 in mind too of course.
Nope, I went a different path, so don't expect any updating from my side. Sorry!
If you still want to use this with 1.10/1.11/1.12 you'd need to put in the work of updating it yourself, but if during that you have any questions about the inner workings of SpockBot, feel free to contact me.
I also have been out of date with the project. I have mainly switched to C# for work so I haven't touched python in a while. The main use I had for this project has been replaced with https://github.com/Microsoft/malmo
I can provide some help answering questions and review pull requests but I am looking to see if anyone else wants to become the main maintainer of the project.
I just wanted to comment on a possible work around for using Spockbot with newer servers would be to use Bungeecord with viabackwards, viaversion and viarewind.
Probably not the best solution for the problem but it's a good solution if you don't want to use malmo or mineflayer.
@yunfan Our protocol was mostly separate from implementation stuff. There is a certain amount of coupling you can't get around (if a packet that you relied on for say, movement, is completely removed you have to use the new packet that replaced it).
Spock is gone for two reasons that aren't related to implementation. 1) Lack of developer time but mostly 2) Better alternatives are around now.
@yunfan Yes. Python has never been a popular choice for MC hacking since Java and now C# are so favored by the community. Projects in those languages as well as mineflayer are way ahead of anything Spockbot did.
But as a said last year, if you make a pull request and the code builds (we need some standards) I'm happy to give anyone push privileges.
Activity
Gjum commentedon Jun 1, 2017
I might pick it up again and update it to 1.10 in the next few weeks because I have a use for it again.
In the mean time, you can also look into https://github.com/PrismarineJS/mineflayer/
ali6836 commentedon Jun 1, 2017
@Gjum I have seen mineflayer, but it is just not as well thought out as Spockbot and the bots that people have made with it aren't as good as the one that people have made with Spockbot. Also, will you just update to 1.10, or will you go all the way to 1.11?
Gjum commentedon Jun 1, 2017
The difference between 1.10 and 1.11 is minimal in terms of the protocol, so if I get it to 1.10 it'll be easy to also make it work in 1.11. My personal use case is for 1.10 though, so I will focus on that primarily. If possible I will keep 1.11 in mind too of course.
Gjum commentedon Jun 15, 2017
Nope, I went a different path, so don't expect any updating from my side. Sorry!
If you still want to use this with 1.10/1.11/1.12 you'd need to put in the work of updating it yourself, but if during that you have any questions about the inner workings of SpockBot, feel free to contact me.
nickelpro commentedon Jun 22, 2017
Submarines are not a conducive environment to coding projects. So I'm out. I'm a huge fan of giving push privileged to literally everyone though
gamingrobot commentedon Jun 23, 2017
I also have been out of date with the project. I have mainly switched to C# for work so I haven't touched python in a while. The main use I had for this project has been replaced with https://github.com/Microsoft/malmo
I can provide some help answering questions and review pull requests but I am looking to see if anyone else wants to become the main maintainer of the project.
yunfan commentedon Jul 3, 2017
why not use a seperated protocol layer? like pyCraft, i saw it has support to 1.12, but it only focus on protocol level
CoderReece commentedon Jun 30, 2018
I just wanted to comment on a possible work around for using Spockbot with newer servers would be to use Bungeecord with viabackwards, viaversion and viarewind.
Probably not the best solution for the problem but it's a good solution if you don't want to use malmo or mineflayer.
nickelpro commentedon Jul 10, 2018
@yunfan Our protocol was mostly separate from implementation stuff. There is a certain amount of coupling you can't get around (if a packet that you relied on for say, movement, is completely removed you have to use the new packet that replaced it).
Spock is gone for two reasons that aren't related to implementation. 1) Lack of developer time but mostly 2) Better alternatives are around now.
yunfan commentedon Jul 11, 2018
@nickelpro by alternatives, are you meaning those non-python solutions?
nickelpro commentedon Jul 11, 2018
@yunfan Yes. Python has never been a popular choice for MC hacking since Java and now C# are so favored by the community. Projects in those languages as well as mineflayer are way ahead of anything Spockbot did.
But as a said last year, if you make a pull request and the code builds (we need some standards) I'm happy to give anyone push privileges.