Agreed. If lower fees would mean a boost in activity to the (currently quite inactive) market, that would be great. As the costs stand now, the market doesn't hold much interest for me.

I had a bug in my code where a type of creep was constantly getting recycleCreep() called on it while it was being created, by the spawn that was creating it. It would go through the spawning process, but would disappear before exiting the spawn and not leave a Resource pile behind. Perhaps a creep should exit the spawn before the spawn is allowed to recycle it, to make it more apparent what's happening.

tedivm: Depending on how visibility is removed, it's possible for it to not affect anyone's code. Game.rooms could continue to only return the rooms that you have creeps in, but Game.getObjectByID could be made to return the object no matter what, and a Game.getRoomByName could be added to return the Room object for any room on the map. Then, you could get all the room's attributes you were talking about.

I don't think the devs intend for us to be able to permanently alter the terrain like that, but it definitely would be cool. It could be that cleared swamps are quickly reflooded by adjacent swamp tiles, meaning that you have to make a concerted effort with multiple creeps to do it.

Awesome! Thanks, stybbe.

Just wondering: has there been an explanation of the purpose of visibility?  In a game that's all about automation, it seems a little strange that I have access to information that my code doesn't, especially since there are ways to circumvent it anyway. Do people feel that the game benefits from restricting visibility?

I agree with Knightshade -- removing the meta rewards for maxing out your rooms would make it a lot less satisfying. There must be a better alternative to the 15 energy limit.

It would be much easier to test fully automated scripts in the simulator if we could increase the speed beyond 500%. Ideally, way beyond 500%.