Jump to content

[FORGE 1.7.2] Crashes when running client through Eclipse


Skua

Recommended Posts

Hi all.

 

This is my second time modding with Forge now. I think I tried in 1.5, but never really followed through with it. If I can remember correctly, I just followed a video for the install and everything was great.

 

Just recently, I had an urge to start again. So, I attempted installing MCP & Forge together (the hard way) via a video tutorial for 1.6.4. Let's just say, it was a nightmare. It just didn't work. I tried updating my JDK (currently on 7) and all sorts. I ended up getting 73 errors in my Terminal. I'm using a Mac so that makes everything 10x as difficult I guess  :-\

 

Anyway, today I saw a thread explaining that I should use Gradle. That it's a much, much more efficient way of installing Forge w/ MCP for 1.7.2 and they sent me to this thread: http://www.minecraftforge.net/forum/index.php/topic,14048.0.html

 

-After following the "initial setup" stages, everything seemed to be working. I installed both the Eclipse workspace and Gradle with no problems whatsoever. Just as everything was going well, (I had setup and opened Eclipse via the workspace folder by this point) I tried to "Run Client" using the green play button on the top toolbar. It gave me several error messages and glitched the Minecraft window out. The music for the game also started to play very, very loud and my computer lagged out for like 3 seconds. When I tried playing Minecraft 1.7.2 with the normal launcher it was fine.

 

Here are my error messages:

http://pastebin.com/sRbQtEMk

 

I hope you guys can help. It's a shame because I really want to mod again  :-\ and it never seemed this hard to install in 1.5.

 

-P.S I've tried everything from deleting all the files in my Minecraft, re-installing the Gradle 3 times over, changing the workspace folders and deleting the example code. Nothing seems to work.

 

Thanks, Skua.

Link to comment
Share on other sites

Try making a new folder and reinstalling forge there. It looks like you have some build errors like:

/Users/Ben/Desktop/MCSK Mod Folder/forge-1.7.2-10.12.0.1057-src/eclipse/mods for mods
[13:25:30] [Client thread/ERROR] [FML]: FML has detected a mod that is using a package name based on 'net.minecraft.src' : net.minecraft.src.FMLRenderAccessLibrary. This is generally a severe programming error.  There should be no mod code in the minecraft namespace. MOVE YOUR MOD! If you're in eclipse, select your source code and 'refactor' it into a new package. Go on. DO IT NOW!

 

Link to comment
Share on other sites

Try making a new folder and reinstalling forge there. It looks like you have some build errors like:

/Users/Ben/Desktop/MCSK Mod Folder/forge-1.7.2-10.12.0.1057-src/eclipse/mods for mods
[13:25:30] [Client thread/ERROR] [FML]: FML has detected a mod that is using a package name based on 'net.minecraft.src' : net.minecraft.src.FMLRenderAccessLibrary. This is generally a severe programming error.  There should be no mod code in the minecraft namespace. MOVE YOUR MOD! If you're in eclipse, select your source code and 'refactor' it into a new package. Go on. DO IT NOW!

 

Thanks for your reply. I'll try doing this again and see if it helps, but I have already done this and it doesn't seem to alter the error.

 

Something else to note, it seems to keep "skipping" loads of the process inside Terminal? Is this meant to happen. On my first install it took ages and didn't skip anything :/

Link to comment
Share on other sites

Try making a new folder and reinstalling forge there. It looks like you have some build errors like:

/Users/Ben/Desktop/MCSK Mod Folder/forge-1.7.2-10.12.0.1057-src/eclipse/mods for mods
[13:25:30] [Client thread/ERROR] [FML]: FML has detected a mod that is using a package name based on 'net.minecraft.src' : net.minecraft.src.FMLRenderAccessLibrary. This is generally a severe programming error.  There should be no mod code in the minecraft namespace. MOVE YOUR MOD! If you're in eclipse, select your source code and 'refactor' it into a new package. Go on. DO IT NOW!

That error is suppose to happen because of a Forge mistake.

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.