I just rejoined the game after a long time away and I've been setting up individual rooms to focus energy on so as to level them up as quickly as possible to compete with the older more established players. The journey from fledgling to maxed out rooms is long and tedious and the only way to speed it up is to focus my resources. From the standpoint of new players with limited code bases, this nerf on terminals looks to limit my options for leveling my rooms up after a respawn and looks to impact new players with no means to use power creeps in a severe way.

It is already very hard to quickly come back after a wipe and transfering all my energy through terminals to a focus room is required to speed that up at all. Using a leg force of transports is a huge CPU and Spawner hit for a new player and is thus not much of a solution.

I urge you to consider the impact of this decision to limit energy through terminals on respawning / newer players.

@mashee

I'll give that a try. TY

Ooops! Just started getting a "Memory Error". "To many tabs are open" error in the Chromium browser.

The only way to fix it was to close and reopen the browser.

The same Chromium browser had been running all afternoon and just started getting the error.

Update,

I ran the Chromium client all day since my last post. I've been doing everything. In and out of rooms, building, selecting troops, ect... with no issues except ---

Every once in a while the page will get an "Oh Snap" error and both the main page and the console page I have on the second monitor. If I refresh the main page it will come back up just fine. The console page on the second monitor must be closed and reopened from the main page to fix.

That's it. I will continue to run the Chromium client for the next couple of days, but it looks to be mostly stable and working fine.

Note that I solved my problem with the Steam client and committing code via a work around. I keep the Steam client open on an empty highway page and minimized in the background. It will do the auto commit for me. I then run the game on the Chromium client which works correctly. I edit my code in Webstorm and the Steam client commits it. The game runs just fine through it all on the Chromium browser.

I will stop posting on this thread now unless you need something more from me. I will only post back if something different happens on the Chromium client.

@artch

OK, I've been running the Chromium client as asked for about an hour now.

My thoughts:

I'm not sure, but I think the performance is actually better than vanilla Chrome. I never had it slow down and movement between rooms seems to be very fast. My cursor never slowed down and busy rooms are not slow.

I did have one "Oh snap!" page crash where the console window on the second monitor and the primary display page both crashed at the same time. I hit "reload" on the primary page and it came right back up to where I was. I had to close and then reopen the console on the second monitor.

I will continue to use Chromium for the game over the next couple of days in case you all have metering on it or something you are looking at.

@artch

I can do that. I did not realize I could provided needed feedback to you. I'm testing now via the Chromium browser.

Is there anything you would like me to look for or just report back with basic performance impressions?

@artch @tedivm

Well, you have been proven correct. The Steam client just died, so the issue has not been resolved.

OK, how do I fix my Steam client? That's where my problem exists. Not with running under Chrome. Running the game under Chrome works fine.

I'm using Webstorm and need to figure out how to commit code with it then If i'm going to be forced to use the Chrome browser to play. The steam client auto commits but when I use the Chrome browser that mechanic does not exist. I have not yet figured out how to commit my code with Webstorm.

@artch

It was not a reboot as the issue has been happening for the last couple of days and I have rebooted multiple times.

I will be messing around with the client all day today so I will report back with additional results as the day goes on.

Note that my Chrome client has always run the game correctly. I have never had a problem with Screeps running in Chrome. The problem I was trying to solve was running in the Steam client.

@mashee

Thanks Mashee, check my response above. It does look like the Chromium version was my problem.

@artch , @tedivm

Preliminary results indicate that you guys absolutely ROCK!

I want to thank you guys for the excellent support.

Your response time was fantastic. Your response was on point and informative. You understood the issue and responded with a solution.

I did the following:

I downloaded and installed the above listed version of Chromium. A version of the browser opened and a link arrived on my desktop. I ran the link and what I assume to be a new version of Chrome opened and ran.

I rebooted. I ran the Steam client and played the game for a while doing everything I could to force the slowdown.

Everything seems to be working fine and the game does not seem to be slowing down.

At this point, it looks like you have solved my problem.

Thank you!