Jump to content

Any tips for beginners?


schefrog

Recommended Posts

Hi! I promised my kids to make a mod for my thesis. I can spend 400 hours with this. I know Java very well, but I don't know Minecraft yet. So my plan is to start playing Minecraft and learn modding from the Forge documentation... but is it realistic? Can you give me some advise on how to get started? What are some good projects to start with, and what could be done in the given time frame by a MC/Forge newbie? Thanks for any suggestions.

Link to comment
Share on other sites

Well, to start modding, you have to learn Minecraft. And to learn Minecraft, you have to play Minecraft. You should start with a very basic Survival World, and see how does the player interact with the world. If you don't understand something, the Minecraft wiki can help you.

Then, after spending a few hours (depending if you learn fast or not) on the game, you can start modding. You have the official Forge documentation here.

To create a basic mod (adding a block or an item), you don't need a lot of Minecraft knowledge. But when your mod starts to be complicated (networking, capabilities...), you'll need more and more Minecraft knowledge.

Also, if you need examples when modding, always look at Minecraft source code. You'll find a lot of examples in the source code, and they will always be up-to-date.

Good luck !

Link to comment
Share on other sites

My usual suggestion still applies, although I will agree with Franckyi, step 0: play Minecraft.

If you don't feel like using the wiki to constantly look up how to make items (and you're not on 1.12 with the recipe book), then I recommend installing Forge and then JEI (Just Enough Items) or NEI (Not Enough Items) depending on which version of Minecraft you're using (those names, by the way, are jokes on the original mod, Too Many Items).

 

From there:

 

Start basic. No, even simpler. Start with a decorative block. Something that does nothing but sit there and look pretty. Or ugly. Who cares about looks, all we care about right now is creating a single block and getting it to show up.

Then make a simple item, again, looks pretty (or ugly).

Then make a block that in some way reacts to something the player does. Maybe it's oriented like a log and when you right-click it, it rotates.

Then make a block that stores data in a Tile Entity.

Then make a machine block (something that has an inventory)--including a UI--does something with that inventory, and finally, displays that progress in the GUI screen.

 

At every stage of the process you should either know how to do everything, know where to look to find a block that does something similar, or have exactly one unknown (or at least, as few as possible). Don't immediately go "I want to make a custom 5x5 autocrafting crafting bench that uses the oredictionary, damages one of the inputs (a "tool"), and makes noise while doing it!" You'll have too many unknowns and will almost certainly try to make things in the wrong order.

Apparently I'm a complete and utter jerk and come to this forum just like to make fun of people, be confrontational, and make your personal life miserable.  If you think this is the case, JUST REPORT ME.  Otherwise you're just going to get reported when you reply to my posts and point it out, because odds are, I was trying to be nice.

 

Exception: If you do not understand Java, I WILL NOT HELP YOU and your thread will get locked.

 

DO NOT PM ME WITH PROBLEMS. No help will be given.

Link to comment
Share on other sites

I agree with Draco18s, having started and stopped modding multiple times. Only things I'd change is play "current" version of minecraft. I'd start with simple items then blocks. After simple block learn about the different minecraft rendering layers. Then continue with Draco18s directions. After his directions work with particles. 

 

Some things to know is there's a lot of material out there and most of it is out of date. Most the time you'll be taking out of data material and updating it. Don't ask any questions about any material below 1.10 on these forums or your thread will get locked very fast and you won't get the answer you need. When you have completed items, blocks, and particles, I also suggest you get familiar with the major mods out there by playing with a couple of the large FTB modpacks in creative mode. This teaches you what players are looking for and what is possible. Then formulate an idea of what you want and look up some of the githubs of mods with similar type stuff. 

 

Things to look out for is everyone structures their code differently. Some will place a function in the block code, others the client proxy, others in "main", and some in a strange class you haven't seen with any other mod. There is very little reason to how people setup things other than that's how they got it to work and makes sense to them. You just need to take their code and play with it until it breaks to figure out what does and doesn't work for yourself. 

 

I use youtube videos and these examples. 

https://bedrockminer.jimdo.com/modding-tutorials/

https://github.com/Choonster-Minecraft-Mods

https://github.com/TheGreyGhost/MinecraftByExample

 

Rome was built up brick by brick. Aim small and expand as you accomplish more and more. Don't build on top of a foundation you don't understand or you'll find pieces of your code not working that should and won't understand why. I have personally tried skipping each one of these steps that were also suggested to me multiple times, and it never ended well, which is why I've started over so many times.

Edited by Stroam

You don't need to point out what's wrong with the programmer. I already know. Now what's wrong with the code?

Link to comment
Share on other sites

The reason I suggest starting with blocks, rather than items, is because you can say "f*k it" to the ItemBlock and just deal with a purple cube until you're ready to do items. Your first item? That block. :)

Apparently I'm a complete and utter jerk and come to this forum just like to make fun of people, be confrontational, and make your personal life miserable.  If you think this is the case, JUST REPORT ME.  Otherwise you're just going to get reported when you reply to my posts and point it out, because odds are, I was trying to be nice.

 

Exception: If you do not understand Java, I WILL NOT HELP YOU and your thread will get locked.

 

DO NOT PM ME WITH PROBLEMS. No help will be given.

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.