Leaderboard
-
Draco18s
Members3Points16559Posts -
poopoodice
Members2Points1160Posts -
DaemonUmbra
Members1Points11222Posts -
Red90
Members1Points4Posts
Popular Content
Showing content with the highest reputation on 08/13/20 in Posts
-
double x = event.getPlayer().getPosX(); double y = event.getPlayer().getPosX <--------??? (); double z = event.getPlayer().getPosX <--------??? ();2 points
-
1 point1) Do not hijack threads 2) Our installer installs everything you need. 3) This has been answered literally a hundred + times.1 point
-
(And I assume that "commonnamespace" is not literally "commonnamespace" but something identifiable to your mod.)1 point
-
Yes. That's how tags work. They are tied to a resource location. Just as minecraft:stone and somemode:stone are different, so too is minecraft:carnivore and mymod:carnivore.1 point
-
1 pointOk, let's do a breakdown of lazy coding. You need a tile entity for that. You need a tile entity for that. You need a tile entity renderer for that. You need to put your block in the block tags for campfires. Just because you decide to copy one part of a block doesn't necessarily mean it will work. At least check and make sure the block isn't referencing anything else before doing so.1 point
-
You haven't understood what Draco and I told you. minecraft:carnivores is a completely unrelated tag to mymod:carnivores. There is no link between them AT ALL. You need to make a single tag (maybe myanimalmodid:carnivores), then for each of your expansion mods, you add to THAT tag. Not to a different tag for each mod.1 point
-
1 pointDelete these folders: %USERPROFILE%\.gradle\caches\forge_gradle\mcp_repo\de\oceanlabs\mcp\mcp_config\1.15.2-20200515.085601 %USERPROFILE%\.gradle\caches\forge_gradle\maven_downloader\de\oceanlabs\mcp\mcp_config\1.15.2-20200515.085601 %USERPROFILE%\.gradle\caches\forge_gradle\minecraft_user_repo\de\oceanlabs\mcp\mcp_config\1.14.4-20190829.143755 and run the refresh command again1 point
-
1 pointNow I'm curious why. I don't think its taken "years" even for a major version. The longest delay I'm aware of was either 1.7 -> 1.10 or 1.12 -> 1.14 In both cases I don't believe it even took a full year. And I know for certain that the majority of the time waiting on 1.14 was due to a massive (absolutely massive) restructuring of Forge's own code to clean up and refactor huge sections of the core codebase to be more robust.1 point
-
Well, 1.16 is quite similar to 1.15, and there's this: https://gist.github.com/williewillus/30d7e3f775fe93c503bddf054ef3f93e That's a primer for 1.15; the rendering system is probably the biggest change in that version. I honestly don't know much about the code before 1.16, but from what I've gathered a majority of tutorials are still relevant from 1.15. One major change in 1.16 that I DO know of is dimensions and dimensiontypes.1 point
-
1.8 is no longer supported on this forum. Update to a modern version of Minecraft to receive support.0 points
