Everything posted by mgen256
-
[1.21]The behavior of the search bar in CreativeModeTab is unusual
When I add a search bar to CreativeModeTab, the text box is not rendered even though it's possible to input text. Additionally, the search is performed on all items. This issue has been occurring since 1.21. Is there something missing in my code? https://github.com/mgen256/AdditionalLights/blob/1.21/src/main/java/com/mgen256/al/AdditionalLights.java
-
[1.20.6]Crash During Mod Loading
The issue was resolved by doing the following: Upgraded Forge from 50.0.0 to 50.0.9 Added reobf = false to build.gradle
-
[1.20.6]Crash During Mod Loading
The issue occurs here: CREATIVE_MODE_TABS = DeferredRegister.create(Registries.CREATIVE_MODE_TAB, MOD_ID); Exception message: java.lang.NoSuchFieldError: Class net.minecraft.core.registries.Registries does not have member field 'net.minecraft.resources.ResourceKey f_279569_' The mod loads and operates without any issues during debugging in the development environment. However, it crashes when loading the mod through the official Minecraft launcher. This problem did not occur in versions 1.20.1 or 1.20.4. How can I resolve this error?
-
Error in VS Code after upgrading to 1.17
I may have simply needed to update the import. Sorry about that.
-
Error in VS Code after upgrading to 1.17
I'm using forge-1.17.1-37.0.15-mdk, and the empty project starts without any problems. I have no idea where the problem lies.
-
Error in VS Code after upgrading to 1.17
It happens with Language Support for Java. Because of this error, my code will not be able to resolve the reference. Please help me. Error Messages: ---------------------------------- [Warn - 9:37:53] 2021/08/01 9:37:53 While loading class "org.eclipse.buildship.core.internal.util.gradle.PublishedGradleVersions$LookupStrategy", thread "Thread[Worker-1: Loading available Gradle versions,5,main]" timed out waiting (30035ms) for thread "Thread[pool-2-thread-1,5,main]" to finish starting bundle "org.eclipse.buildship.core_3.1.5.v20210112-1646-s [14]". To avoid deadlock, thread "Thread[Worker-1: Loading available Gradle versions,5,main]" is proceeding but "org.eclipse.buildship.core.internal.util.gradle.PublishedGradleVersions$LookupStrategy" may not be fully initialized. Unable to acquire the state change lock for the module: osgi.identity; type="osgi.bundle"; version:Version="3.1.5.v20210112-1646-s"; osgi.identity="org.eclipse.buildship.core"; singleton:="true" [id=14] STARTED [STARTED] org.osgi.framework.BundleException: Unable to acquire the state change lock for the module: osgi.identity; type="osgi.bundle"; version:Version="3.1.5.v20210112-1646-s"; osgi.identity="org.eclipse.buildship.core"; singleton:="true" [id=14] STARTED [STARTED] at org.eclipse.osgi.container.Module.lockStateChange(Module.java:350) at org.eclipse.osgi.container.Module.start(Module.java:419) at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:511) at org.eclipse.osgi.internal.hooks.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:117) at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClass(ClasspathManager.java:572) at org.eclipse.osgi.internal.loader.ModuleClassLoader.findLocalClass(ModuleClassLoader.java:345) at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:401) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:480) at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:170) at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:519) at org.eclipse.buildship.core.internal.util.gradle.PublishedGradleVersionsWrapper$LoadVersionsJob.run(PublishedGradleVersionsWrapper.java:60) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63) Caused by: java.util.concurrent.TimeoutException: Timeout after waiting 30 seconds to acquire the lock. at org.eclipse.osgi.container.Module.lockStateChange(Module.java:347) ... 11 more Caused by: org.eclipse.osgi.framework.util.ThreadInfoReport: Thread dump ... ----------------------------------
-
[1.16.1] Mob can't climb on my block
I have resolved. I just had to insert the following code in my block. @Override public boolean allowsMovement(BlockState state, IBlockReader worldIn, BlockPos pos, PathType type) { return false; }
-
[1.16.1] Mob can't climb on my block
Does anyone know?
-
[1.16.1] Mob can't climb on my block
They will not climb if the collision shape is smaller than the Full Cube. I tried this. private static final VoxelShape COLLISION_SHAPE = Block.makeCuboidShape(0, 0, 0, 14, 14, 14); @Override public VoxelShape getCollisionShape(BlockState state, IBlockReader worldIn, BlockPos pos, ISelectionContext context) { return COLLISION_SHAPE; } A low value like (0,0,0,6,6,6) seems fine. But because it's lower than the model's height, the mob's legs above it are buried. Looking at other mods, there were some that could climb and some that could not, and the cause could not be identified. I tried putting the same value but it didn't work for my mod. Can you think of anything that might have caused it?
-
[1.16.1] Mob can't climb on my block
Do you understand the cause?
-
[1.16.1] Mob can't climb on my block
Thank you !! Will be very studying.
-
[1.16.1] Mob can't climb on my block
I'm sorry for the late reply. I need help. This is the complete source code page. https://github.com/mgen256/AdditionalLights/tree/1.16.1 Direct download https://github.com/mgen256/AdditionalLights/archive/1.16.1.zip I'm not very familiar with github. Please let me know if there are any missing items.
-
[1.16.1] Mob can't climb on my block
I'm sorry, I don't know what you're saying. My source code should be available from the URL. Need to do something?
-
[1.16.1] Mob can't climb on my block
I don't know where is the problem in my code. I couldn't find any difference with other vanilla blocks. Here is the code. https://github.com/mgen256/AdditionalLights/blob/1.16.1/src/main/java/com/mgen256/al/blocks/StandingTorch_S.java I confirmed that it works by returning VoxelShapes.fullCube() in getShape(). Please tell me.
-
[1.16.1]How to scare mobs
You are wonderful to come up with the latter method. However, both methods are hesitant to make choices. If IsIn() had a state value, I wouldn't have to worry so much ๐ But I could learn a lot. I decided to give up. Thank you very much.
-
[1.16.1]How to scare mobs
Sorry, I'm having trouble. I have a block that has an ON/OFF status, like a campfire. In this case, registering the block in the tag is bad. PiglinsMobsSensor has the following code. private static boolean func_241391_a_(ServerWorld p_241391_0_, BlockPos p_241391_1_) { BlockState blockstate = p_241391_0_.getBlockState(p_241391_1_); boolean flag = blockstate.isIn(BlockTags.field_232865_O_); return flag && blockstate.isIn(Blocks.SOUL_CAMPFIRE) ? CampfireBlock.func_226915_i_(blockstate) : flag; } It looks impossible to me... Is there a solution?
-
[1.16.1]How to scare mobs
Thank you very much! I was able to achieve it by creating a tag in the following location. src/main/resources/data/minecraft/tags/blocks/piglin_repellents.json { "replace": false, "values": [ "modid:myblock" ] } I have something to know. I initially tried to register via an internal variable, like BlockTagsProvider, but gave up. Is that possible?
-
[1.16.1]How to scare mobs
I want Piglin to be scared of my blocks. Like the fire of the soul. but I can't find its code. Where is that code? Or please tell me how.
IPS spam blocked by CleanTalk.