Jump to content

Recommended Posts

Posted (edited)

Hello!

 

I'm currently running the latest version of SevTech: Ages (version 3.1.5) with all the default mods enabled, except for three mods: Better Foliage, Fancy Block Particles, and Smooth Font (as these are a little taxing on performance).

Aside from the default mods in this pack, I had only added in OptiFine_1.12.2_HD_U_F5 (clientside), which greatly helps with performance.

 

Now, after having been flawlessly running a SevTech: Ages server for almost over three weeks now and reaching the 5th Age, upon logging in a few days ago, I noticed some corruptions in the world.  After investigating a bit, I noticed basically all of the block ID's from the mod PrimalCore had been switched around (essentially they were remapped).

 

pic.thumb.jpg.0192b4f0a947ccbbbea6ef7b0d939aef.jpg

 

As seen in the picture here, what is supposed to be Terra Clay has converted to Ovis Atre Wool.  Also seen to the left, Wet Mud converted into Inaris Carpet, and in the background, Rushes converted into Jack o'Lanterns.

After looking at the ID mappings for a bit, I noticed it was the third digit that shifted down by one.  For example:

 

Wet Mud       --->  Inaris Carpet              (ID:2642 --->ID:2632)

Ortho Stone  --->  Oak Drying Rack       (ID:2595 --> ID:2585)

 

I'm not sure how this happened and I don't see a good reason as to why it should have happened, but it seems to have happened sometime when the server was empty during a constant uptime period of around 5 days.  I have also been doing proper server shutdown procedures (typing stop to close it).

While this is obviously a corruption, are there any suggestions on how it might be fixed?

Backups are out of the question because AromaBackup was not personally configured and so it only had backups ranging from 1-4 hours ago (my fault).

 

This corruption also takes place in the End and Nether where there are a decent amount of blocks from PrimalCore in the environment.  I think the easiest fixes for those dimensions would be to just delete the DIM1 and DIM-1 folders in the save file to reset those dimensions.  But are there any suggestions on how this might be fixed for the Overworld?

 

Also, just to be clear, this corruption happened in chunks that had been previously generated (no corruption found in discovering new chunks). 

One thing I tried was using the /worldutils blockreplacepairs command from the World Utils (https://www.curseforge.com/minecraft/mc-mods/world-utils) mod and it works somewhat, but it doesn't seem to have to have a very long range, even though it says it should replace all blocks throughout all previously unloaded generated regions.

 

-Thanks

Edited by Rissa-
Posted

1.12 is no longer supported on this forum.

Please update to a modern version of Minecraft to receive support.

This is my Forum Signature, I am currently attempting to transform it into a small guide for fixing easier issues using spoiler blocks to keep things tidy.

 

As the most common issue I feel I should put this outside the main bulk:

The only official source for Forge is https://files.minecraftforge.net, and the only site I trust for getting mods is CurseForge.

If you use any site other than these, please take a look at the StopModReposts project and install their browser extension, I would also advise running a virus scan.

 

For players asking for assistance with Forge please expand the spoiler below and read the appropriate section(s) in its/their entirety.

Spoiler

Logs (Most issues require logs to diagnose):

Spoiler

Please post logs using one of the following sites (Thank you Lumber Wizard for the list):

https://gist.github.com/100MB Requires member (Free)

https://pastebin.com/: 512KB as guest, 10MB as Pro ($$$)

https://hastebin.com/: 400KB

Do NOT use sites like Mediafire, Dropbox, OneDrive, Google Drive, or a site that has a countdown before offering downloads.

 

What to provide:

...for Crashes and Runtime issues:

Minecraft 1.14.4 and newer:

Post debug.log

Older versions:

Please update...

 

...for Installer Issues:

Post your installer log, found in the same place you ran the installer

This log will be called either installer.log or named the same as the installer but with .log on the end

Note for Windows users:

Windows hides file extensions by default so the installer may appear without the .jar extension then when the .log is added the log will appear with the .jar extension

 

Where to get it:

Mojang Launcher: When using the Mojang launcher debug.log is found in .minecraft\logs.

 

Curse/Overwolf: If you are using the Curse Launcher, their configurations break Forge's log settings, fortunately there is an easier workaround than I originally thought, this works even with Curse's installation of the Minecraft launcher as long as it is not launched THROUGH Twitch:

Spoiler
  1. Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge)
  2. Make a launcher profile targeting this version of Forge.
  3. Set the launcher profile's GameDir property to the pack's instance folder (not the instances folder, the folder that has the pack's name on it).
  4. Now launch the pack through that profile and follow the "Mojang Launcher" instructions above.

Video:

Spoiler

 

 

 

or alternately, 

 

Fallback ("No logs are generated"):

If you don't see logs generated in the usual place, provide the launcher_log.txt from .minecraft

 

Server Not Starting:

Spoiler

If your server does not start or a command window appears and immediately goes away, run the jar manually and provide the output.

 

Reporting Illegal/Inappropriate Adfocus Ads:

Spoiler

Get a screenshot of the URL bar or copy/paste the whole URL into a thread on the General Discussion board with a description of the Ad.

Lex will need the Ad ID contained in that URL to report it to Adfocus' support team.

 

Posting your mod as a GitHub Repo:

Spoiler

When you have an issue with your mod the most helpful thing you can do when asking for help is to provide your code to those helping you. The most convenient way to do this is via GitHub or another source control hub.

When setting up a GitHub Repo it might seem easy to just upload everything, however this method has the potential for mistakes that could lead to trouble later on, it is recommended to use a Git client or to get comfortable with the Git command line. The following instructions will use the Git Command Line and as such they assume you already have it installed and that you have created a repository.

 

  1. Open a command prompt (CMD, Powershell, Terminal, etc).
  2. Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in).
  3. Run the following commands:
    1. git init
    2. git remote add origin [Your Repository's URL]
      • In the case of GitHub it should look like: https://GitHub.com/[Your Username]/[Repo Name].git
    3. git fetch
    4. git checkout --track origin/master
    5. git stage *
    6. git commit -m "[Your commit message]"
    7. git push
  4. Navigate to GitHub and you should now see most of the files.
    • note that it is intentional that some are not synced with GitHub and this is done with the (hidden) .gitignore file that Forge’s MDK has provided (hence the strictness on which folder git init is run from)
  5. Now you can share your GitHub link with those who you are asking for help.

[Workaround line, please ignore]

 

Guest
This topic is now closed to further replies.

Announcements



×
×
  • Create New...

Important Information

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