Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

Coraline77447

Members
  • Posts

    10
  • Joined

  • Last visited

Posts posted by Coraline77447

  1. I was gonna type a pretty long message for you diesieben07 and the rest of the forge forum team but since y'all have been treating me with silence and not being positive and kind that now y'all don't deserve my lengthy important message since all of you would just ignore me anyways like how you all have been for the last week!

    I'll just be in my newly created 1.16.5 modded world while waiting for forge's first 1.17.1 stable release!

  2. I've took a look and by the looks of things that you were trying to continue to play in 1.16.5 modded after trying out 1.17.1 modded and forge 1.17's outdated data pack did this?

    Btw to update a mod's data pack is to manually change the mod's pack formatting number in the pack.mcmeta file in a file manager like 7Zip.

    I've done so with Biomes O' Plenty's latest 1.17 update since they're still using pack format 6 instead of 7.

    But for 1.16.5 mods you'll have to change whatever the mod's pack formatting number is to 6 so that they're not outdated anymore and notify the mod creator/owner kindly to update their data packs to the correct pack formatting number to match with the vanilla data pack formatting number.

    Also I'm still waiting for forge 1.17 to update it's data pack so that I can enjoy modded 1.17...

  3. I've been having this same issue for the past 3-4 days now with Forge's data pack being outdated (all that they just need to do is to change it's pack formatting number from 6 to 7).

    I can't create a new modded 1.17.1 singleplayer world and had to delete my first 1.17.1 modded world due to Forge's outdated data pack.

    Been going back to 1.16.5 modded for now till they update Forge's data pack.

  4. Here's the image that I'd tried to add on here;

    https://imgur.com/a/z7D3h26

    Btw that screenshot was taken a few days ago but the main issue (above my data pack comment issue) does reappear which I would have to update forge on my end to workaround it till it happens again the next day.

    But as I've said in my data pack comment above that I can't make a new world now cause Forge's data pack is outdated.

    Also I'm not registered on imgur yet and my image post on there is set to private for safety/security reasons so I don't know if you can view my screenshot on imgur. 

  5. Even tho what I'm about to say should be in it's own post but when creating a new modded world in the data packs screen I see that Forge 37.0.10's data pack isn't formatted to 7...

    Since minecraft 1.17 requires data format of 7 now, so could you guys please update Forge's data pack format to 7? Please?...

    Had to delete my modded 1.17.1 world cause of this...

    I wanted to change forge's data pack format number to 7 just like how I did with some of the mods that I'm playing with but I don't know where Forge's pack.mcmeta file is and it's NOT my responsibility to do that anyways...

    Btw I didn't touch or do anything when I was searching for Forge's pack.mcmeta file in 7Zip file manager and I'll never do that again, ok?....

    Also I can't create a new modded world now cause of Forge's outdated data pack format number so I'll just go back to 1.16.5 modded till 37.0.11+ with it's data pack format number being at 7....

  6. Strange, I can't seem to upload the screenshot of my launcher which is normally my vanilla launcher that I've tried to launch forge 1.17.1 37.0.2 in it...

    I'm getting an error message when trying to upload the screenshot....

    Btw I'll be trying Forge 37.0.8 with no mods (especially without OptiFIne) to see if It'll load right now.

     

    UPDATE: Forge 37.0.8 with no mods has loaded successfully for me but now I'll be testing if it'll load with the mods that have been ported to 1.17 already which is 25 mods atm plus OptiFine.

    NOTE: If it crashes cause OptiFIne isn't compatible with forge (yet) then OptiFine will be taken out till both are compatible with each other. 

     

    UPDATE 2: Forge 37.0.8 with mods was loading but crashed cause of tool belt mod with its rendering models and what not, so I'll report that with the dev(s) of Tool Belt mod.

     

    In conclusion, Forge 37.0.8 is working for me. The issue may have already been resolved between 37.0.3 and 37.0.8.

    I know that I could've waited for an update that would've fixed my issue that I was experiencing but I really wanted to make a modded 1.17.1 world with the 25 mods that have been ported to 1.17 that I've enjoyed playing with in 1.16.5 modded (even tho I was playing with upwards of 50+ mods with somewhat good framerate), which was why I created this report/post in the first place.

    I really didn't want to create this post in the first place cause of the bad experience that I've had in the past as of my first post on the Forge Forums but I know that Forge 1.17 is in beta right now and that's ok which is why us minecrafters like me are doing the bug testing while wanting to play 1.17 modded so that the devs can fix the bugs we find.

    You can close this report/post respectfully now since I'm not experiencing this issue in 37.0.8.

    Also I'm sorry for wasting your time with this post....

  7. I've been trying to play modded 1.17.1 for at least an hour now, took out all the mods in the mods folder (especially OptiFine) and my game works fine as of Minecraft 1.17.1 and with just OptiFIne 1.17.1  but when I try to play Minecraft with Forge 37.0.2 without OptiFine the game still crashes with exit code 1.

    Haven't tried to just load forge with no mods yet but I already know that forge would fail to load still...

    There's no crash report or log and the debug logs aren't going to help as of the files themselves because I viewed them myself and only saw two or four lines of info and the latest log only has two lines as well.

    The only log or debug log that I can provide is through screenshots;

    1278801948_Screenshot(11).thumb.png.55536d99c51af3230f4cfd87f84d2667.png

    1805808523_Screenshot(12).thumb.png.7c1cc36aa20e64e3689c904008d47013.png

    1742487788_Screenshot(13).thumb.png.f2e607e8d1fa73b33c72ada547401004.png

    But if you still insist of me sending the debug files then here, see for yourself to see what I saw within them then;

    latest.log

    debug.log

    This info below came from a source that I'm not willing to tell but it should help tho... 

    [Launcher] Starting Minecraft 1.17.1-forge-37.0.2...
    [Launcher] Launching in: C:\Users\Pwrus\AppData\Roaming\.minecraft
    Starting garbage collector: 66 / 290 MB
    Garbage collector completed: 45 / 290 MB
    [Launcher] Processing post-launch actions. Assist launch: true
    ===============================================================================================
    WARNING: Unknown module: cpw.mods.securejarhandler specified to --add-exports
    WARNING: Unknown module: cpw.mods.securejarhandler specified to --add-opens
    Exception in thread "main" java.lang.ExceptionInInitializerError
        at cpw.mods.jarhandling.impl.Jar.<init>(Jar.java:90)
        at cpw.mods.jarhandling.SecureJar.from(SecureJar.java:58)
        at cpw.mods.jarhandling.SecureJar.from(SecureJar.java:50)
        at cpw.mods.jarhandling.SecureJar.from(SecureJar.java:42)
        at cpw.mods.bootstraplauncher.BootstrapLauncher.main(BootstrapLauncher.java:54)
    Caused by: java.util.NoSuchElementException: No value present
        at java.base/java.util.Optional.orElseThrow(Optional.java:377)
        at cpw.mods.jarhandling.impl.SecureJarVerifier.<clinit>(SecureJarVerifier.java:16)
        ... 5 more

    So until this issue get's fixed for good, I'll be going back to Forge 1.16.5 36.0.62 or whatever version it's at currently in...

  8. I know that I'm not supposed to use cracked launchers but from when I started playing java edition back in 2016 or so till near the end of 2020 that I can't buy Minecraft since I don't have any money but someone on a discord server was kind enough to buy me the game for my main Microsoft account so that I wouldn't have to use Tlauncher anymore😥😥😥

     

    Btw I would like to bring an update about my report that forge 35.1.35 and 35.1.36 aren't working for me cause I think I have a mod or mods that are not working past forge 35.1.34 anymore.

     

    Since I may be the only one who's experiencing this problem, so even tho this problem is forge related but a mod may be causing this issue if one of my mods not working with forge past 35.1.34..

     

    Unfortunately I'm not willing to go through my mods folder and butcher it and accidentally on purpose kill my newly created worlds just to find out which one of my mods that I'm using is not working past 35.1.34 that is causing this problem to occur as of right now cause I just want to start my modded minecraft play session now...

     

    Also I'm sorry for sayin that I'm a cracked client/user even though I do officially own Minecraft now (thanks to a friend from a discord server that I joined a few weeks ago) as of my main Microsoft account😥😥😥

     

    But I'm still going to use Tlauncher cause when I used the official launcher that I couldn't see Project MMO's texts on my screen in-game...

     

    Even when I turned on and off the skills GUI for project MMO mod I still couldn't see the skills on my screen except for when I use Tlauncher which is why I'm still using Tlauncher or else I would've deleted Tlauncher since I officially own the game now and that can't accumulate as much RAM as I used to since the official launcher let's me accumulate up to 3072 (2997 for Tlauncher)😥😥😥

  9. Hi, I'm experiencing Ticking World crashs in the latest version of forge (forge 35.1.36 for Minecraft1.16.4, as of my cracked client for Tlauncher but I do have the official launcher but I use Tlauncher for modded. 

     

    Anyways this ain't important, what's actually important is my report about what's going on with the latest version of forge for me).

     

    When I tried to load into my modded survival world before deleting it due to having thoughts about this being mod related that an entity from a mod that I had recently uninstalled was causing the ticking world crash.

     

    Then I tried to make a new fresh modded world and the new world instantly dies right before I was even able to spawn into the world (ticking world crash).

     

    When I created a new world with forge 35.1.32 I was able to spawn into the new world which was when I discovered that my ticking world crashs are Forge related and are only happening in Forge 35.1.36.

×
×
  • Create New...

Important Information

By using this site, you agree to our Privacy Policy.