I am not 100% sure about this but did anyone notice that this piece of code:
that its just more efficient as i faced resource looses caused by probably invalid rows of updates by the PlanetRessUpdate class and this one.
I mean if i only use the code used at else and i am on this planet, i sometimes face resource looses.
Those Resources Looses not only happened on Flights - also on Features for example, so i wonder if somebody else may encountered this.
PHP Source Code
- if($PLANET['id'] == WHATEVER_END_ID_OF_A_PLANET_OR_SOMETHING_ELSE) {
- $PLANET[$resource[901] += SOME_NUMBER;
- } else {
- database::get()->update("UPDATE %%PLANETS%% SET metal = :currentMetal + :newMetal WHERE id = :planetId", [
- ':currentMetal' => $PLANET['metal'],
- ':newMetal' => SOME_NUMBER,
- ':planetId' => $PLANET['id']
- ]);
- }
I mean if i only use the code used at else and i am on this planet, i sometimes face resource looses.
Those Resources Looses not only happened on Flights - also on Features for example, so i wonder if somebody else may encountered this.