Forums - Open Redstone Engineers
Testing Bots on the Build Server - Printable Version

+- 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: Testing Bots on the Build Server (/thread-10882.html)

Pages: 1 2


Testing Bots on the Build Server - Phase - 09-13-2016

In early 2015, I started my first Minecraft bot: PhaseBot. This bot worked on by many members of the community, including John and Gio, on and off until early this year. A few weeks ago, I started another bot. This bot was met with praise from members seeing Owk return to ORE, and work was going rather swimmingly with the new codebase being written in Kotlin instead of Java.

All of this came to a sad end when Nickster258 logged on IRC. He noticed my commands to the bot in chat, and swiftly shutdown the project. Owk's permissions were removed and he was made a visitor, giving him no rights to break or place blocks. Nick quickly told me that I was not allowed to test Owk on ORE, and I had to continue development on another server. I bargained with him, saying I could remove chat commands by implementing private message parsing, and I could remove relogs with code hotswapping, but this wasn't enough for Nick. Not long after my bot was prohibited from joining the server, another bot logged on. An IRC bot, owned by none other than Nickster258.

I'm here to ask for permission to test pabot, the newest incarnation, on ORE. As previously mentioned, I can take many precautions to make pabot as silent as possible, while also making something the community can enjoy together.


RE: Testing Bots on the Build Server - Nickster258 - 09-13-2016

get your facts straight:

1) I was not the only one expressing concern about this bot. Nonemu was there also and expressed equal concern.

2) My bot is an IRC bot that only PMs people while this bot has, at least in the past, messaged publicly. As I told you at the time, an in-game bot with the permissions capable to destroy the entire server is not quite *ideal*.

3) After some short discussion between you and Nonemu that day, we agreed that removal of those permissions while retaining access to the server seemed okay.

k den...

I am willing to *consider* giving it more capabilities but at least not to the full extent of a builder. Maybe a custom rank (with precautions against worldedit, blockplacing floodrates(?), and chat) and not just "builder" given the [Bot] tag.


RE: Testing Bots on the Build Server - VoltzLive - 09-13-2016

Nickster, a Player could just as easily destroy the entire server.

Ultimately, Phase would be responsible for the bots actions. It's no different than himself doing it.


RE: Testing Bots on the Build Server - Nickster258 - 09-13-2016

(09-13-2016, 06:14 AM)VoltzLive Wrote: Nickster, a Player could just as easily destroy the entire server.

I think there is a difference between a bot and a player, if I am not mistaken.


RE: Testing Bots on the Build Server - VoltzLive - 09-13-2016

Elaborate then, What could a bot do that a player couldn't? Or a player with tools such as a modded client.

I see it like this, The bot is one of your accounts, and You are ultimately responsible for the actions of your client. Why should it be any different to a bot?


RE: Testing Bots on the Build Server - Phase - 09-13-2016

I would have to explicitly send StartDigging and FinishDigging packets hundreds of times to do any real damage. That's not just "break the block at x, y, z", I need do all sorts of calculations involving tool times and block faces. Players also have a reach limit, so I'd need to move to any location I want to break. This is a lot to do "accidentally". A malicious script could do this, but Voltz and I, the only people currently on the whitelist, aren't going to make nor run such a script. Limiting his abilities limits his usefulness. What if I want to run WE commands to do complex rotations of objects? The more the bot is allowed the do, the better we can build it.

Private messages are manageable, meaning it would take less than 15 lines of code to make the bot completely silent.


RE: Testing Bots on the Build Server - Nickster258 - 09-13-2016

You are right, the bot is under your control and whatever it ends up doing, you would be held liable for it.

I am willing to give it special permissions. As I said, a new rank so it will no longer be classified as a "member" but as a "bot", so the permissions behind it can be set according to not only your bot, but potential, all be it highly unlikely, bots later down the road.

I do ask though: what is the functionality of this bot? Does it create things others have already created, or do your building for you? I personally don't see the full usefulness of it other than a really cool programming project, so it is hard for me to sympathize to this specific thing.


RE: Testing Bots on the Build Server - Phase - 09-13-2016

The end goal for it will to be able to run survival on its own. In the meantime, I would like it to do some creative things. Having it build complex redstone circuitry, that it understands, would be awesome. The project will evolve in time, and goals may change.

Edit: Private Messages are done


RE: Testing Bots on the Build Server - Nickster258 - 09-13-2016

(09-13-2016, 06:45 AM)Phase Wrote: Having it build complex redstone circuitry, that it understands, would be awesome. 

Definitely interesting.

Staff will be opening up discussion on this bot, and future bots for that matter.


RE: Testing Bots on the Build Server - VoltzLive - 09-13-2016

Isn't that what this thread is for?