NoSuchFieldError
1Euro7Cent opened this issue ยท 1 comments
WorldEdit Version
7.2.9
Platform Version
forge:1.18.1-39.1.0
Confirmations
- I am using the most recent Minecraft release.
- I am using a version of WorldEdit compatible with my Minecraft version.
- I am using the latest or recommended version of my platform software.
- I am NOT using a hybrid server, e.g. a server that combines Bukkit and Forge. Examples include Arclight, Mohist, and Cardboard.
- I am NOT using a fork of WorldEdit, such as FastAsyncWorldEdit (FAWE) or AsyncWorldEdit (AWE)
Bug Description
On startup the client crashes with that error in title.
Expected Behavior
Start client (not crash)
Reproduction Steps
- have a forge development enviroment
- add mod to mods folder
- client does not start
Anything Else?
I am developing my own mod and I want world edit to test things.
Putting that mod in the mods folder causes the client to not start.
optifine is working. So it's not a general mod loading problem.
crash report:
crash-2022-03-15_11.19.37-fml.txt
debug log:
debug.log
latest log:
latest.log
you cant throw "runtime-compiled" mods into a dev environment.
Forgegradle has specific mechanisms for depending on mods and remapping them for your dev workspace, ypu should go look at that.
edit: in fact judging by the mods already there, you're aware of this? not sure why you treated worldedit differently.
forge-1.18.1-39.1.0_mapped_official_1.18.1.jar |Minecraft |minecraft |1.18.1 |SIDED_SETU|Manifest: a1:d4:5e:04:4f:d3:d6:e0:7b:37:97:cf:77:b0:de:ad:4a:47:ce:8c:96:49:5f:0a:cf:8c:ae:b2:6d:4b:8a:3f
main |JustEnughTNT |justenoughtnt |0.0NONE |SIDED_SETU|Manifest: NOSIGNATURE
|Forge |forge |39.1.0 |SIDED_SETU|Manifest: NOSIGNATURE
silent-lib-1.18-6.0.0_mapped_official_1.18.1.jar |Silent Lib |silentlib |6.0.0 |SIDED_SETU|Manifest: NOSIGNATURE
worldedit-mod-7.2.9.jar |WorldEdit |worldedit |7.2.9+e20e013 |ERROR |Manifest: NOSIGNATURE
jei-1.18.1-9.2.3.84_mapped_official_1.18.1.jar |Just Enough Items |jei |9.2.3.84 |SIDED_SETU|Manifest: NOSIGNATURE