Ordinator

Thank you for including in this commit the change for these log entries to be DEBUG level instead of TRACE. It'll be much easier for anyone else in the future to provide logs that have the necessary Registry entries with just "THE DEBUG FLAG ENABLED" and not have to figure out that TRACE logging needs to be set in Java properties as well. These are the logs with TRACE logging from a user on Forge 2456 that would get this error 100% of the time when trying to connect even after multiple client restarts and multiple "fresh install" of the modpack: https://gist.github.com/OrdinatorStouff/482605faa16e4412b2fe15e55b2cbeac The same user then switched to Forge 2460 and and was able to connect to the server (still running 2456) without the error/warning. I assume that this user being able to connect now when 100% he could not before means that this bug has been fixed, but if you would like to see the same logs from the 2460 successful server join or server logs or anything else please let me know.

Internal Exception: java.lang.illegalstateexception: could not determine owner for override on aroma1997sdimension:aromicportal. Vaule: block(null) When using a dedicated server that has ever had any blocks removed (either by mod update rename/removal) or an entire mod removal from the instance, clients will sometimes encounter the above error when trying to connect to the server. Usually a client restart will fix it, but I've had multiple people report that it can take 4+ consecutive restarts before they can finally load into the SMP world and some are not able to ever get in no matter how many restarts of the client or server. As directed by LexManos in this PR ( https://github.com/MinecraftForge/MinecraftForge/pull/4266 ) I had a user that was experiencing this add "-Dforge.debugRegistryEntries=true" to their launch args and send me their latest.log as follows: ( http://paste.ubuntu.com/25342196/ ) This example came from 14.21.1.2443 but as far as I'm aware it's been experienced in multiple 1.12 forge versions. I am an administrator of the "All The Mods" modpack team and have encountered this error with many of our users on our official servers as well as having reports made on other servers. Here's an example of the same error being reported to Aroma1997's issue tracker as well ( https://bitbucket.org/Aroma1997/miningworld/issues/134/people-not-being-able-to-join-server ) demonstrating the issue is widespread.