Game.market.getAllOrders method now supports internal indexing by resourceType. When you provide an object literal filter description, it will work significantly faster:
Game.market.getAllOrders({resourceType: RESOURCE_UTRIUM}); // fast
Game.market.getAllOrders({resourceType: RESOURCE_UTRIUM,
type: ORDER_SELL}); // fast
Game.market.getAllOrders(); // slow
Game.market.getAllOrders(i => i.resourceType == RESOURCE_UTRIUM); //slow
We have enabled Subscription Tokens integration with the Steam Community Market. Now you can not only buy tokens using Steam Wallet, but also sell them there. If you own Screeps in your Steam account, having tokens in your profile will allow you to exchange and trade them on Steam in the same way as with any other items on it.
upgradeBlocked period, which means it is unavailable to activate safe mode again within the next 200 ticks.StructureExtractor.cooldown property. It is triggered on each harvest action, your harvesters have to wait for 5 ticks until the next harvest call is possible (it will return ERR_TIRED result code).|
Resource | Sell order price | Buy order price |
|---|---|---|
  |
3.00 Cr | 1.00 Cr |
    |
6.00 Cr | 1.00 Cr |
 |
18.00 Cr | 1.00 Cr |
| Energy | 1.00 Cr | — |
Money, money, money
Must be funny
In the Screeps MMO world.
So, our market is opening its floodgates, and all the miners, chemists, speculators, and shopaholics of all sorts have finally found each other to embrace the craze of spontaneous and unconstrained shopping spree! Want those “60 days of CPU subscription”? Sure, grab them for just 3M! Still have no time to harvest some power? But hey, look at that shining one on the shelf for just 20! And, oh boy, there’s a ton of goodness for 20…
As we all know, money is power, and some players have started saving credits for the future, while others rushed to buy valuable lots. Currently we’re seeing 100–900 deals between players in an hour with the total cash turnover at 100K–600K credits an hour (less the buying of resources on NPC orders).
Game.market.getOrderById.Introduced new room safe mode mechanics. It will replace room novice walls protection, and allow to arbitrarily safeguard your rooms while you are offline.
Safe mode is enabled on the room controller when a new player spawns in the world initially. It also can be triggered by any player manually using either the StructureController.activateSafeMode() method, or the button in the controller UI. When activated, it blocks attack, rangedAttack, rangedMassAttack, dismantle, heal, rangedHeal, attackController and withdraw methods of all hostile creeps in the room.
Only one room can be in safe mode at the same time. Safe mode period lasts for 20,000 ticks. It cannot be activated again during the 50,000 ticks cooldown period. But in Novice Areas, there is no cooldown at all.
In order to activate safe mode you spend available activations (StructureController.safeModeAvailable property). You obtain one activation on each controller level upgrade, and also can generate it by Creep.generateSafeMode() method using 1000 ghodium resource.
If the controller is downgraded, it loses all its available safe mode activations, and triggers the cooldown period.
StructureController.safeMode, StructureController.safeModeAvailable, StructureController.safeModeCooldown.StructureController.activateSafeMode.Creep.generateSafeMode.Game.map.isRoomProtected property to Game.map.isRoomAvailable (with the opposite meaning). The old name is still available, but deprecated and will be removed in the future. Rooms in safe mode are considered available.StructureContainer.ticksToDecay property.Game.market.changeOrderPrice.Game.market.extendOrder.The Market system has been deployed.
Market.credits, Market.orders.Market.createOrder, Market.cancelOrder, Market.getAllOrders, Market.deal.Game.resources property.maxCost option to the PathFinder.search method.PathFinder.search method: cost, incomplete.September has begun, and we start getting natural questions like: “When will the open-source server go live that was promised in August?” So in this post we’d like to explain the situation that’s going on now.
Currently we have actually three parallel development pipelines for Screeps:
When our second Indiegogo campaign was launched, the plan was roughly this: make a market system as a major feature, and then delve completely into the development of the standalone server and a Steam client for it. That’s why we set August as an approximate milestone date. However, after the campaign’s end and some consideration we realized that the Steam launch proper and the standalone server release are two vastly different things that should be better done one at a time rather than simultaneously. A higher traffic from Steam may require some adjustments in the scalability of the game servers, so we’d be having hard time watching this process and at the same time taking care of the open-source project that would appear along with it. We decided to first launch the Steam client to attract users to the main official world, debug it, and then move to the standalone server without any hassles.
Our experience has shown it was a right decision. When Steam gave us hundreds and hundreds of new players, it revealed a number of issues in our server architecture that prevented capacity scaling for running your scripts, and we put a lot of time and efforts to debug and optimize those bottlenecks. You might remember how the tick duration soared from 2.5 to 5 seconds, then fell back, then grew again, and then stabilized at 2.7-3 seconds. We are content with the current rate, but achieving it required a lot of work within the past two months.
Due to this reason, unfortunately, the standalone server won’t be launched within the coming weeks. We are sorry to realize that we missed some deadline, but please be assured this was not due to our laziness, but we decided to rearrange the work, and the history proved it was a right decision.
And there is another reason for delaying too. After the Indiegogo campaign was over, we spent some time on designing the concept of a standalone server, and we realized we couldn’t just take the current server code, open-source it, and rest on our laurels. For the project to gain traction as standalone as we see it, the following design concepts need to be implemented:
Implementing some of these things requires the overhauling of the current server code of Screeps since they were not accounted for 2 years ago when the game was first designed. But we are convinced that short of these, the standalone server won’t be the type of product we really want to share with you.
In terms of deadlines, we don't want to be overly optimistic at this point making promises we won’t be able to meet. Let’s keep October in mind. If we get a working version earlier, we’ll definitely show it. As was promised, our Indiegogo campaign backers will be the first to get their hands on it, while the public availability will begin a month later.
Another month has passed as the game servers were doing your bots’ bidding. More than a thousand of artificial intelligences, from fledgling to cunning and hugely optimized ones, have claimed dominance in our parallel universe, and today we can hang this picture on a wall in a frame: