Both the vanilla bed and the opaque glass seem to be resource pack side issues - will try to take a look as soon as I get a chance.
1.12.2 Bug Report Thread
- Thread starter geeberry
- Start date
-
The Spring 2023 edition of The Rookery is now out! Take a look to see the latest builds, guides, progress and development updates on the upcoming 1.18.2 switch. You can read it here:
https://indd.adobe.com/view/f943da18-ed77-4d55-845d-fee9bfa14247
Mike specifically removed Liteloader since it has a high memory cost.
Hopefully it still works, though, as the current macro mod is pretty limited compared to the liteloader one.
Hopefully it still works, though, as the current macro mod is pretty limited compared to the liteloader one.
Yeah - you should be able to install liteloader yourself I think? It was adding an additional like 1MB to 2MB memory required to load the same for a single mod...
Also, for those missing Waila (the mod that showed more information of a block) give this offshoot a try
And let me know if it works
Also, for those missing Waila (the mod that showed more information of a block) give this offshoot a try
And let me know if it works
Ah, yeah I tried running the 1.12.2 version but the launcher freezes on 100% without loading the game.
LiteLoader - A Lightweight Mod System for Minecraft
LiteLoader is a lightweight mod system designed to provide simple loader functionality for client-side mods which don't need to modify game mechanics.
Ah, yeah I tried running the 1.12.2 version but the launcher freezes on 100% without loading the game.
LiteLoader - A Lightweight Mod System for Minecraft
LiteLoader is a lightweight mod system designed to provide simple loader functionality for client-side mods which don't need to modify game mechanics.www.liteloader.com
Increase the memory in the launcher
I tried a different computer, going from 5GB to 24GB memory allocated, with the same result unfortunately. I can try copying out the console/log if that helps.
That Waila is helpful for at least showing the block names (which /br info doesn't reveal), though the block Id/meta data is a bit garbled. Thanks though.
Installing Liteloader and Macro+Keybind mod just worked fine for me.
Did you perhaps put the Liteloader installer jar in the mods folder? You need to execute the installer, click the "extract liteloader" option, and extract it to your mods folder instead.
Also, is it possible for Liteloader and Macro+Keybind mods to be "optional" mods in the launcher that are disabled by default, like WE CUI?
Did you perhaps put the Liteloader installer jar in the mods folder? You need to execute the installer, click the "extract liteloader" option, and extract it to your mods folder instead.
Also, is it possible for Liteloader and Macro+Keybind mods to be "optional" mods in the launcher that are disabled by default, like WE CUI?
Yeah I extracted it, I’ll try again with a clean install or something, how much memory have you got allocated?
Eventually got it working, disabling Dynamic Surrounds did the trick, not ideal but better than nothing
Antony
Printmaker
Apparently, when I shoot arrows, my arrows despawn immediately, exactly how it happens to nobuilds when they shoot arrows.
Same goes to splash potions
Same goes to splash potions
Last edited:
Margaery_Tyrell
The Dark Lord Sauron
Noticed an issue with schemsets
I do /schbr &PoplarM and &AspenM and trees are not placed unless I'm actively clicking the block its supposed to go on instead of being able to do so from a distance, meaning that it can spawn 2-4 trees per spot.
I do /schbr &PoplarM and &AspenM and trees are not placed unless I'm actively clicking the block its supposed to go on instead of being able to do so from a distance, meaning that it can spawn 2-4 trees per spot.
Yeah I’m not sure if this is tied to the other bug we’re seeing with WE where the brushes now have a really short right click range - when I tried the Schem Brush earlier I wasn’t able to left click at a bigger range either.
First step might be to see if we can adjust the default WE brush range on the plugin end, then we can setup a taskforce to fix the underlying offset issues with the various Schem sets we’ve been seeing lately.
I found a minor bug with horse spawns that might be an issue down the line if too many people do this. If you spawn a horse, get off of it, warp to a place outside of the main map, e.g. spawn, and then warp /back, your horse will still be there, but spawning another one will not cause the first one to despawn. I even logged off the server and got back on, returning to the spot I was in, and that first horse was still there.
Not saying it wouldn't be hilarious for the entire server to be colonized by horses and for them to start tearing it all down and building a horse-based society, though.
Not saying it wouldn't be hilarious for the entire server to be colonized by horses and for them to start tearing it all down and building a horse-based society, though.
Antony
Printmaker
Thats why we kill them after using them
Margaery_Tyrell
The Dark Lord Sauron
A minor resource pack issue, Idk when it happened but retexturing zombies as Wights causes a lot of issues with builds like for example Kings Landing where their heads are used for heads on spikes and have turned from dead criminals and traitors to the frozen over heads of wights.
I noticed a similar retexture with skulls which aren't as big of a change, but I did prefer the coloring of the other skull to this one
I noticed a similar retexture with skulls which aren't as big of a change, but I did prefer the coloring of the other skull to this one
Adorkabley
Royal Messenger
- Pronouns
- she/her
Guests don't have perms to kill things.