i dont want to be rude, but it seems like dan coders are using copy/paste a lil to much for their coding....as simple as that... they modified the bit of code in the planet page that calculate scan, but they didn't change the bit of code that calculate cloack vs scan in the scan planet page. weird enough it isn't the same function() or (which would be less "lazy coding") you made a new file to include with a new name, but forgot to change the name in the page used for planet scanning....... which is quite common mistakes...
i've found an exploit about energy and reported it; it look like another copy/paste lazy coding...really dan you should start using triggers in your database .... thats powerfull tool...which also save a lot of work for server processor.....
for example, everytime something change a planet cloak value (building or buff), the database trigger intercept it, ask database (ONCE!) for all the current buff/building on that planet, calculate the cloaking. Then, when you need a planet cloak value, it just have to ask something like (select cloak from planets where planet_id = xxxxx) which is much faster then caculating it everytime you need it.....
if you need some help to clean your code, i'll gladly help you dan
but i pretty much guess you wont read my post as you ignored my post about Energy exploit (and how to fix it with 5 minute of intense coding...).
regards.
