Jump to content
View in the app

A better way to browse. Learn more.

Forge Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

warjort

Members
  • Joined

  • Last visited

Everything posted by warjort

  1. If this is 1.19.3, textures need to be in the item folder not items. See Mojang's change notes Otherwise you are going to need to show more than just 4 lines of json, preferably on github. Does changing it to use minecraft:item/apple work?
  2. Use java 17, mixin does not support java 19
  3. That is a crash in the java virtual machine. Did you try the create/flywheel configuration change posted above? https://forums.minecraftforge.net/topic/119518-exit-code-1073740940/#comment-524102 Otherwise you need to talk to microsoft or try a different java.
  4. Looks like a conflict between create and a mixin added by the deftware framework mod EMC.jar?
  5. Looks like an issue with bountiful mod. Check you have the latest version then contact the mod author. Off-topic. You should use java 17. That is the long term support version. You won't get anything but security fixes for java 18 now java 19 is released.
  6. That doesn't show an error either. The last thing in the log is an error from the signpost and/or dynamic surroundings mods, but there are many of those. Then it just shows the error code And then it says it trying to submit a crash report to Mojang but that fails because of bad ip configuration? It doesn't say which crash report it is trying to submit.
  7. Looks like an issue with the create mod. Probably caused by an earlier we can't see because you don't post a link to your logs/debug.log Check you have the latest version of the create and registrate mods then contact the mod author.
  8. Conflict between uniquebase and apotheosis. Check you have the latest versions then contact the mod authors.
  9. I don't see anything identify a problem mod in that log, but I do see this before the error you are getting Maybe the server debug.log has some information? That log does at least show which mods have custom network code Which should help in cutting down the search?
  10. warjort replied to N4no57's topic in Modder Support
    Same error as before, but this time with a folder name in your assets directory?
  11. ItemRenderer e.g. see how the CampfireRenderer uses it.
  12. Forge can't create your mod. Probably because there is no public no args constructor?
  13. A painting is an entity. You need to use one of the level.getEntities() methods with the bounding box (AABB) saying where you are looking.
  14. There is no error in the server log. The client seems to stop responding when processing the registries. Add the same system property to your client launcher so we can see what is happening there. Also if you just going to remove all the mods. You should try a fresh reinstall of the server with a new world save. That will rule out something corrupted in your save files causing this.
  15. Look at the ResourceLocation class for valid namespaces (modids)
  16. We are talking about very different things. There are the mod event bus events that run at game startup to do one time initialisation. Then there are the runtime events for when the actual server/runtime is starting (ServerLifecycleEvents + others). Which do things that need to change things based on which save is loaded.
  17. See the javadoc for CapabilityProvider.reviveCaps() i.e. getting access to the original capabilities for removed objects. Don't forget to invalidateCaps() afterwards.
  18. When you create the world/save. Or you can temporarily enable cheat mode if you "open to lan".
  19. In singleplayer you enable cheat mode to get op privileges.
  20. Technically a provider is a superset of that because not all providers will/have to fire the attach event.
  21. An entity is a provider. A provider is anything that can have capabilities attached to it. What it is talking about is a provider that has internal capabilites not registered in the CapabilityDispatcher - e.g. it overrides getCapability() instead. See for example the internal inventory capabilities in LivingEntity (equipment slots) or BaseContainerBlockEntity (vanilla containers). It has to override invalidateCaps() to invalidate these additional capabilities. When you attach your capability to a say an entity, you can add that listener which will tell you when the entity has been removed from the world so you can do any additional tidyup e.g. if your capability uses other internal capabilites that need to be invalidated.
  22. That is an error in the networking code of one of your mods. Post a link to your logs/debug.log to see if it has any clue to which mod is causing it. Using the wrong (1.19) version of journey map with 1.19.2 is an FAQ in this forum. But usually the only way to find the problem mod is to experiment with removing mods until the problem goes away. (Backup your world before removing mods).
  23. warjort replied to LightningLemonTart's topic in Mods
    Issue with the same mod - actually its library mod (puzzleslib). Check you have the latest version then contact the mod author.
  24. You don't create a loop. Minecraft is "event driven". You set some state inside your entity then override Entity.tick() or one of its called methods to do the check. You should look at how LivingEntity handles Levitation in travel() - called by tick(). Levitation is a MobEffect rather than a simple flag inside the entity.
  25. Post a link to the logs/debug.log so we can see the error.

Important Information

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

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.