<Ic3Tank> But flying-squid is still very limited. And for more in depth testing vanilla servers are used.
<Ic3Tank> There is even a project node-mincraft-wrap that provides easy access to launching minecraft instances or servers with node.js
<Saiv46> Hello there, I was been missing here for while
<Darvin> I really love that idea of a lightweight vanilla node server and appreciate everyone working on it
<Darvin> There a a few chunks that does not load or unload immediatly if you dont look at them directly, just look at my video
<Darvin> Video is taken from a 1.16 localhost server but i had the same errors on https://flying-squid.host/
<Saiv46> Yeah, it just chunks being corrupted
<Saiv46> And main problem with flying-squid is because nobody really understand how it works.
<Saiv46> I mean - it's working and it's better to not break anything.
<Darvin> What do you mean exaclty?
<Darvin> Iam reading and trying to understand its code since a few days yet but i still need veryy loonngg time before i can contribute 😄
<Saiv46> I mean - everything about flying-squid:
- Behaviours (being removed)
- Core plugins
- More built-in plugins
<Darvin> Why does no one understand it? I think its very well documentated
<Saiv46> Yeah, modular architecture is great, but it have some drawbacks.
<Darvin> I think flying-squid needs way more devs working on it, i personally love the concept
<Darvin> what are some drawbacks for example?
<LabGuy94> ```
const mcServer = require('flying-squid')
mcServer.createMCServer({
'motd': 'A Minecraft Server \nRunning flying-squid',
'port': 25565,
'max-players': 10,
'online-mode': true,
'logging': true,
'gameMode': 1,
'difficulty': 1,
'worldFolder':'world',
'generation': {
'name': 'diamond_square',
'options':{
'worldHeight': 80
}
},
'kickTimeout': 10000,
'plugins': {
},
'modpe': false,
'view-distance': 10,
'player-list-text': {
'header':'Flying squid',
'footer':'Test server'
},
'everybody-op': true,
'max-entities': 100,
'version': '1.16.5'
})
```
https://cdn.discordapp.com/attachments/413438265475989534/891546154012143678/unknown.png
<DrunkMoon> Failed tests, but runs on my machine
<Ic3Tank> When does the client consider being spawned in a world? The minecraft-protocol example spawns you in a world with blocks health and all. But if a mineflayer bot joins the example server it does not emit the spawn event. It seams mineflayer emits the spawn event after it receives a update_health packet. Is that correct? Should it not maybe listen for a map packet instead?
<deandre> oh 1.16.1
<deandre> my bad
<deandre> whats with the arrows
<Saiv46 (flying-squid.host op)> Yep, 1.16.5+ is still not supported properly
<deandre> i was on 1.8.9
<Saiv46 (flying-squid.host op)> That's a known bug, where player spawns arrow instead of item
<Saiv46 (flying-squid.host op)> Idk how to fix that, so I'll just rewrite whole server.
<Saiv46 (flying-squid.host op)> Project called
disco-dragon
<deandre> is it possible to make water work properly
<Saiv46 (flying-squid.host op)> That's possible, but nobody will ever do that
<deandre> could it be done using plugins
<deandre> to at least add the physics when swimming
<Saiv46 (flying-squid.host op)> Actually physics is only client-side
<Saiv46 (flying-squid.host op)> Server needs only to send packets when player is in water