Jump to content

Redstone timing / loop issues.


keybounce

Recommended Posts

I have a redstone loop that behaves badly in Forge.

 

You can see this loop setup, in 12w27a, here:

 

Short summary: It is a 14 tick loop, 3x4 for repeaters, and 2 for torches. Ideal behavior is 9 ticks on, 5 ticks off (9 ticks on from a button).

 

Since 12w30c (?), I have only seen it show either the 9/5 or the 8/6 state (in the video, when I'm mentioning that the timing of the notes is now different). I have never seen the lockup state in 1.3.2 vanilla.

 

I just (two days ago) saw it lock up in 1.3.2 + forge.

 

If it makes a difference, this is full multiplayer server.

 

I will do more testing in 1.3.2 vanilla; as I said, I have not seen this happen there yet.

Jeb! The sheep! The fence pens, they do nothing still leak!

Link to comment
Share on other sites

There are a lot of things that could cause MC timing to get screwed up, namely just pure lag.

If the server can't keep up with the updates, especially across chunk boundaries.

This isn't so much a Forge bug as a MC.. quirk...

It is rather difficult to track down, or to counteract these quirks.

Its something that you need to take into account in your designs.

 

I do Forge for free, however the servers to run it arn't free, so anything is appreciated.
Consider supporting the team on Patreon

Link to comment
Share on other sites

... And I finally managed to make it happen in vanilla 1.3.2, so it is not forge at all. Reporting at the MC site.

 

(What happens? Well, the button is supposed to put 9 ticks of "on" state into the loop, and it is supposed to take 14 ticks to go around the loop. Instead, that 9 ticks of "on" extends to all 14 ticks of the loop, and the side with the doorbell button is always on, like if you pressed the button twice.)

 

As for lag/chunk issues: This time the testing was with only one person on the server, standing still, right in front of it. Technically it's an adjacent chunk, but no chunks were being loaded/unloaded.

 

===

 

Lex, do you (or anyone) have ideas on how to make things like this work properly? Any way to design around MC's "quirks"?

 

I want to play with long distance instant wire, but the "best"/cheapest way I've seen for that involves pulse transmitters, and a decoder/counter at the far end. If this is messing up, I can only imagine how that will mess up ...

 

(The pulse transmitters I'm not that worried about; BUDs making a piston retract is pretty stable. The question of distance, unloaded chunk signal propagation, and then just the tracking at the other end ...)

 

Jeb! The sheep! The fence pens, they do nothing still leak!

Link to comment
Share on other sites

Tee hee.

 

Because I want my overworld to function in vanilla.

Anything goes in the ages, but the overworld has to function if loaded in vanilla.

 

And, you're not the first person to recommend Redpower.

I had issues with it and 125 when playing on someone else's server, and there's the whole issue of marble generation in Mystcraft.

Jeb! The sheep! The fence pens, they do nothing still leak!

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Announcements



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • They were already updated, and just to double check I even did a cleanup and fresh update from that same page. I'm quite sure drivers are not the problem here. 
    • i tried downloading the drivers but it says no AMD graphics hardware has been detected    
    • Update your AMD/ATI drivers - get the drivers from their website - do not update via system  
    • As the title says i keep on crashing on forge 1.20.1 even without any mods downloaded, i have the latest drivers (nvidia) and vanilla minecraft works perfectly fine for me logs: https://pastebin.com/5UR01yG9
    • Hello everyone, I'm making this post to seek help for my modded block, It's a special block called FrozenBlock supposed to take the place of an old block, then after a set amount of ticks, it's supposed to revert its Block State, Entity, data... to the old block like this :  The problem I have is that the system breaks when handling multi blocks (I tried some fix but none of them worked) :  The bug I have identified is that the function "setOldBlockFields" in the item's "setFrozenBlock" function gets called once for the 1st block of multiblock getting frozen (as it should), but gets called a second time BEFORE creating the first FrozenBlock with the data of the 1st block, hence giving the same data to the two FrozenBlock :   Old Block Fields set BlockState : Block{minecraft:black_bed}[facing=east,occupied=false,part=head] BlockEntity : net.minecraft.world.level.block.entity.BedBlockEntity@73681674 BlockEntityData : id:"minecraft:bed",x:3,y:-60,z:-6} Old Block Fields set BlockState : Block{minecraft:black_bed}[facing=east,occupied=false,part=foot] BlockEntity : net.minecraft.world.level.block.entity.BedBlockEntity@6d1aa3da BlockEntityData : {id:"minecraft:bed",x:2,y:-60,z:-6} Frozen Block Entity set BlockState : Block{minecraft:black_bed}[facing=east,occupied=false,part=foot] BlockPos{x=3, y=-60, z=-6} BlockEntity : net.minecraft.world.level.block.entity.BedBlockEntity@6d1aa3da BlockEntityData : {id:"minecraft:bed",x:2,y:-60,z:-6} Frozen Block Entity set BlockState : Block{minecraft:black_bed}[facing=east,occupied=false,part=foot] BlockPos{x=2, y=-60, z=-6} BlockEntity : net.minecraft.world.level.block.entity.BedBlockEntity@6d1aa3da BlockEntityData : {id:"minecraft:bed",x:2,y:-60,z:-6} here is the code inside my custom "freeze" item :    @Override     public @NotNull InteractionResult useOn(@NotNull UseOnContext pContext) {         if (!pContext.getLevel().isClientSide() && pContext.getHand() == InteractionHand.MAIN_HAND) {             BlockPos blockPos = pContext.getClickedPos();             BlockPos secondBlockPos = getMultiblockPos(blockPos, pContext.getLevel().getBlockState(blockPos));             if (secondBlockPos != null) {                 createFrozenBlock(pContext, secondBlockPos);             }             createFrozenBlock(pContext, blockPos);             return InteractionResult.SUCCESS;         }         return super.useOn(pContext);     }     public static void createFrozenBlock(UseOnContext pContext, BlockPos blockPos) {         BlockState oldState = pContext.getLevel().getBlockState(blockPos);         BlockEntity oldBlockEntity = oldState.hasBlockEntity() ? pContext.getLevel().getBlockEntity(blockPos) : null;         CompoundTag oldBlockEntityData = oldState.hasBlockEntity() ? oldBlockEntity.serializeNBT() : null;         if (oldBlockEntity != null) {             pContext.getLevel().removeBlockEntity(blockPos);         }         BlockState FrozenBlock = setFrozenBlock(oldState, oldBlockEntity, oldBlockEntityData);         pContext.getLevel().setBlockAndUpdate(blockPos, FrozenBlock);     }     public static BlockState setFrozenBlock(BlockState blockState, @Nullable BlockEntity blockEntity, @Nullable CompoundTag blockEntityData) {         BlockState FrozenBlock = BlockRegister.FROZEN_BLOCK.get().defaultBlockState();         ((FrozenBlock) FrozenBlock.getBlock()).setOldBlockFields(blockState, blockEntity, blockEntityData);         return FrozenBlock;     }  
  • Topics

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.