Bug Status [10/4]

[Infinite Aerospace]

On 10/5/2023 at 2:49 AM, PicoSpace said:

I haven't seen #19 yet... that's a whooper!

 

That's what Avenged Sevenfold were singing about in their fantastic song 'Planets' on the Hail to the King album. 

[WatchClarkBand]

Saying "I have no idea what's going on" definitely isn't a good status report. However, saying "I investigated X, Y, and Z, and they're definitely not involved" is useful because it narrows down the path of investigation. So many "smart" but naive engineers would crap on the notion of documentation, but I would usually insist that documenting what was tried and didn't work was as important as documenting the implemented approach as, inevitably, some new engineer (to the team or the problem space) would see some deficiency and then dive in investigating a path that was already proven to be untenable, wasting valuable time. There's nothing wrong with not solving a problem immediately, but good engineers should communicate the paths investigated but not taken.

[nubnubbud]

On 10/4/2023 at 5:17 PM, nestor said:

Number 2 is not really a bug but a side effect of all the calculations that are running in the background and that are needed for future features such as colonies. This will need a mix of optimizations and  adjustments to the plan to be able to have something that can scale with future updates of the game. As with other areas we are exploring both short term improvements and long term solutions to the challenge. 

Honest question- 
for updates to various values, I would expect that colonies take a "sample" such as calculating how much resource income per time there is, then once that's done, simply make it a deterministic value, so no matter how forward you go, it would be accurate the next time you checked. You'd only need to check and fully update it in times and places where you could use it. otherwise a vague abstraction or estimate should work fine.