Jump to content

[Solved] Looking to get back into Minecraft Modding


WARDOGSK93

Recommended Posts

So im looking to get back into Minecraft Modding but dont know how to setup my build.gradle files

 

Want to layout my workspace like below, I havnt used gradle ever (I left Minecraft Modding just after gradle was added, between 1.6.4 and 1.7.10)

 

If anyone watches iChun's Dev streams (if he even still does them) this layout is kinda like how his is

 

Anyone know of a good tutorial or way that will make gradle set up my workspace how I want it

 

--------------------------------------------------------------

Workspace -¬

            CoreMod -¬

                      Can have deps that children can access

                      Src/Main/Java_Resources -¬

            Mod A -¬

                    Requires Core Mod

                      Src/Main/Java_Resources -¬

            Mod B -¬

                    Requires Core Mod

                      Src/Main/Java_Resources -¬

            Mod C (Mainly for testing if a API / Impl works) -¬

                    Requires Core Mod

                    Requires Mod A

                      Src/Main/Java_Resources -¬

            Run -¬

                  Clients / Servers run from here (Layout eg: 'Run/saves')

--------------------------------------------------------------

Link to comment
Share on other sites

Basic setup: http://www.minecraftforge.net/forum/index.php?topic=14048.0

 

One workspace == one project. One project != one mod.

 

So yeah, you can have many packages and classes with @Mod annotation (making your project have multiple mods), but when you compile it (build), you will have to either make Jars on your own or write script to do so (for such help you will probably need to look into gradle itself - there are help forums/tutorials I guess).

1.7.10 is no longer supported by forge, you are on your own.

Link to comment
Share on other sites

Basic setup: http://www.minecraftforge.net/forum/index.php?topic=14048.0

 

One workspace == one project. One project != one mod.

 

So yeah, you can have many packages and classes with @Mod annotation (making your project have multiple mods), but when you compile it (build), you will have to either make Jars on your own or write script to do so (for such help you will probably need to look into gradle itself - there are help forums/tutorials I guess).

 

Ive looked at that and i dont rly want to run 'gradle setupDevWorkspace' in all my mod folders, main reason why im making this post :P

 

isnt there any way using the 'dependencies {}' part of the 'build.gradle' file to make it depend on my 'CoreMod'? (if there is I would just do the same to make 'Mod C' depend on 'Mod A' right?)

Link to comment
Share on other sites

thats not what you think is a 'CoreMod' its what all my mods require like 'iChunUtil' 'CoFHCore' 'CodeChickenLib' etc but ye I guess calling it a CoreMod is wrong, no base Minecraft edits

 

That's effectively a library mod.  "Coremod" has a specific meaning.

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

Basic setup: http://www.minecraftforge.net/forum/index.php?topic=14048.0

 

One workspace == one project. One project != one mod.

 

So yeah, you can have many packages and classes with @Mod annotation (making your project have multiple mods), but when you compile it (build), you will have to either make Jars on your own or write script to do so (for such help you will probably need to look into gradle itself - there are help forums/tutorials I guess).

 

Ive looked at that and i dont rly want to run 'gradle setupDevWorkspace' in all my mod folders, main reason why im making this post :P

 

isnt there any way using the 'dependencies {}' part of the 'build.gradle' file to make it depend on my 'CoreMod'? (if there is I would just do the same to make 'Mod C' depend on 'Mod A' right?)

 

 

build.gradle

This goes in the @Mod annotation

mcmod.info

 

 

I assume you mean like that?

Link to comment
Share on other sites

After abit of google'ing i got my build.gradle file to do what i want :D

 

(mix of old gradle fiiles before i quit modding and what i just searched)

 

Gradle files

 

This sets up my workspace fully for me :D all in 1 build.gradle file, all mods depend on forge stuff and my 'Core' mod

 

*Please note i tested this on 1.7.10 since that was the last version i modded and want to try it with something im some what familiar with*


Basic setup: http://www.minecraftforge.net/forum/index.php?topic=14048.0

 

One workspace == one project. One project != one mod.

 

So yeah, you can have many packages and classes with @Mod annotation (making your project have multiple mods), but when you compile it (build), you will have to either make Jars on your own or write script to do so (for such help you will probably need to look into gradle itself - there are help forums/tutorials I guess).

 

Ive looked at that and i dont rly want to run 'gradle setupDevWorkspace' in all my mod folders, main reason why im making this post :P

 

isnt there any way using the 'dependencies {}' part of the 'build.gradle' file to make it depend on my 'CoreMod'? (if there is I would just do the same to make 'Mod C' depend on 'Mod A' right?)

 

 

build.gradle

This goes in the @Mod annotation

mcmod.info

 

 

I assume you mean like that?

 

Thanks i was also about to ask how does one do dependencies again in @Mod ;)

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

Announcements



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • I tried to play a mod for forge 1.20.2 and the mod didn't work, fix this please.
    • EntityRenders requires an EntityRenderProvider. This is what I have: @Mod.EventBusSubscriber(modid = MODID, bus = Mod.EventBusSubscriber.Bus.MOD, value = Dist.CLIENT) public static class ClientModEvents { @SubscribeEvent public static void clientSetup(FMLClientSetupEvent event) { EntityRenderers.register(HOSE.get(), new HoseEntityRenderFactory()); } private static class HoseEntityRenderFactory implements EntityRendererProvider<HoseEntity> { @Override public EntityRenderer<HoseEntity> create(Context context) { return new HoseEntityRenderer<>(context); } } } Replace HoseEntity with your own entity. If you're doing multiple try doing generics (though untested).
    • First off, I know should probably be able to debug this on my own, but this is my first mod, and I couldn't figure it out for multiple days now. What I'm trying to do, is to modify the default minecart by replacing it with a slightly different version, but I'm stuck 1 step before that, that being "cloning" the minecart as a separate Entity/Item. Here you can see a GitHub gist of all relevant files: https://gist.github.com/Kipama/cd39127e8891715a3006fa990ca7ff14 If there are files missing or access isn't working as intended, please let me know! In the Gist you can find the following files: -CustomMinecartEntity.java:        This file extends AbstractMinecart and is a clone of the vanilla minecart entity. I know I should override the minecart entity directly, but as this should work rn, I didn't change it yet. -CustomMinecartRenderer.java:  Basically vanilla MinecartRenderer with a Custom slapped on it, extends MinecraftRenderer. -ModEntities.java:                         This is where the new Entity gets added to the deferred register ENTITY_TYPES. -ModernMinecarts.java:               The main mod file. Relevant part is at the bottom, where I try to use onClientSetup to register the new Entity using EntityRenderers.register(). That last part is where my problem begins. When I try to register the new entity using EntityRenderers.register(ModEntities.CUSTOM_MINECART_ENTITY.get(), CustomMinecartRenderer::new); I get a syntax Error saying the provided and required types don't match. These are the required and provided types: ModEntities.CUSTOM_MINECART_ENTITY.get(): Required: EntityType<? extends T> Provided:EntityType<CustomMinecartEntity> CustomMinecartRenderer::new: Required: EntityRendererProvider<T> Provided:<method reference   So far I looked at 2 different Git repositories implementing custom entities, but haven't been able to figure out what I'm doing wrong. Any answers, suggestions and ridicules appreciated.
    • Yes, it is. I found out how to do it. (for Forge 1.20.1) Add this to main class constructor: // ... MinecraftForge.EVENT_BUS.<PlayerInteractEvent.EntityInteract>addListener(e -> { Player playerWhoUsed = e.getEntity(); ItemStack usedItemStack = e.getItemStack(); Entity entityThatWasClicked = e.getTarget(); if (usedItemStack.getItem() instanceof YourItem item) { // your code... e.setCancelled(true); // you can remove this if you want to continue interaction } } // ...
    • Hi there, I'm hoping to create a block that renders a fake skybox, blocking anything behind it. There are a couple of mods that already do this, but they are very outdated. One example: https://github.com/Elix-x/Skyblocks/ https://www.curseforge.com/minecraft/mc-mods/skyblocks I'm not familiar enough with rendering to be able to port it. Is there anyone who can point me in the right direction? Any help would be appreciated.
  • Topics

×
×
  • Create New...

Important Information

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