Big prismarineJS projects

[rom1504]

This issue will serve as room to discuss big projects
see https://github.com/PrismarineJS/mineflayer/wiki/Big-Prismarine-projects

[Karang]

A lot of them can be closed. I can make a list if you want (or directly close them).

[rom1504]

okay, go ahead and close what you think can be closed, it can always be reopened if needed

[rom1504]

I think what might be interesting is using milestone or project features of github to :

• provide guidance on what needs doing for new version support
• provide ideas on what to work on for people that want to contribute
• promote the most important issues to fix

[rom1504]

I marked a few issues I consider to be high priority https://github.com/PrismarineJS/mineflayer/issues?q=is%3Aissue+is%3Aopen+label%3A%22high+priority%22

everything else is low priority TBH

[rom1504]

started a project there https://github.com/orgs/PrismarineJS/projects/9 with important issues
only a beginning though
it would be useful to write a guide with all the different kind of stuff (low level, high level, AI level, server, client, optimization, ..) that would be useful

[rom1504]

Quick version of that guide (would need to be put somewhere else) :

1. optimization

• protodef can be optimized up to 100x improve nmp perf by using a protodef compiler node-minecraft-protocol#711

2. visualization

• displaying the world of the bot/server in a browser would be amazing Implement a prismarine-world web visualizer prismarine-world#17
• related Move the whole world state to prismarine-world for better packaging #334

3. easier maintenance

• better procedure to update mcdata, see Write guide on how to provide data for new versions minecraft-data#283

4. more protocol support

• bedrock is the future of minecraft, let's have support for it nmp/protodef support for mcpe node-minecraft-protocol#235

5. more doc => more users and less questions

• we need tutorials for mineflayer Write good introduction tutorials for mineflayer #908

[rom1504]

tracking at https://github.com/orgs/PrismarineJS/projects/9

[rom1504]

https://github.com/PrismarineJS/mineflayer/wiki/Big-Prismarine-projects

[rom1504]

this issue will serve as discussion room for big projects planning

[Karang]

About visualization, one possible direction is to save a file compatible with https://github.com/ReplayMod/ReplayMod
As far as I understand, it records the packets to a file so it shouldn't be hard to do with a mineflayer plugin. The mod then allow to load the replay and explore it in spectate or in first person, generate videos and even display custom objects (paths).

[rom1504]

Yeah that's an interesting idea.
I still think that having a js viewer unlocks more things, but being able to view stuff directly in the vanilla client is indeed quite nice.

[rom1504]

New one:

12:00 | <rom1504> | I tried tooling the vanilla client at some point to do some automated testing with it
-- | -- | --
12:00 | <jvyden420> | it didn't go very well, did it?
12:01 | <rom1504> | https://github.com/PrismarineJS/node-minecraft-wrap/pull/18 still there
12:01 | <rom1504> | Just didn't finish
12:01 | <rom1504> | I have a launched in js and everything for it
12:02 | <rom1504> | +robotjs to click on stuff
12:02 | <rom1504> | What was missing is virtual x server
12:02 | <rom1504> | Was not available in circle ci
12:02 | <jvyden420> | interesting
12:02 | <rom1504> | This should be easier in GitHub action now
12:04 | <rom1504> | Would definitely be cool to finish this thing
12:04 | <rom1504> | Possible applications :
12:04 | <rom1504> | * macro-style bots
12:05 | <rom1504> | * auto testing for flying-squid
12:05 | <rom1504> | * dumping automatically client bound and server bound packets using a vanilla server and client and an nmp proxy
12:06 | <rom1504> | * automatically getting behavior information from the client and server interacting with each other, like physics constants
12:07 | <rom1504> | I guess I'll add that in one of the interesting project to work on in PrismarineJS org

[rom1504]

Will add it properly to the page later