Posts made by stybbe

One option is to download the repository from https://github.com/screeps/docs and host your own web server to browse. Another option is to install a web page archive plugin to your browser and download website.

This room state hang the tab for me when using webgl renderer. Work just fine with the old one. It was the same issue when it was live and not only in the replay view. https://screeps.com/a/#!/history/shard0/W22S18?t=22318600.

@hyramgraff said in Changelog 2017-09-28:

@dissi-mark

I must admit that I'm a bit nostalgic about the default names that were generated by createCreep. Is there a way to expose the function that it was using to generate creep names?

The function is posted in this thread https://screeps.com/forum/topic/626/please-give-us-access-to-random-name-generator-for-creeps/5

Have you tried creating a new branch? Or clearing your memory? The patch introduces a lot of bugs so I guess the Artem is quite busy right now.

Ye it's all normal, everyone has it.

If you need any help calculating the GLC from stats.energyControl you can check this code.

If you're using Chrome and the Screeps SC extension you can add your own little module to have this feature. 

Example:

In settings.json

{
    "path": "modules/room.select.objectid.js",
    "runAt":{
       "onUpdate": "https://screeps.com/a/#!/room/" 
    }
}

Create a new file modules/room.select.objectid.js

/**
  * @summary Select object by id on room access.
  * 
  * Example: https://screeps.com/a/#!/room/W10S10?objectid=57cd3a30c0551957424a1f47
  *
  */
 module.exports.init = function () {
     module.getScopeData("room", "Room", ['Room.objects'], function (Room) {
         var id = module.exports.getParameterByName("objectid");
         var objects = _.filter(Room.objects, { _id: id });
 
         if (objects.length) {
             Room.selectedObject = objects[0];
         } else {
             console.warn("Could not select object by id: " + id)
         }
     });
 }
 
 module.exports.update = function () {
     // not used.
 }
 
 // http://stackoverflow.com/questions/901115/how-can-i-get-query-string-values-in-javascript/901144#901144
 module.exports.getParameterByName = function (name, url) {
     if (!url) {
         url = window.location.href;
     }
     name = name.replace(/[[\]]/g, "\\$&");
     var regex = new RegExp("[?&]" + name + "(=([^&#]*)|&|#|$)"),
         results = regex.exec(url);
     if (!results) return null;
     if (!results[2]) return '';
     return decodeURIComponent(results[2].replace(/\+/g, " "));
 }

I've made a chrome extension for screeps. The extension is built so it's very easy to write and add your own modules. The project includes modules I've made so if you just want some nice extra client features you can install and use it in its current form.

See the repository at: https://github.com/stybbe/Screeps-SC 

Ye the url is https://screeps.com/api/user/code?branch=$activeWorld 

You could try changing the limit to see if your code run faster, but there is a limit on how fast your browser can process each tick. You could probably run it a lot faster if you host a local server to test your code.

Type the following in the console to change the limit

angular.element(document.getElementsByClassName('game ng-scope')).scope().Game.maxSpeed = 1000

Ye it's due to how the server manage to scripts. What you have to do is store the object id of every game object you want to store for longer than a tick. And when you want to access the object use Game.getObjectById(id);

Was not this feature implemented as a part to avoid unwanted novice areas? http://screeps.com/forum/topic/446/Interesting-novice-area

If it's still that I think the the documentation should say something about how often you need to resign it to avoid novice area. I know from experience that a novice area can pop up in just in few hours from a lost room (https://screeps.com/a/#!/room/W25S23) so it would be useful to know if I need to resign it every hour or every day.

I think a fun thing could be that invaders scale depending GCL spent on the room. So if you boost the room massively you going to have to defend it against armies of invaders.

Believe this is more of a browser issue. You have to assign your details tag with an unique id if you want it to keep its state.

Example if you print just one list each tick this should work:

"<details id='" + Game.time + "'>"

With the new demanding remote invader attacks I would like my room to react a bit faster with killing the invaders. If all my spawns are busy spawning and the creeps are unlucky, they will have to wait for an extra 150 ticks before rescue arrives.

The StructureSpawn.recycleCreep command return OK when used on a spawning creep. The problem is that the spawn timer doesn't reset... it just kill the spawning creep and continue the timer.

Proposal:
Reset spawn timer when using StructureSpawn.recycleCreep on a spawning creep or add a new abort() function to StructureSpawn.

Your replay doesn't really show what you're stating. On your first replay the creep didn't run away. A new one spawned because the current one had been alive for over 300 ticks with low health. This was in the change log in the last source keep change. Your error seems to be in your guards committing suicide when all move parts are destroyed; or some other kind of error?

See tick replay at https://screeps.com/a/#!/history/E6N16?t=14716374 at bottom right, your creep vanish when on half health.

1 work dismantle 0.25 energy so you need at least 4 work to not get rounded down to 0.

Well for rooms in a radius of 10 you could use your observer structure before dealing. For far away enemies a blacklist could probably work, hopefully it's not a day off to fill the blacklist. 

Nice looking badge btw

I think it will be a bit redundant. You can already achieve this with description parameter in the StructureTerminal.send

I would like to have the option to specify where my new born creep should exit the womb. 

If the exit is blocked the next exit can be picked from the exit cycle.

The exit parameter should be one of current constants

 TOP: 1,
 TOP_RIGHT: 2,
 RIGHT: 3,
 BOTTOM_RIGHT: 4,
 BOTTOM: 5,
 BOTTOM_LEFT: 6,
 LEFT: 7,
 TOP_LEFT: 8,