Jump to content

Luis_ST

Members
  • Posts

    5704
  • Joined

  • Last visited

  • Days Won

    72

Everything posted by Luis_ST

  1. Please create your own thread and post there the debug.log from the logs folder. If you using CurseForge you need to enable the debug.log in the settings. You can use https://gist.github.com/ to upload log file.
  2. This is not really helpful. Please post a Git Repo of your Mod.
  3. Your answer have the same result. Moderation: Lock thread, since unsupported version
  4. Which version of Forge did you use? The installer does generate the .bat and .sh file which must be used to start the server.
  5. What exactly is your problem? Please post debug.log from the logs folder.
  6. But the log you post is the same like in your other thread. Please post debug.log from the logs folder. If you using CurseForge you need to enable the debug.log in the settings.
  7. Please post debug.log from the logs folder. If you using CurseForge you need to enable the debug.log in the settings.
  8. In addition to @warjort: Ideally a Git repo of your Mod, so we can debug this locally.
  9. Mixin is the last thing you should use, it's in no way recommend and officially not supported on this Forum. In general it's better to create a PR to Forge to add a Hook or a Event for this that to use Mixin.
  10. How are you be able to compile this? You should use the public setter PlayerEvent$BreakSpeed#setNewSpeed.
  11. Duplicated thread of: Please do not create duplicate threads.
  12. Do you have any idea what exactly cause this issue, it seems like not? Due this error happens really often and is known by OptiFine and already fixed.
  13. Please post debug.log from the logs folder. If you using CurseForge you need to enable the debug.log in the settings. You can use https://gist.github.com/ to upload larger text files.
  14. This shows you have literally no idea what cause the crash. Moderation: This thread should be locked, due suspicious version (i guess it's 1.16.5).
  15. You should properly ask a Question like this, on the Forge Discord server (link: https://discord.gg/forge).
  16. The issue has already been reported: https://github.com/AlexModGuy/Citadel/issues/81
  17. Please post a screenshot of your Mods folder or a Mod List. Problem with citadel.
  18. A loot table is already a form of a config, you can replace/edit it by creating a data pack for your Mod which replace this file.
  19. Make sure you post the full debug.log from the logs folder. If this is the full debug.log please post launcher_log.txt as well.
  20. Please post debug.log from the logs folder. If you using CurseForge you need to enable the debug.log in the settings.
  21. You can try to use a backsplash before the %, or you add the % when creating the TranslatableComponent.
×
×
  • Create New...

Important Information

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