Posts by mojoroc

What gives?? been many hours now

After restoring one of our grids on the cluster, we are having some sync issues (claims & beds that are outta sync). People are saying we need to clear the Redis cache and it should fix the issue, but I don't know how to do that

Saw that too.... cant figure out what is causing the restart loop / failure though. The log files really don't tell me anything useful

I have opened a ticket.... just worried how long they take to respond (sometimes never). What did you do to resolve it?

I checked the log files for the server, and this is all I see (this is for our C1 grid):

Thu Jun 6 04:50:01 PDT 2019 atlasmain Server restart requested (Daily Restart)
Thu, 06 Jun 2019 04:52:00 -0700 Server restart requested (WINDOWS)
Thu, 06 Jun 2019 05:00:59 -0700 ni2314384_3 restarted more than 10 times in a row. There seems to be something very wrong. Stopping server. (WINDOWS)
2019-06-07 04:05:27 Server restart requested (Webinterface)
2019-06-07 04:10:57 Server restart requested (Webinterface)

Any ideas what is going on??

UPDATE: just tried restarting the whole cluster, and yet again, this server failed starting up

FYI - copying the command into your json using the grid editor works... we are now able to build on the dungeon island

but we do have the ability to add command line parameters inside the json though? Are you saying whatever we put there will be ignored?

Once we get this update (tick tock), and I want to add this setting to my json, do I need to have the "?" at the beginning inside the project properties line that contains launch parameters?

We going to get this update anytime soon?? This seems a pretty insanely long time between release and the Nitrado update no?

Hopefully we get update soon... but they added the following to launch param or gus.ini:

Server Launch params:
?DisableStructurePreventionVolumes=true

or in GameUserSettings.ini
[ServerSettings]
DisableStructurePreventionVolumes=true

Nitrado Do we have a way to put this launch parameter somewhere? Or, do I need to update the gus.ini??

Wondering is anyone knows how we might be able to undo the crab nerf setting... our whole cluster wants the old crab back. Not sure if there is a .ini setting, or if it would require a full mod

I understand you control when u update the server builds, but common, let's get this done already please. This is the key thing I want up and running from the 104.61 release: - Creatures no longer require the desired temperature after they reach 10% maturity

NOTE officials are already on v104.78… we are only 104.57

I have definitely checked the json… even posted copies of it for others to review syntax - it all checks out. But, they are just not spawning for us, or at least we have never found or seen them

Quote from DOAGEN

I think it is a known bug. Ive read something at playatlas, and yes we are experiencing it as well.

all 3 bugs, or just the names thing?

As the subject indicates, we haven't been able to fix the following 3 bugs:

Our disco zone names are NOT showing up as island overlays when discovery has been made (they USED to before mega patch)

Although double and triple checked syntax, we can find no gentle whales nor giant squids in the zones that are supposed to have them spawn (mean whales spawn where expected)

Anyone have similar? Or better yet, figured out how to get this working?

Nitrado are u pulling the latest server build?? 101.32 has actually got a fix for this very issue Mekki   DOAGEN

Most of our folks cant log in due to mismatch of client / server versions... prime time Friday evening

Are you getting the same functionality though by tweaking those settings? our folks hate the new system

Quote from DOAGEN

sorry, have no idea.

I am only aware for unclaimed

NoClaimFlagDecayPeriodMultiplier=4.0

not sure you can. See in the ini files.

I am looking at them.

found PvEStructureDecayPeriodMultiplier=1.000000

Recommend doing a back up of the ini you are changing.

Display More

Does not affect the claim flag decay unfortunately... this is nuts for our player base btw

Anyone know this?? I can't find a .ini entry to modify, yet we are only getting a 6 hour decay on our normal PVE claims.... really could use some Nitrado help here