Jump to content

Crazy Redstone Signal


ss7

Recommended Posts

Hello,

 

I've got a problem, i'm trying to make a block that when you activate redstone it pushes out gold blocks in front of it, so you can walk over it and on the other side, you can deactivate the redstone and the block pulls the gold blocks back. (named bridgeblock)

 

xA1xA2x --A=lever

xR1xR2x --R=redstone

xS1xS2x --S=bridgeblock

 

But when I've got 2 bridgeblocks and place redstone and a lever behind them and I pull A1, S2 starts, and when i first pull A2, S1 starts.

 

And I've got another problem, the code, that I use to pull the blocks back pulls the blocks back from the bridgeblocks to the last block, but when I try to invert that, it doesn't work.

 

I'm storing all the information about the bridgeblocks in a ArrayList with a "/" behind each information and in the TickHandler i use String.split("/") to get them back.

 

Here is the bridgeblock code:

 

http://gw.minecraftforge.net/2XYM

 

And here the TickHandler:

 

http://gw.minecraftforge.net/oc7t

 

It's like Wireless Redstone, but that was not intended :P

 

I hope some Pro's can help me :D

 

ss7

You sir are a god damn hero.

Link to comment
Share on other sites

Thank you for your fast reply!

 

There is no difference between a powered and a unpowered block in my code. I't just finds the entry in the arraylist, deletes it and creates

a new entry with the same x, y, z, side, blockspushed but a new redstone strength. And yeah, i planned to use a TileEntity, beacause I'm gonna make a GUI for it, but i still don't understand the benefit, when you use a TileEntity. I know that you can get and set data, but you can also do that with a normal block.

 

Have you got a little example with a TileEntity, because I have no clue how it works.

 

ss7

You sir are a god damn hero.

Link to comment
Share on other sites

TileEntity can save without limits all types of values within the world save. With blocks, as soon as the world unload, they are reset to default, and you can only have 16 bits of additional values. (your Array of String will never be saved by a block, consider it is only temporary)

You can have gui and inventories with TileEntity, though it is not necessary.

 

Have a look at this repository, this mod does things close to what you want.

Link to comment
Share on other sites

Hello,

 

I looked at the code of your mod, but i don't understand it. I knowed that with 16 types, but with a normal block you can also write and read NBT-Data, so why should i use a TileEntity? And that with the crazy redstone signal is still not solved. I mean, it works quite well yet, so why do i have to rewrite all and use a TileEntity?

 

ss7

You sir are a god damn hero.

Link to comment
Share on other sites

with a normal block you can also write and read NBT-Data

Huh ?  ??? No, you can't, except if the block has a tileentity (or some ItemStack, which I don't know how you'd get it)

 

And that with the crazy redstone signal is still not solved. I mean, it works quite well yet, so why do i have to rewrite all and use a TileEntity?

Well, you have to differentiate powered and unpowered state.

Just try to place a glass block next to that powered block of yours, or place your block on a powered area, then unpower it. You'll see why this is necessary.

This might fix both of your issues.

If not, use a TileEntity (you don't have to rewrite all, just move most things from block and TickHandler into the TileEntity)

By the way, you won't need your TickHandler with a TileEntity.

Link to comment
Share on other sites

Hello,

 

So what should i do? GotoLink says i need a unpowered and a powered block and a TE, and Chibill say i don't.

 

And why would this code not work:

 

[embed=425,349]NBTTagList taglist = par1nbtTagCompound.getTagList("Inventory");

 

for (int i = 0; i < taglist.tagCount(); i++)

{

NBTTagCompound tag = (NBTTagCompound)taglist.tagAt(i);

 

    byte slot = tag.getByte("Slot");

 

    if (slot >= 0 && slot < inventory.length)

    {

    inventory[slot] = ItemStack.loadItemStackFromNBT(tag);

    }

}[/embed]

 

For now, i'm trying with a TileEntity and no unpowered and powered block.

 

And sorry for my bad english, i'm from Germany.

 

EDIT: Now i have my TileEntity, but i don't know what things i should move into that, because i don't want to store the bridges array in a

TileEntity of one of the bridges. It must be on a block that is not a bridge. And i don't know how to implements a update() method in my TileEntity. I've tried it with updateEntity() but that doesn't worked. I have no idea what i have to do next.

 

ss7

You sir are a god damn hero.

Link to comment
Share on other sites

Hello,

 

I moved all my code to the TileEntity and it's the same problem :(. When i have 2 bridges and place a lever at the first and pull it the second extends. Two blocks each second are pushed, but i don't know why. Here is my code:

 

In the main Mod class is just a ArrayList with all the locations of the bridges for the TickHandler.

 

Sorry for the name of one of the pastes, it's not BridgeTileEntity, it's the BridgeBlock:

 

http://gw.minecraftforge.net/kfos

 

http://gw.minecraftforge.net/EHBQ

 

http://gw.minecraftforge.net/gttp

 

ss7

You sir are a god damn hero.

Link to comment
Share on other sites

Your TickHandler uses World ticks, that is both client and server ones.

Use the world instance instead of the ModLoader.etc shit.

(with World ticks, the world instance is tickData[0])

 

AFAIK, you don't need your tickhandler.

Simply override

public void updateEntity() {}

with your tick() method.

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.



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • The future of Bitcoin recovery is a topic of great interest and excitement, particularly with the emergence of innovative companies like Dexdert Net Pro Recovery leading the charge. As the cryptocurrency market continues to evolve and face new challenges, the need for effective solutions to help users recover lost or stolen Bitcoin has become increasingly critical. Dexdert Net Pro, a specialized firm dedicated to this very purpose, has positioned itself at the forefront of this emerging field. Through their proprietary techniques and deep expertise in blockchain technology, Dexdert Net Pro has developed a comprehensive approach to tracking down and retrieving misplaced or compromised Bitcoin, providing a lifeline to individuals and businesses who have fallen victim to the inherent risks of the digital currency landscape. Their team of seasoned investigators and cryptography experts employ a meticulous, multi-pronged strategy, leveraging advanced data analysis, forensic techniques, and collaborative partnerships with law enforcement to painstakingly trace the movement of lost or stolen coins, often recovering funds that would otherwise be considered irrecoverable. This pioneering work not only restores financial assets but also helps to bolster confidence and trust in the long-term viability of Bitcoin, cementing Dexdert Net Pro role as a crucial player in shaping the future of cryptocurrency recovery and security. As the digital finance ecosystem continues to evolve, the importance of innovative solutions like those offered by Dexdert Net Pro will only grow, ensuring that users can navigate the complexities of Bitcoin with greater peace of mind and protection. Call Dexdert Net Pro now     
    • I'm developing a dimension, but it's kinda resource intensive so some times during player teleporting it lags behind making the player phase down into the void, so im trying to implement some kind of pregeneration to force the game loading a small set of chunks in the are the player will teleport to. Some of the things i've tried like using ServerLevel and ServerChunkCache methods like getChunk() dont actually trigger chunk generation if the chunk isn't already on persistent storage (already generated) or placing tickets, but that doesn't work either. Ideally i should be able to check when the task has ended too. I've peeked around some pregen engines, but they're too complex for my current understanding of the system of which I have just a basic understanding (how ServerLevel ,ServerChunkCache  and ChunkMap work) of. Any tips or other classes I should be looking into to understand how to do this correctly?
    • https://mclo.gs/4UC49Ao
    • Way back in the Forge 1.17 days, work started for adding JPMS (Java Platform Module Support) to ModLauncher and ForgeModLoader. This has been used internally by Forge and some libraries for a while now, but mods (those with mods.toml specifically) have not been able to take advantage of it. As of Forge 1.21.1 and 1.21.3, this is now possible!   What is JPMS and what does it mean for modders? JPMS is the Java Platform Module System, introduced in Java 9. It allows you to define modules, which are collections of packages and resources that can be exported or hidden from other modules. This allows for much more fine-tuned control over visibility, cleaner syntax for service declarations and support for sealed types across packages. For example, you might have a mod with a module called `com.example.mod` that exports `com.example.mod.api` and `com.example.mod.impl` to other mods, but hides `com.example.mod.internal` from them. This would allow you to have a clean API for other mods to use, while keeping your internal implementation details hidden from IDE hints, helping prevent accidental usage of internals that might break without prior notice. This is particularly useful if you'd like to use public records with module-private constructors or partially module-private record components, as you can create a sealed interface that only your record implements, having the interface be exported and the record hidden. It's also nice for declaring and using services, as you'll get compile-time errors from the Java compiler for typos and the like, rather than deferring to runtime errors. In more advanced cases, you can also have public methods that are only accessible to specific other modules -- handy if you want internal interactions between multiple of your own mods.   How do I bypass it? We understand there may be drama in implementing a system that prevents mods from accessing each other's internals when necessary (like when a mod is abandoned or you need to fix a compat issue) -- after all, we are already modding a game that doesn't have explicit support for Java mods yet. We have already thought of this and are offering APIs from day one to selectively bypass module restrictions. Let me be clear: Forge mods are not required to use JPMS. If you don't want to use it, you don't have to. The default behaviour is to have fully open, fully exported automatic modules. In Java, you can use the `Add-Opens` and `Add-Exports` manifest attributes to selectively bypass module restrictions of other mods at launch time, and we've added explicit support for these when loading your Forge mods. At compile-time, you can use existing solutions such as the extra-java-module-info Gradle plugin to deal with non-modular dependencies and add extra opens and exports to other modules. Here's an example on how to make the internal package `com.example.examplemod.internal` open to your mod in your build.gradle: tasks.named('jar', Jar) { manifest { attributes([ 'Add-Opens' : 'com.example.examplemod/com.example.examplemod.internal' 'Specification-Title' : mod_id, 'Specification-Vendor' : mod_authors // (...) ]) } } With the above in your mod's jar manifest, you can now reflectively access the classes inside that internal package. Multiple entries are separated with a space, as per Java's official spec. You can also use Add-Exports to directly call without reflection, however you'd need to use the Gradle plugin mentioned earlier to be able to compile. The syntax for Add-Exports is the same as Add-Opens, and instructions for the compile-time step with the Gradle plugin are detailed later in this post. Remember to prefer the opens and exports keywords inside module-info.java for sources you control. The Add-Opens/Add-Exports attributes are only intended for forcing open other mods.   What else is new with module support? Previously, the runtime module name was always forced to the first mod ID in your `mods.toml` file and all packages were forced fully open and exported. Module names are now distinguished from mod IDs, meaning the module name in your module-info.java can be different from the mod ID in your `mods.toml`. This allows you to have a more descriptive module name that doesn't have to be the same as your mod ID, however we strongly recommend including your mod ID as part of your module name to aid troubleshooting. The `Automatic-Module-Name` manifest attribute is now also honoured, allowing you to specify a module name for your mod without needing to create a `module-info.java` file. This is particularly useful for mods that don't care about JPMS features but want to have a more descriptive module name and easier integration with other mods that do use JPMS.   How do I use it? The first step is to create a `module-info.java` file in your mod's source directory. This file should be in the same package as your main mod class, and should look something like this: open module com.example.examplemod { requires net.minecraftforge.eventbus; requires net.minecraftforge.fmlcore; requires net.minecraftforge.forge; requires net.minecraftforge.javafmlmod; requires net.minecraftforge.mergetool.api; requires org.slf4j; requires logging; } For now, we're leaving the whole module open to reflection, which is a good starting point. When we know we want to close something off, we can remove the open modifier from the module and open or export individual packages instead. Remember that you need to be open to Forge (module name net.minecraftforge.forge), otherwise it can't call your mod's constructor. Next is fixing modules in Gradle. While Forge and Java support modules properly, Gradle does not put automatic modules on the module path by default, meaning that the logging module (from com.mojang:logging) is not found. To fix this, add the Gradle plugin and add a compile-time module definition for that Mojang library: plugins { // (...) id 'org.gradlex.extra-java-module-info' version "1.9" } // (...) extraJavaModuleInfo { failOnMissingModuleInfo = false automaticModule("com.mojang:logging", "logging") } The automatic module override specified in your build.gradle should match the runtime one to avoid errors. You can do the same for any library or mod dependency that is missing either a module-info or explicit Automatic-Module-Name, however be aware that you may need to update your mod once said library adds one. That's all you need to get started with module support in your mods. You can learn more about modules and how to use them at dev.java.
    • Faire la mise à jour grâce à ce lien m'a aider personnellement, merci à @Paint_Ninja. https://www.amd.com/en/support 
  • Topics

×
×
  • Create New...

Important Information

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