Skip to content
This repository has been archived by the owner on Sep 12, 2022. It is now read-only.

Major change to Forge-loom Getting Started #1

Open
SCDevel opened this issue Jan 31, 2021 · 2 comments
Open

Major change to Forge-loom Getting Started #1

SCDevel opened this issue Jan 31, 2021 · 2 comments
Labels
documentation Improvements or additions to documentation enhancement New feature or request priority: low This does not immediately need to be resolved

Comments

@SCDevel
Copy link

SCDevel commented Jan 31, 2021

https://architectury.github.io/architectury-documentations/docs/forge_loom/getting_started.html

My proposal is you don't try and create a forge (forge-loom) mod from the fabric example mod but the architectury example mod. It is extremely confusing for someone trying to create a forge only mod using forge-loom (mostly because the Getting Started does not state some things, i.e. changing the fabric resources to forge. and yes i was dumb not to think about it but it still happened and i had to learn it the hard way).

The reason I think this is better is because its easily laid out for both forge and fabric (and architectury multi-mod) instead of having fabric in the focus and then confusion at the end for forge. what you would do for one is what you would do for the other, is what im trying to say.

OK on with the proposal. im just going to make a fast tutorial.

'Main:' = the main directory
'Forge:' = the forge directory
'Fabric:' = the fabric directory
ML: = Forge: or Fabric: directory (Depending on which route you go)

When I list a few things to copy but don't say were to place it read a little more down

I tested this by making forge version. though this was written after so there may be a mistake. but the concept is the same.

1 Make 'em copies

Clone architectury-example-mod

2 Fixing the main gradle files and choosing a side(Mod Loader)

In Main:build.gradle:

  • in plugins remove apply false off of id "forgified-fabric-loom" version "0.6.59" apply false
  • delete everything that has architectury in it.
  • move dependencies outside of subprojects then delete subprojects
  • move all the contents of allprojects then delete allprojects
    In Main:gradle.properties:
  • delete architectury_version=1.5.101
  • Depending on which side you chose delete the all of other sides properties(i.e. for fabric delete forge_version=36.0.1)
  • if you chose forge add loom.forge=true (don't worry fabric will get its extra step too)
    In Main:settings.gradle:
  • delete everythng past pluginManagment. so the include()'s and rootProject.name

3 The Pre-Split

  • Delete the common directory
    in ML:build.gradle:
  • copy the whole processResources group.
    in Main:build.gradle:
  • paste the processResources group

4.1 For Forge

  • Delete the fabric directory
    In Forge:build.gradle:
  • copy forge "net.minecraftforge:forge:${rootProject.minecraft_version}-${rootProject.forge_version}" dependency
    In Main:build.gradle:
  • paste the forge dependency in dependencies
    Copy the src directory from the forge directory to the main directory and delete the forge directory
    Now your done and have a broken forge example mod (better than a fabric example mod though)

4.2 For Fabric

  • delete the forge directory
    In Fabric:build.gradle:
  • copy modCompile "net.fabricmc:fabric-loader:${rootProject.fabric_loader_version}" dependency
  • copy modCompile "net.fabricmc.fabric-api:fabric-api:${rootProject.fabric_api_version}" dependency
    In Main:build.gradle:
  • paste both the dependencies in the dependencies group
  • change modCompile to modImplementation on the dependencies you just pasted (remember the extra step I mentioned)
    Copy the src directory from the fabric directory to the main directory and delete the fabric directory
    Now your done and have a broken fabric example mod (better than a forge example mod though)

Finished

What you guys have going on here is amazing but there needs to be a better way to make either a fabric or a forge mod with a standard system were everyone can hop on and try, unlike how you have it now were its more fabric or both with the arch. plugin, where as forge kinda just gets left in the dust. anyway keep up the great work.

P.S. If i sound like a bit of a dick its not my intention, I'm just trying to improve this.

@SCDevel SCDevel changed the title Improvment to Forge-loom Getting Started Major change to Forge-loom Getting Started Jan 31, 2021
@shedaniel
Copy link
Member

I would like to offer a separate repo for an example mod using forgified fabric loom to build mods for forge. The thing is that the architectury example mod offers an example to a mod that compiles to both fabric and forge, and comparatively speaking, it is easier to convert the fabric example mod to forge than to convert the architectury example mod to forge.

I will definitely be improving the tutorial and the template in the future, and possibly automating the creation of new example mods into a downloadable MDK.

@MaxNeedsSnacks MaxNeedsSnacks added enhancement New feature or request documentation Improvements or additions to documentation and removed enhancement labels Apr 4, 2021
@MaxNeedsSnacks
Copy link
Member

A forgeloom example mod now exists, so now it's just a matter of updating the docs to state that, as well!

@MaxNeedsSnacks MaxNeedsSnacks added the priority: low This does not immediately need to be resolved label Apr 4, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
documentation Improvements or additions to documentation enhancement New feature or request priority: low This does not immediately need to be resolved
Projects
None yet
Development

No branches or pull requests

3 participants