thinking about it now, color blindness would make it hard to identify what body parts a creep has on it at first glance too...

yup, even a hover tooltip would probably help.

@Davaned agreed. someone just sending an attack and someone else defending should not affect their scores. we would need to identify a successful attack or defense to adjust the scores. perhaps a surviving defender would get an increase in PvP points, just not as much as a successful attack... also, if it resets monthly, like the other leaderboards, i do not see the issue of 0 sum adjustments like @deft-code's being critical.

@artch Out of curiosity, if this is a sandbox game specifically designed to let players do whatever they want and some players identify a way to transport energy more effectively (I too agree that energy is too immobile), then why is it an issue? Is there a reason that energy was intentionally made so difficult to transport?

Alternatively, a lot of players use recycle to recoop boosts for temporary use creeps. Is there any way to use the 70% for the energy recovery, but leave boosts at 100%?

the last i heard in the slack, was that the build takes more memory than running it in the first place (causing it to fail on a lot of RasPIs). you might need to build it piece-meal, or build it elsewhere and migrate it onto the PI afterwards.

I'd still say that it will not be a very good server, but if youre willing to get it working just as a challenge, i say go for it.

yeah, the runners should know whether they will need to perform a global reset on the next tick before pushing their updates to the DB. if it were to add a REQ_PLAYER_CODE flag or something, then the DB would only need to push the code to the runners once per global reset, not every tick, reducing a crap ton of the bandwidth which was one of the initial arguments against raising it 2 years ago. If the DBs are the limiting factor for tick times, then not requesting and sending code for every player every tick should be a major boon to tick times too...

@mototroller A lot of the old guard left due to a lack of new features. Depending on how well this was implemented, it might be enough to bring some of em back... Do not underestimate "late game features."

@artch would tunnels act like ramparts in the defense of creeps? it could work both ways, defending both attackers and defenders if you decide to do that... attackers could still "collapse" tunnels too

@artch said in StructureSpawn causing "circular structure" error on JSON.stringify():

We can add RawMemory.autoCreateObjects boolean property which is true by default, but you can change it to false before accessing Memory first time on the tick.

I think it should be false by default, but if there were an option I can use to prevent this, I would be absolutely ecstatic.

It would also prevent debugging by serializing it to the console, as identified by the global.ex() function by @WarInternal that I mentioned in a previous post. I use that in the console frequently to debug, and that was why I was and still am against that option. I am still a proponent of the console.log() inside of the .toJSON() function, warning about what they are doing. Player education over player coddling...