Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

DeferredRegistries vs Registry Event Questions


Daniel Rollins
 Share

Recommended Posts

Hi,

I've been hearing a lot about Deferred Registries recently. Some people seem to say this is the new/better way to register everything and to change everything over to the new way. Other people seem to indicate that it is useful for some things and not others. Some people have mentioned certain things not working with deferred registries. Rather than go off of hearsay and people who probably don't know much about the subject, I'd like to hear from you all the truth about this. Is Deferred registries the new way, replacing the old? Should I be changing all my Registry Events to deferred registries? Or is this just a tool for certain use cases, and if so, what cases? Is there a doc somewhere about this? I did try looking for one but haven't found anything answering my questions. Thanks

Link to comment
Share on other sites

Howdy

At the moment, I think it's largely a matter of personal preference.

 

Personally I don't like deferred registries because I hate the "magic pokery" of the Annotations methods, I prefer a more imperative style because it's much easier to find references to objects using the IDE that way.  

 

But they both work fine, with the possible exception of some of the DedicatedServer vs ClientOnly events (old-style proxy) which are much easier to use in the imperative style.  I wouldn't bother to change if/until the Forge masters remove the imperative style entirely.

 

-TGG

 

 

Link to comment
Share on other sites

Deferred Registers are there to placate people who felt they needed to statically initialize crap.

They are just a wrapper around the Registry Event system.

This is my Forum Signature, I am currently attempting to transform it into a small guide for fixing easier issues using spoiler blocks to keep things tidy.

 

As the most common issue I feel I should put this outside the main bulk:

The only official source for Forge is https://files.minecraftforge.net, and the only site I trust for getting mods is CurseForge.

If you use any site other than these, please take a look at the StopModReposts project and install their browser extension, I would also advise running a virus scan.

 

For players asking for assistance with Forge please expand the spoiler below and read the appropriate section(s) in its/their entirety.

Spoiler

Logs (Most issues require logs to diagnose):

Spoiler

Please post logs using one of the following sites (Thank you Lumber Wizard for the list):

https://gist.github.com/100MB Requires member (Free)

https://pastebin.com/: 512KB as guest, 10MB as Pro ($$$)

https://hastebin.com/: 400KB

Do NOT use sites like Mediafire, Dropbox, OneDrive, Google Drive, or a site that has a countdown before offering downloads.

 

What to provide:

...for Crashes and Runtime issues:

Minecraft 1.14.4 and newer:

Post debug.log

Older versions:

Please update...

 

...for Installer Issues:

Post your installer log, found in the same place you ran the installer

This log will be called either installer.log or named the same as the installer but with .log on the end

Note for Windows users:

Windows hides file extensions by default so the installer may appear without the .jar extension then when the .log is added the log will appear with the .jar extension

 

Where to get it:

Mojang Launcher: When using the Mojang launcher debug.log is found in .minecraft\logs.

 

Curse/Overwolf: If you are using the Curse Launcher, their configurations break Forge's log settings, fortunately there is an easier workaround than I originally thought, this works even with Curse's installation of the Minecraft launcher as long as it is not launched THROUGH Twitch:

Spoiler
  1. Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge)
  2. Make a launcher profile targeting this version of Forge.
  3. Set the launcher profile's GameDir property to the pack's instance folder (not the instances folder, the folder that has the pack's name on it).
  4. Now launch the pack through that profile and follow the "Mojang Launcher" instructions above.

Video:

Spoiler

 

 

 

or alternately, 

 

Fallback ("No logs are generated"):

If you don't see logs generated in the usual place, provide the launcher_log.txt from .minecraft

 

Server Not Starting:

Spoiler

If your server does not start or a command window appears and immediately goes away, run the jar manually and provide the output.

 

Reporting Illegal/Inappropriate Adfocus Ads:

Spoiler

Get a screenshot of the URL bar or copy/paste the whole URL into a thread on the General Discussion board with a description of the Ad.

Lex will need the Ad ID contained in that URL to report it to Adfocus' support team.

 

Posting your mod as a GitHub Repo:

Spoiler

When you have an issue with your mod the most helpful thing you can do when asking for help is to provide your code to those helping you. The most convenient way to do this is via GitHub or another source control hub.

When setting up a GitHub Repo it might seem easy to just upload everything, however this method has the potential for mistakes that could lead to trouble later on, it is recommended to use a Git client or to get comfortable with the Git command line. The following instructions will use the Git Command Line and as such they assume you already have it installed and that you have created a repository.

 

  1. Open a command prompt (CMD, Powershell, Terminal, etc).
  2. Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in).
  3. Run the following commands:
    1. git init
    2. git remote add origin [Your Repository's URL]
      • In the case of GitHub it should look like: https://GitHub.com/[Your Username]/[Repo Name].git
    3. git fetch
    4. git checkout --track origin/master
    5. git stage *
    6. git commit -m "[Your commit message]"
    7. git push
  4. Navigate to GitHub and you should now see most of the files.
    • note that it is intentional that some are not synced with GitHub and this is done with the (hidden) .gitignore file that Forge’s MDK has provided (hence the strictness on which folder git init is run from)
  5. Now you can share your GitHub link with those who you are asking for help.

[Workaround line, please ignore]

 

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.

Guest
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.

 Share



  • Recently Browsing

    No registered users viewing this page.

  • Posts

    • Ran again after I got up, had a different error: PS C:\Users\user\Desktop\MinecraftForge> ./gradlew setup To honour the JVM settings for this build a single-use Daemon process will be forked. See https://docs.gradle.org/7.2/userguide/gradle_daemon.html#sec:disabling_the_daemon. Daemon will be stopped at the end of the build > Configure project : Version: 1.17.1-37.0.61 Java: 1.8.0_291 JVM: 25.291-b10(Oracle Corporation) Arch: amd64 > Configure project :clean WARNING: This project is configured to use the official obfuscation mappings provided by Mojang. These mapping fall under their associated license, you should be fully aware of this license. For the latest license text, refer below, or the reference copy here: https://github.com/MinecraftForge/MCPConfig/blob/master/Mojang.md, You can hide this warning by running the `hideOfficialWarningUntilChanged` task WARNING: (c) 2020 Microsoft Corporation. These mappings are provided "as-is" and you bear the risk of using them. You may copy and use the mappings for development purposes, but you may not redistribute the mappings complete and unmodified. Microsoft makes no warranties, express or implied, with respect to the mappings provided here. Use and modification of this document or the source code (in any form) of Minecraft: Java Edition is governed by the Minecraft End User License Agreement available at https://account.mojang.com/documents/minecraft_eula. FAILURE: Build failed with an exception. * Where: Build file 'C:\Users\user\Desktop\MinecraftForge\fmlcore\build.gradle' line: 7 * What went wrong: A problem occurred evaluating project ':fmlcore'. > java.lang.UnsupportedClassVersionError: org/javamodularity/moduleplugin/ModuleSystemPlugin has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0 * Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights. * Get more help at https://help.gradle.org BUILD FAILED in 21s 2 actionable tasks: 2 up-to-date  
    • Here's a shot of where I'd expect to find it. There's one older forge version that appears at the bottom of the list, so I checked its entire length to be sure.  
    • Hi!, I'm trying to set up a workspace for a 1.17 mod. I want to port a 1.16.5 mod I already have, but first I wanted to try to set up a new empty mod, just to assure it works. The problem is when I run genEclipseRuns, it throws me FAILURE: Build failed with an exception. * What went wrong: Could not resolve all files for configuration ':runtimeClasspathCopy'. > Could not find net.minecraftforge:forge:1.17.1-37.0.61_mapped_official_1.17.1. Searched in the following locations: - file:/C:/Users/migue/.gradle/caches/forge_gradle/bundeled_repo/net/minecraftforge/forge/1.17.1-37.0.61_mapped_official_1.17.1/forge-1.17.1-37.0.61_mapped_official_1.17.1.pom - file:/C:/Users/migue/.gradle/caches/forge_gradle/bundeled_repo/net/minecraftforge/forge/1.17.1-37.0.61_mapped_official_1.17.1/forge-1.17.1-37.0.61_mapped_official_1.17.1.jar Required by: project : * Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights. * Get more help at https://help.gradle.org Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0. You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins. See https://docs.gradle.org/7.2/userguide/command_line_interface.html#sec:command_line_warnings BUILD FAILED in 24s I have OpenJDK16, and the Path and JAVA_HOME variables correctly set. I'm using the default mdk, so I didn't change anything from build.gradle Any help is appreciated, I've been stucked with this for hours
    • I'm new to Java and modding, so I went to the tutorial on https://mcforge.readthedocs.io/en/1.16.x/gettingstarted/ but I already am facing issues. I followed the guide up until step 6, at which point when I run "gradlew enIntellijRuns" I get an error which reads "Could not find net.minecraftforge:forge:1.16.5-36.2.0_mapped_official_1.16.5.". Do any knowledgable modders know what this means and how to fix it? Log: https://pastebin.com/vt9VgLPz Please let me know if I need to supply any additional information such as further logs or screenshots.
    • I will check out how chests work and see if I can figure a couple things from that, meanwhile ignore the fact I just table flipped on setBlock doing one thing, but not with blockpos.offset wow this change from 1.7 to 1.17 is making me feel dumb Lol Edit: yup nope lack of sleep derp for that Lol Oh well
  • Topics

  • Who's Online (See full list)

×
×
  • Create New...

Important Information

By using this site, you agree to our Privacy Policy.