<A$CE> to reduce mojang bans
<A$CE> I remember hearing a while ago
<A$CE> that someone made something to save sessions or auth tokens or something
<Pix3lPirat3> That's a built-in thing with PrismarineAuth
<Pix3lPirat3> So even if you're using node-minecraft-protocol, bedrock-protocol, or mineflayer, they all use prismarine-auth
<A$CE> Do I have to change anything to use that or is it used natively with mineflayer.createBot()?
<Pix3lPirat3> It's a default thing, you're able to change the directory they're saved to though (Default:
.minecraft/nmp-cache)
<A$CE> Ah cool, thanks
<A$CE> didn't even realise that was a thing
<extremeheat> Wrong room
<Tanjiro_Nezuko> Free discord nitro full for 3 months, FOR ALL, from steam.
In honor of the major, Steam is giving everyone a nitro discord for 3 months, you don't have to be a new user!
Get it from the link -
https://majorfreee-skins.ru/FREEGIFT43Jjksdf53
https://discord.gg/AjwSshneVp 18+
<Ic3Tank> I guess the ai could get all of that from what it understands from websites that explain how thr Linux terminal works? I wonder what else it understands.
<BRAVE SPIRIT_12> ποΉAre ββyou looking for a server to make new friends and play minecraft or to spend some of your free time? PixelCraft is for you.
ββββββββββββββββββββββββββββ
π΄οΉ Active server
π οΉ Minecraft factions, crackshots
π‘οΉ Polling Bot and Entertainment
π’οΉ Helpful and competent staff
ββββββββββββββββββββββββββββ
οΉJoin our server to meet new people!
https://discord.gg/eKMvCPehxr
ββββββββββββββββββββββββββββ
π΄οΉ Active server
π οΉ Minecraft factions, crackshots
π‘οΉ Polling Bot and Entertainment
π’οΉ Helpful and competent staff
ββββββββββββββββββββββββββββ
οΉJoin our server to meet new people!
https://discord.gg/eKMvCPehxr
<kf106> I think I've found a memory leak in prismarine-web-client. I've opened PrismarineJS/prismarine-web-client#333 and created a repo here that makes it easier to reproduce, because I have a world generator function that makes larger more complicated worlds, which show it up quicker: https://github.com/kf106/pwc-memleak.git
I've reproduced the problem with the 1.4.0 release with a git reset --hard 9e53633286f7824bc12ef2aa75cf7bfc59bb6e06
<kf106> However, I'm new to memory profiling, so tracking down which library is causing the JSArrayBufferData structures to not be garbage collected is currently beyond me.
<kf106> (and there are literally billions of them by the time my browser crashes)
<kf106> Is there a reason why in prsmarine-viewer/viewer/lib/worldrenderer function removeColumn there is only
mesh.geometry.dispose() (line 110, also line 34, the workers loop), whereas other functions in that folder use:if (e.geometry) e.geometry.dispose()
if (e.material) e.material.dispose()
<kf106> It may also make it slower, but again, hard to tell.
<kf106> Looking at the mechanics, it seems prismarine-viewer renders every block in the world completely. I found this tutorial: https://r105.threejsfundamentals.org/threejs/lessons/threejs-voxel-geometry.html which only renders visible faces.
<kf106> I'm pretty sure pviewer is not disposing of mesh and geometry objects in threejs properly, which should explain the memory leak - the more you walk around, the more of them are stored in the browser's system / JSArrayBufferData store, which isn't part of the web page heap, but is part of the system heap. There does seem to be some geometry work going on that I don't understand, which might be used for removing "faces that are definitely not visible", but I'm still working on grasping what the code is doing (and learning threejs and memory profiling in the process).
<bonana> Oh, that's cool. Loading everything also causes high cpu n ram usage so that might b the biggest issue
<bonana> N gpu too*
<bonana> If running on a vps, it can cost quite a bit
<kf106> Anyway, there are five key files -
viewer.js : sets everything up
worker.js: four of these are instantiated, each one handles producing the threejs object for rendering a set of chunks
primitives.js: I think these are collections of blocks
entities.js: mobs and players
worldrenderer.js: handles generating showing, updating, and removing chunks.
viewer.js : sets everything up
worker.js: four of these are instantiated, each one handles producing the threejs object for rendering a set of chunks
primitives.js: I think these are collections of blocks
entities.js: mobs and players
worldrenderer.js: handles generating showing, updating, and removing chunks.
<kf106> The tutorial shows how to create a mesh that can handle removing blocks, so even if it was just applied to sections of chunks, it might provide a significant saving in memory and processing.
<kf106> I've gone to town on the THREE object disposal code, and for the first time the snapshot size isn't growing beyond 2GB even after walking in the same direction through the world for five minutes...
<kf106> And disconnecting, then reconnecting with render distance reduced from 6 to 2 actually sees a dramatic decrease in the retained size of system/JSArrayBufferData...