I can confirm that world regen is severely affected by the change - not quite sure if it is lag related (so client side only) or the server isn’t able to keep, but I tested it with the type of farming where you keep spamming regen bombs
I farmed peat in my peat regen farm on Refgar (I’m on Europe) with a forged topaz shovel (speed 118). It worked as always, no unexpected draw delay or anything. Regen bomb, too, worked as expected. I did not notice any difference.
And portals in the Dragon Hub still take forever to load (2 seconds) for me.
He said he was taking it down to 20. Maybe an increase up to about 30 would smooth things out?
I did some testing last night. I mined, bombed some areas, spawned a few meteors, went through many portals, farmed a gleam ball and saw another person running and it all looked normal on my end. I’m going to check it again today when the servers are a little busier also.
I didn’t see any issues, but I’m also on a very fast connection. I’ll give it another try in a bit.
As Far as the mass mining that squeekums mentioned I have seen that for several weeks. It is like a small hesitation as it hits and gathers the blocks. So to me that is not a new thing. The other thing was the draw distance that Catfud mentioned it seems sluggish when loading the surrounding area. So I agree these are both a thing but don’t believe these are new.
well it seems to be related to your ping and since that increased significantly on some worlds… I also saw it a lot more on streams from console players, so it’s definitely not a new thing, but now everyone gets it it seems :-/ I definitely never had that problem in the past.
I expect this change will increase the minimum ping time, but decrease the amount of pings that are significantly higher than the minimum.
When you’re waiting on a server process, first it has to wake back up, then it has to do the thing.
Total Time = Sleep Time + Execution Time
Counterintuitively, increasing Sleep Time can decrease Total Time, because cpus have a penalty for context switching. When processes sleep a little longer, it frees up the cpu for additional work (maybe like portals). But it also means processes sleep a little longer before they reply to pings.
I’d expect the time for a ping reply to increase because it’s mostly Sleep Time, which just got increased.
Yeah, I’m in rural Australia, so a very slow connection ‘and’ forget about it when it rains.
Will you please let us know what the change entailed??? You said “update frequency” with no actual details around it. Then you go make a change to LIVE servers again with on details on what is changed. This is very concerning to see us adjusting stuff and just hoping and praying things don’t blow up. The servers have a huge host of underlying things they do and if you don’t know what you are doing you can make things worse.
A slight delay to help CPU processing
That wasn’t I was talking about when I asked him the first question. He wouldn’t have been asking what the “update” was for if the GIT code provided the explanation. Because there was no explanation it had much more functionality behind the “updates” and what they do. Just changing things on a production server really is reckless especially when you don’t understand the code.
Jumping to the conclusion that it wasn’t tested in a non-prod environment is a little hasty.
Understanding the code is one thing, but they do own the code and while I agree changing things in a prod environment is bad I’m just glad there is work being done.
Also, I’m willing to bet James left very little in regards to how everything works and why a minor change was done on GitHub. It’s also something that could be easily reverted.
I wonder what could be taking 2 seconds. That seems like longer than I’d expect.
Most have reported faster portal loading. But the server reset did throw hunts off. Usually when I prep my planet I get a minimum of one meteor per region and several with multiple/ Then once we start the hunt we get a bonus or two before crossing into the region, then a few regular one. In the first two regions we usually see anywhere from 8 to 11 meteors. Today the warm up and hunt were way off. I heard a few others have been slow for meteors as well since the update. Hope it is something that clears up by next weeks hunt. We will let you know for sure. Any other hunt runners if you would please kind of see how they go for you as well. If you see some big changes I guess let them know. Hope it was just the reset but never seen this adverse change after a reset. That being said I don’t know how a frequency in how often the server updates could affect it. All I know is it caused a lower Oort count and creature parts due to meteors not falling to the norm.
Thanks for letting me know. Maybe it’s rolling dice every update. I’ll look into it and get it fixed.
I’ve suspected this from the beginning.
well, we are still here, its never too late to learn right?
every single action from their side, every single add or change that influence the game will be immediatly reported by us, who will be better testers of changes than long last dedicated players who love the game?
im sure we are willing to test everything they will be trying to do, to see how it works right?
So you are going to be critical of me of jumping to a conclusion and in the same post just ■■■■ on James because you didn’t like him and assume that he didn’t turn anything over? That is pretty ridiculous. I have 30+ years in IT development, systems management, and enterprise architecture in a top 100 company so I’m gonna be a bit critical when I see a Dev come in, do a quick post, wait a few days, then change a setting in Prod because they “feel” it is off just AFTER a screwed up “exo” released colors that had not been correctly unlocked.
- Where was the post for the test servers being up and us being able to log in and try the new code?
- How long was the code running on test and what was the user load?
It didn’t happen so of course I was going to say something about it.
Going in and just changing settings because you feel that the CPU time slice is too small is not development nor maintenance. We had those settings for a very long time and more than a few experienced programmers that were with that game from the start still on the team. There is a very likely hood that the setting was put that way for a reason and not just that the UK team was more stupid than the US team.
I’m all for changes but we have someone making changes that clearly doesn’t UNDERSTAND a large part of the code or why things are set the way they are set. I’d much more have liked to just see them go through code, ask questions, and start to understand how the game actually works. Sure, we have less people playing than before so maybe a few things can be adjusted to make the experience better after discussion. But, this game has some very complicated systems for regeneration and other components that could ultimately get worse if things go haywire. The game was never really sent through a full optimization path because of how release and development went.
I’m very happy to see we have someone around now versus complete silence. Even though, it is pretty bad that there was NO POST or any details being presented on the person or why things are even being touched. We need a regular reboot schedule and should have a list of critical issues to be fixed not just throwing darts because code looks off.
You want honesty?
They abandoned the game and their responsibility to take care of and fix things to work on another game. At the first big chance to jump ship…THEY DID.
I’m not beholden to them at this point. Especially after the YEARS of silence. I’m not really a supporter of Monumental since they were just as guilty of radio silence.
But now, changes are being made, hopefully for the better. They make break a few eggs along the way, but it’s better than nothing at this point.
And you don’t know what @jon-eric level of skill is. You’re making assumptions and quite honestly, making a fool of yourself.
So either sit back and wait, offering helpful suggestions…or go back under your bridge, troll.
Seems smooth to me. Nice work.