Leaderboard
Popular Content
Showing content with the highest reputation since 04/16/24 in all areas
-
This PR may fix the remaining issues here. It's still under review and hasn't been released yet, but may be merged and released in the next few days or so.2 points
-
dont worry about this anymore, i think ive got it. thanks for the suggestion though1 point
-
# Problematic frame: # C [atio6axx.dll+0x192b60] Get the latest AMD/ATI drivers from their website1 point
-
1 point
-
1 point
-
Make a test witout xaerominimap and xaeroworldmap1 point
-
That seemed to fix it! Both Textrue's Embeddium Options and Projectile Damage Attribute were causing it to crash. Thank you so much!1 point
-
Idk how u do it but ty fr, I update it and it works, so ty again1 point
-
After I removed it the debug showed me an error that cleared it up, it was canary doing it, a performance mod that it makes sense to have been conflicting. Thank you!1 point
-
1 point
-
Tried it, and changed a bunch more settings and it works. Not sure what made it work because it is running on the integrated card instead of the GeForce one (probably just because I have not restarted the PC yet) but all packs load up now. Thank you for your help.1 point
-
1 point
-
1 point
-
Thanks!! Now it works.1 point
-
1 point
-
1 point
-
I tested it and apparently the problem comes directly from rubidium/oculus and Valkyrien skies, they're not compatible in 1.20x... I'm maybe going to fabric then since optifine doesn't work either. Thank you anyway and have a great day!1 point
-
If you have nvidia graphics, don't touch your amd drivers, otherwise it might fix it but keep running on integrated graphics, which will result in terrible performance. For nvidia graphics, you need to tell windows and nvidia control panel that anything Minecraft related (the launcher, java, etc...) should prefer high performance graphics so that it actually uses your nvidia gpu1 point
-
1 point
-
On the one off the last lines of code you have put && boots.isEmpty() Instead of && !boots.isEmpty() is that a typo?1 point
-
Changing the event to RenderGuiEvent.post kinda did the trick. If there is any more suitable events please tell me, and thanks for the help!1 point
-
1 point
-
That didn't actually attach your project, it just shows a filename. Also, attaching as a compressed file is not the best way to share, you should create a github repository for it, then share the link here. https://www.google.com/search?q=how+to+use+github1 point
-
public static void sendEntityToLevel(ServerLevel otherDimensionLevel, LivingEntity entity, Vec3 location) { entity.teleportTo(otherDimensionLevel, location.x, location.y, location.z, new HashSet<>(), 0, 0 ); } This is what I'm using and it's worked fine1 point
-
thanks, you nailed with the answer, my mistake I didn’t check out the lastlog before, so I found the error, It’s a mod problem, The corail woodcutter, I don’t why, because one day all was runinng smooth and just next day happen that, but I already solved the problem, thanks again.1 point
-
Oh! It worked. thanks! i paid someone to make a modpack for me but it just wasnt working. Was the one mod breaking my entire Modpack? 0.0 thanks again!1 point
-
1 point
-
On the web there are a lot of custom player totem resource-packs available. But they all require a copy of the player-skin-texture renamed as the totem-texture. This requires reinstalling the pack every time, when you change your player-skin. So i think about making a mod to reproduce how player-head-blocks get their texture. How can i do this while using a a custom json item-model, that i created in blockbench, that a player-skin fits on? I taught about having both arm sizes in the model and find a way to detect the model width (3-pix-arms or 4-pix-arms), that the given player uses to hide or shor each arms on the model. Best regards Maxi1 point
-
1 point
-
1 point
-
I have no idea how a UI mod crashed a whole world but HUGE props to you man, just saved me +2 months of progress!1 point
-
I ended up removing both balm-forge and waystones, and it worked! Tysm for your help!1 point
-
Add crash-reports with sites like https://paste.ee/ and paste the link to it here Start with removing graveyard and modernfi1 point
-
Everything's fixed! Thank you for your help! Have a good day/night! 😄1 point
-
Thank you very much, the mod worked. I almost destroyed my computer out of anger because I couldn't find the error.1 point
-
Delete the config of the mod cupboard (config folder) If there is no change, remove this mod1 point
-
Keep this post up just in case but I'm using the curseforge launcher and it's working IM SOO HAPPY1 point
-
Add the latest.log (logs-folder) with sites like https://paste.ee/ and paste the link to it here1 point
-
1 point
-
This has already been the de-facto standard for quite a while now, but figured it would be a good idea to properly formalise it and make it clear for everyone. TL;DR: You can ask and offer support for Forge on any MC version, as long as you're not demanding it from staff and can accept that older versions may receive less attention due to people moving on to newer, shinier things. Tiered support policy There are now essentially three tiers of support: full, legacy and minimal. Full support This tier has dedicated channels for help on the Discord, gets priority for documentation, new features and bugfixes, and is generally considered the main focus for Forge development and support. Triage actively ports and backports things as needed for versions within this tier where time allows. The MC versions covered by this follows the existing "LTS" system. In other words, the latest MC version and select versions before it are covered by this tier. We recommend people consider using the newest version possible, as it's likely to be fully supported for longer. Legacy support This tier is for older versions of MC that are no longer covered by the full support tier. This tier gets less attention, but is still supported to some extent. To be clear, this is not a "no support" tier, but it is not the main focus. You're welcome to ask for help, submit PRs and help out, but please be aware that you may not get a response as quickly as these versions are generally not as popular anymore and may not have as many people around to help. Staff may still choose to work on these legacy versions and help people, but please don't demand it from them. Please note that due to the nature of the old toolchains used for building legacy versions, developing mods using the default MDK may not work. We also cannot easily publish updates to some of these old versions without your help - if you're interested in fixing this, please reach out to us. Minimal support This is rare and usually only applies to versions of MC where there's no legitimate reason to be using them. A real-world example of this is 1.20.3, which had a data loss bug that was fixed in 1.20.4 shortly after. All mods made for 1.20.3 work on 1.20.4, so there's no reason to use 1.20.3. We will help you update to the fixed version instead, but that's about it.1 point
-
Which iterates through the inventory, but you are right, one does not have to do so manually. Yea thats what i meant you don't have to do it yourself because there is a method that dose it for you.1 point