Official Everybody Edits Forums

abrar11 wrote:

Koya wrote:

abrar11 wrote:

Koya wrote:

I asked Player.IO if they had a timeline for if a full Javascript port is available

So once that is sorted making online bots will be a doddle.

https://github.com/Yonom/playerio.js
For now you can use this (I believe it works)

You can make a basic web based bot which logs in, can log out, and can send different messages to the bot(for example place block, send message etc) from the web page & can receive messages from js to the web page (for example the chat so you can see the ee chat from the web page you've made).

<Proc> playerio.js works a bit
<Proc> it can connect to worlds

Would be interested in the full version

I would try some things with it, but it's not working for me currently but from what I see, it does most basic things though from what I can read, what were you looking for in it? also indeed, a full version would be amazing for web based!, also with playerio.js you can send most functions with connection.send etc, you could most likely make a temp web bot, and switch when anything is out/updated

Creating bots with node.js and app.js means that people running Windows, MacOS or Linux can run it with no issues.
Also node bots make more sense than working with mono all the time, easier to bridge the gap between a webpage and a bot.

I asked Player.IO if they had a timeline for if a full Javascript port is available

Chris D wrote:

We're not making any commitments to timelines. We expect that it will be done this year, but again, we're not making any promises :-)

So once that is sorted making online bots will be a doddle.

abrar11 wrote:

I would be interested in helping however I'm not too sure I'd be a good contribution

It would be nice to have a web developer helping out, as the original plans were to make an online archive, similar to the Wayback Machine (web.archive.org).
Furthering that, it would be most useful to have a web interface for viewing (possibly modifying) worlds; accessibility is a large, often overlooked, aspect.

Some things that you'd require:
A VPS.
     Should require at least 100 MB RAM to run the base, but this can quickly increase depending on the popularity.
A website.
     Could be run on above mentioned VPS, but what framework will be used? PHP or ASP? (Won't go in detail why one or the other).
A place to store files (the "snippets" saved by players, the whole concept of this system).
     Again could be placed on the VPS, but could also be done on an external service like Dropbox, Google Drive or One Drive.
A bot to read rooms (optionally at given dimensions).
     Easy enough to make, might be a bit harder since it has to communicate with above services, but it's nothing too hard.
A bot to reading specified saved room/snippet and placing it.
     Again should be easy enough but is a bit harder due to web communications. The idea where you can have a "toolbar" where several different blocks will each create their own snippet really isn't that hard either.

Now you could do it with just the website and file service, but PHP and ASP are server-sided, so that certainly won't work. So there HAS to be a port to javascript (which would be increasingly easy once the game has been ported to Unity) so the bot basically runs from your own browser tab.
Now I'm not sure if there's actually said port to language, but I do know there are ~2-3 people (donno who though) here that have made a bot from pure sockets (so no PlayerIO used).
It TECHNICALLY could also be made a mobile app (PlayerIO has SDK's for android and IOS), but I doubt anybody is willing to do that.

Might as well post an updated picture.

EDIT: Holy crap that resolution was high. I'm just going to post a hyperlink for now: http://i.imgur.com/z1qfQKU.jpg