Forgotten Relics Updated to 2.6.0-Beta-3 Looking For Players

[odd marten]

Side note

This server is welcome to one and all and to everyone who wants to join and have people to play with. Your more than welcome to form groups and do ur own things

Myself and two others one being a Completely New person to Gregtech

One being a Hardcore Sweat GT player that has done Stargate

are going for the Star gate role following the rule guide lines https://docs.google.com/document/d/1Iww1FNLkCuun6s6LW7Q6_1Z1aldtxYeRxYOeq_P-vK8/edit

We will be looking for two more ppl, but those two ppl Will have to go tho testing from us.. if you want to join..

If you dont want to go tho the testing and just play on the server with us. Your welcome to join

[odd marten]

We are starting <t:1712599200> so anyone wants to join still we will be looking for players up until EV will be keeping tabs here ❤️

[odd marten]

We are also Running 2.6.0 beta version of the pack ❤️

[north rivet]

@odd marten Hey, are you aware that there's a GTNH fork of Dynmap called GTNH-Web-Map? Based on various rendering issues I'm seeing, I'm guessing you're not using it? If not, is there a reason why not?

[odd marten]

First off, been eons since i visit 1.7.10 / 2nd off i did not know of this.. / third off dont use dynmap alot

Do i need to re render ?? if i switch now ?

[north rivet]

https://github.com/GTNewHorizons/GTNH-Web-Map/releases

You can keep your current render, but it wont fix the rendering issues until it's redrawn. But the terrain issues aren't super bad (bamboo trees look weird, as do IC2 rubber trees and various plants) so it's not a huge deal, but GWM has waaay better support for various modded blocks like GT machines/cables/pipes, AE2 networks, ArcitectureCraft shapes, Carpenters Blocks and so on.

[odd marten]

So basically what im hearing.. the rendering issue need to be redrawn.. aka i need to re render the whole map to fix said issues ?

and this is basically replacing Dynmap mod correct ?

[north rivet]

Yes. But again, those issues aren't that bad. Any bases being built will however greatly benefit from it. It'll keep using your existing images until those chunks are redrawn.

It's a fork, yes. Almost a drop in replacement, you must however remove/rename your renderdata/custom folder. GWM have those built in for GTNH and various other popular 1.7.10 mods.

[odd marten]

Wdym rename ? and your talking about the Dynmap folder ?

[north rivet]

In your server folder, you have a Dynmap folder. Inside it, there's a renderdata folder, and inside that, I'm guessing you have created a custom folder where you've placed a bunch of .txt files from DynmapModScraper. That step is not needed with GWM as it has those .txt files built in. In fact, you must remove them as they'll override the improved/fixed versions that GWM has built in.

[odd marten]

i never created a custom folder..

[north rivet]

What's in modsupport?

[north rivet]

Wait. What version of Dynmap are you using?

[odd marten]

Just updated the server with the GTNH-web-map fork version

seem its still rendering the surface atm

might need to do a /dynmap updaterender

after its all done to fix those issues u mention

[north rivet]

Interesting, I did not know that beta shipped with as much mod support as it did built in. It's extremely outdated with respects to GTNH though, and doesn't contain all mods, so GWM is still recommended. 🙂 Normally when you install Dynmap on a modded server, you would run DynmapModScraper (DynmapBlockScan on newer versions) to get definition files for all mods in your packs, which you then place in renderdata/custom to make your Dynmap installation support them.

I'm not sure what updaterender does, but I'd probably run /dynmap fullrender ForgottenGTNH:surface when you're done.

It should be able to just run in the background, it typically has no noticeable impact on server performance anyway, especially early game.

[odd marten]

Good to know

[odd marten]

@north rivet mind if i get some help ?

[north rivet]

What do you need? (It's almost 1am, so limited)

[odd marten]

my server was working perfectly fine... and now it wont even launch there no crash report either ?

only log i got is this

[22:51:38] [Server thread/INFO] [FML]: The state engine was in incorrect state ERRORED and forced into state SERVER_STOPPED. Errors may have been discarded.
[22:51:38] [Server thread/INFO] [FML]: The state engine was in incorrect state ERRORED and forced into state AVAILABLE. Errors may have been discarded.

these are the last two lines i get before it restarts itself..

is the forge corrupted ?

[north rivet]

It looks like ForgeEssentials errors out

[odd marten]

so Forge Essential got corrupted ?

[north rivet]

[22:45:59] [Server thread/TRACE] [ForgeEssentials/ForgeEssentials]: Sending event FMLServerStartingEvent to mod ForgeEssentials
[22:45:59] [Server thread/ERROR] [ForgeEssentials/ForgeEssentials]: com.forgeessentials.jscripting.ModuleJScripting@6b7364fe
[22:45:59] [Server thread/ERROR] [ForgeEssentials/ForgeEssentials]: com.forgeessentials.jscripting.ModuleJScripting@1bc9f973
[22:45:59] [Server thread/ERROR] [ForgeEssentials/ForgeEssentials]: Error parsing data file "/home/container/./ForgottenGTNH/FEData/json/Grave/[226,40,451,dim=0].json"
[22:45:59] [Server thread/INFO] [STDERR/ForgeEssentials]: [java.lang.Throwable$WrappedPrintStream:println:749]: com.google.gson.JsonSyntaxException: java.io.EOFException: End of input at line 24 column 23

I think a grave got corrupted

With the path /home/container/./ForgottenGTNH/FEData/json/Grave/[226,40,451,dim=0].json

I've never used ForgeEssentials myself though

I think

[odd marten]

let me check

i reuploaded the forge / the forge mod

and deleted that grave

see if that works ig ?

hardcore blindness with a gun over here

hopefully it hits xD

[north rivet]

It's my best guess. Though I'm definitely not the right guy to ask TBH. I'm the web map dev, I'm more or less clueless about the rest.

[odd marten]

yep

idk what it was

but doing those three things

fixed it

[north rivet]

Nice! 🙂

[odd marten]

Ty ❤️

[north rivet]

🙂 Good luck with your playthrough! Also, note that you are (according to the description) playing a beta version of the pack. Some issues and possibly crashes are to be expected. I highly recommend upgrading to 2.6.0 stable when it comes out. For most packs, that "beta" notation is more or less symbolic, for GTNH it's very real. 🙂

[odd marten]

ye i will do that

also doing the SG Role

anything i need to know about that beside the rules on the google doc ?

[north rivet]

The basic thing is don't cheat. If possible, try posting some form of progress pics in the relevant channels. If nothing else, it might be fun for you to look back at etc. 🙂 With that said, I'm not in any way involved in the "judging" or whatever. It's up to the admins (red names) and team members (blue names) to decide those things. I'm just writing code. 🙂

[odd marten]

Ah

Ty ❤️

[north rivet]

BTW, let me know if you encounter any issues on your map. I'm actively developing/maintaining/supporting GWM, so all feedback is appreciated. 😉

[odd marten]

Sure

will do

[nimble mortar]

@old summit possible issue with FE on 2.6. Not sure if you wanna take a look at what’s going on

[old summit]

My hunch is it was just an issue with the currupted grave. Gson errors are known to crash FE if something is corrupted. (this is intentional since we don't want to delete the file if it is corrupted but instead leave it so the user can repair it if they need to)

[north rivet]

Seems somewhat reasonable, but perhaps backing up the corrupt file and either resuming or presenting a more visible and actionable error message would be preferable to bricking the server, at least in case it's something like a grave..?

That may have come out significantly less constructive than I indended it to. 🤣 Read it more in a constructive brainstorming kind of voice than in and overly critical voice. 🙂

[odd marten]

@north rivet just letting you know

it happen again

removed the grave json file fixed it again

here the log

but basically

[04:35:38] [Server thread/TRACE] [ForgeEssentials/ForgeEssentials]: Sending event FMLServerStartingEvent to mod ForgeEssentials
[04:35:38] [Server thread/ERROR] [ForgeEssentials/ForgeEssentials]: Error parsing data file "/home/container/./ForgottenGTNH/FEData/json/Grave/[209,64,59,dim=0].json"

what caused it

the player who died and left his grave

said he collected everything from it..

but the fence and head was left behind.. and didnt disppear

which i believe what causing the crash..

[old summit]

hmn... strange, thanks for letting me know

that definitly shouldn't be happening

open the contents of the grave file and post them in here

I wonder if there is some bug that is causing the grave to not delete the file

Worse case scenario, just disable the entire afterlife module. It isn't really needed since openblocks graves is in the pack.

To disable, go to ForgeEssentials\main.cfg and find the afterlife module in the config file

[amber harness]

Brokie detected

[odd marten]

Will do if one ever shows up again I been making sure players collect everything in the grave

So if I get one I will let you know

[odd marten]

Also this guy is living in sorts 3 chunks atm due to the first week of the server only having 3 chunk loading

He also almost MV tier atm

[old summit]

if you don't have it, it is better to just disable the afterlife module all together. Clearly it is causing an issue and multiple grave mods don't tend to play well together regardless.

[odd marten]

@old summit Just letting you know i have the file now...

Sorry about responding so late

What i think going wrong is that its missing a } at the end...

So...

Adding a " } " at the end of this .json file..

basically Fix the issue...

now new graves spawning about.. im pretty sure their going have the same issue

so idk if that something to do with how it codes graves.. and what basically inputting or misinputting the } at the end.. but that fixes it for what ever help that is.

[odd marten]

Forgotten Relics Official Launch Looking For Players

[old summit]

sounds like a strange corruption issue but the fact it is just missing the ending } is very strange. I would have expected it to be empty or something...

[odd marten]

Ye i have no idea what causes that to not have the } at the end..

Just happy i was able to help if u need anything else just let me know ❤️

[north rivet]

Does it write it as some form of stream that never gets properly closed/flushed in the end or something perhaps?

[old summit]

wouldn't be surprised... It just hasn't happened before in my testing but a similar change was made on 1.17... https://github.com/ForgeEssentials/ForgeEssentials/pull/2669/files#diff-e5c013a77a37f64fed8dd462309cfefcfb6106276efdf76a4843d037d4e0eb2dR131

[north rivet]

If you're referring to the added out.flush() in DataManager.save(Object, File), then yes, that could very well be it. https://github.com/ForgeEssentials/ForgeEssentials/blob/1.7.10/develop/src/main/java/com/forgeessentials/data/v2/DataManager.java#L121
https://github.com/ForgeEssentials/ForgeEssentials/pull/2669/files#diff-e5c013a77a37f64fed8dd462309cfefcfb6106276efdf76a4843d037d4e0eb2dR131

The comment does say something about it being required in newer versions of Java. Are you testing with modern Java? @odd marten are you using modern Java on your server?

[odd marten]

testing with java 17

17.0.10

[north rivet]

But are you using that on your server as well?

[odd marten]

1 sec let me double check

[north rivet]

My guess is no. Damn, that might have explained it.

[odd marten]

ya its running java 8

as i dont have the ability to run Java 17..

on the server

[odd marten]

because basically

when i run Java 21 Zulu or Java 8 Shenandoah with the jar lwjgl3ify-forgePatches.jar i get this message..

which i assume i have to add -Djava.system.class.loader=com.gtnewhorizons.retrofuturabootstrap.RfbSystemClassLoader to my JVM flags... which is a complicated story..

[old summit]

yea, there are a whole bunch of flags you need to add for Java 17+. (As to J 17, I run that on my server but never ran into the issue so I was confused too.)

I am going to add a flush later when I get a moment because it doesn't hurt to add it.

[old summit]

Btw, for Java 17+, these are the args you need to use for it. https://github.com/GTNewHorizons/lwjgl3ify?tab=readme-ov-file#server

(it is best to download the Java 9+ version of GTNH since it has the required mods for J17)

[old summit]

Btw, I added the flush to 1.7.10. Hopefully it will prevent the issue from happening. https://github.com/ForgeEssentials/ForgeEssentials/actions/runs/8714155106 Also, keep an eye out for messages in the form of Error saving data to as cases like those may prevent the object from fully saving.

[odd marten]

Going be awhile before im able to update the server due to some "other Reasons" i rather not speak about.. but for now i will just disable the afterlife module which is this right ??

#1226555797014712402 message Also for anyone who decides to pop in and doesnt want to scroll up to the top

[old summit]

yep, and to be honest, you might be better off. FE's graves are nice since they give you a GUI to grab your items like a chest but openblocks graves work just as well.

[odd marten]

Alright Thank you

[old summit]

np

[odd marten]

Who do i talk too about a bug btw ?

I just found one with this recipe.. not giving C02 gas

Here the phyically proof

[old summit]

hmn...

what is your muffler hatch tier

I think the output depends on the tier

but it should still produce gas on the lowest tier (at least it did in the past)

however, I know the tooltip said that that teir gave 0 percent output.

So, it is possible they fixed a bug

Regardless, this is a question to ask in #beta-testing or #mod-dev

As far as GTNH bugs though, I can't really help you much cause I am not a GTNH dev

[odd marten]

lv muffler

[odd marten]

also dont got access to the first link but i do have access to the 2nd link

[brave arrow]

As spacebuilder mentioned depending on the mufflers tier the output is decreased but i dont remember it being completely 0%.
If it is indeed a bug it might have been already fixed with Beta 3 but wouldnt hurt to test this in beta 3 with different mufflers.
I may have a look into it tomorrow 🙂

[old summit]

I do remember the book saying that the LV would cut the output to 0 but it still working

[old summit]

first link is the beta testing channel. Figured you wouldn't have access to it. (it is probably the more appropriate channel since you are playing with the beta version of the pack)

according to the tool tip, the muffler hatch is supposed to give 0 percent but it gives 5 percent. (the rate the advanced muffler hatch advertises for LV tier)

in testing, both the basic and advanced muffler hatch gives 5 percent at the LV tier.

in contrast, the MV muffler hatch gives 13 percent as advertised and the advanced give 41 percent.

to test things more @odd marten I recommend making an advanced muffler hatch of the LV tier

[odd marten]

Alright ty i will do that when i have more time to play appericate it ❤️

[old summit]

np

Personally, I am not sure it is a bug or they fixed a bug to make the advanced mufflers more required in LV

[brave arrow]

nvm LV Mufflers actually do not recover any CO2 at all The Advanced one should give 5% at least

[odd marten]

ye

i switched it and got C02 Gas from it

💀

gotta love that 0% output ig

[odd marten]

Forgotten Relics Official Launch Need 1 More / Currently Have 4

#1226555797014712402 message Also for anyone who decides to pop in and doesnt want to scroll up to the top

[odd marten]

Forgotten Relics Updated to 2.6.0-Beta-3 Looking For Players

[old summit]

Btw, I was able to figure out what the issue is with the graves. It was actually an issue with the forge bundled GSON due to the library needing some aspects of reflection that were not in the add-opens specifiers.

To fix, add the following to your java9args file.

--add-opens
    java.base/java.lang.ref=ALL-UNNAMED
--add-opens
    java.base/java.util.concurrent.locks=ALL-UNNAMED```

[odd marten]

alright thanks

but we havent had any issues.. since we updated to Java 21