MiscPeripherals isn't available for 1.6+, I don't think it's 1.5+ actually
Ask a simple question, get a simple answer
- Thread starter HeffronCM
- Start date
-
The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
Gravel falling in Beyond Reality seems weird to me:
Sometimes the gravel falls normally just like in vanilla.
Sometimes it falls instantly, i.e. as soon as you mine the block below it the gravel takes its place. Also you can't place a torch to harvest it when it falls this way.
It's kinda random, sometimes it behaves normally, sometimes instantly. Does anyone have an explanation?
Sometimes the gravel falls normally just like in vanilla.
Sometimes it falls instantly, i.e. as soon as you mine the block below it the gravel takes its place. Also you can't place a torch to harvest it when it falls this way.
It's kinda random, sometimes it behaves normally, sometimes instantly. Does anyone have an explanation?
lagGravel falling in Beyond Reality seems weird to me:
Sometimes the gravel falls normally just like in vanilla.
Sometimes it falls instantly, i.e. as soon as you mine the block below it the gravel takes its place. Also you can't place a torch to harvest it when it falls this way.
It's kinda random, sometimes it behaves normally, sometimes instantly. Does anyone have an explanation?
I don't think so. I'm in singleplayer and the gravel block instantly takes the space of the mined block. It would be different if it was lag.
The lag could be the opposite way, making it look like the gravel's falling normally when it's supposed to be sped up.I don't think so. I'm in singleplayer and the gravel block instantly takes the space of the mined block. It would be different if it was lag.
Or rather, the opposite way. It could be serverside lag when the world saves and you get that lagspike of doom. It wouldn't affect much in the way of FPS if you had a really beefy computer. And once again, yes. You can have serverside lag on singleplayer worlds. Yes, it's terrible.The lag could be the opposite way, making it look like the gravel's falling normally when it's supposed to be sped up.
I know that. But that can't be it since I don't have any noticeable delay.And once again, yes. You can have serverside lag on singleplayer worlds. Yes, it's terrible.
I have to do a bit more testing with this. I doesn't feel like lag.
In 1.7? You do not use MCEdit... unless you are expecting people to use that exact same world, all the time.BTW how do we use Mcedit without the insane lag that pops up
Other than that, lower render distance, that's all I can suggest. MCEdit is laggy at the best of times.
What do you mean?In 1.7? You do not use MCEdit... unless you are expecting people to use that exact same world, all the time.
I don't think so because any mob with a boss tag is autoblacklisted from the Auto SpawnerIs there anyway to get the King Slime to play nice with MFR Autospawner in DW20 1.7.10?
MCEdit works by using block IDs. Which are all static for vanilla blocks, however modded block IDs change between world. So in world 1 ID 425 may be a block of steel, but in world 2 it could be a manasteel blockWhat do you mean?
I see. But non-vanilla blocks are displayed as "future blocks" anyway and MCEdit doesn't change them. One can still use MCEdit to e.g. remove a crashing block.MCEdit works by using block IDs. Which are all static for vanilla blocks, however modded block IDs change between world. So in world 1 ID 425 may be a block of steel, but in world 2 it could be a manasteel block
Of course you shouldn't transfer chunks from one world to another.
Yes, you can always use it delete something. But when someone mentions MCEdit I assume they are using it for map making, and that is risky if they are doing a schematic world (1 void world with all the building schematics they want) and they then try to use the schematics in a different world = bad timeI see. But non-vanilla blocks are displayed as "future blocks" anyway and MCEdit doesn't change them. One can still use MCEdit to e.g. remove a crashing block.
Of course you shouldn't transfer chunks from one world to another.
Or so it uses the IDs... so instead of 1 it uses <minecraft:stone>someone should update MCEdit to use the ID table per world and allow migrations
You need to pass the ID table with any schematics with mod blocks anyway
The only reason the thing still works is because vanilla IDs got harcoded
The only reason the thing still works is because vanilla IDs got harcoded
There is a mod called "YouShallNotStack" that allows you to change stack sizes.
Do you happen to have a link? I'm actually getting zero results when searching for it. Thanks! It looks like it would be exactly what I want, hopefully I can find it.