Navigation

    forum

    • Login
    • Search
    • Categories
    • Recent
    • Popular
    • Users
    • Groups
    1. Home
    2. Technical Issues and Bugs
    • Newest to Oldest
    • Oldest to Newest
    • Most Posts
    • Most Votes

    Technical Issues and Bugs

    • Unsolved room.controller.pos returns a creep position
      • Yyg

      3
      3
      Posts
      3679
      Views

      @o4kapuk Thanks. I'll start checking for any position assignments.
    • Unsolved Private server -> rooms are not displayed
      • chuckingame

      3
      3
      Posts
      5156
      Views

      i managed to fixed this error: Couldn't reload bot AI "simplebot": Error: ENOENT: no such file or directory, stat 'C:\Program Files (x86)\Steam\steamapps\common\Screeps\server\node_modules@screeps\simplebot\src' by installing the simple bot: npm install @screeps/simplebot but still getting these errors: Unhandled rejection: Error [ERR_HTTP_HEADERS_SENT]: Cannot set headers after they are sent to the client at ServerResponse.setHeader (_http_outgoing.js:470:11) at ServerResponse.header (E:\dev\screepsAI_V1\node_modules\express\lib\response.js:767:10) at ServerResponse.send (E:\dev\screepsAI_V1\node_modules\express\lib\response.js:170:12) at ServerResponse.json (E:\dev\screepsAI_V1\node_modules\express\lib\response.js:267:15) at E:\dev\screepsAI_V1\node_modules\q-json-response\q-json-response.js:17:14 at _rejected (E:\dev\screepsAI_V1\node_modules\q\q.js:864:24) at E:\dev\screepsAI_V1\node_modules\q\q.js:890:30 at Promise.when (E:\dev\screepsAI_V1\node_modules\q\q.js:1142:31) at Promise.promise.promiseDispatch (E:\dev\screepsAI_V1\node_modules\q\q.js:808:41) at E:\dev\screepsAI_V1\node_modules\q\q.js:624:44 Unhandled rejection: Error [ERR_HTTP_HEADERS_SENT]: Cannot set headers after they are sent to the client at ServerResponse.setHeader (_http_outgoing.js:470:11) at ServerResponse.header (E:\dev\screepsAI_V1\node_modules\express\lib\response.js:767:10) at ServerResponse.json (E:\dev\screepsAI_V1\node_modules\express\lib\response.js:264:10) at E:\dev\screepsAI_V1\node_modules\q-json-response\q-json-response.js:17:14 at _rejected (E:\dev\screepsAI_V1\node_modules\q\q.js:864:24) at E:\dev\screepsAI_V1\node_modules\q\q.js:890:30 at Promise.when (E:\dev\screepsAI_V1\node_modules\q\q.js:1142:31) at Promise.promise.promiseDispatch (E:\dev\screepsAI_V1\node_modules\q\q.js:808:41) at E:\dev\screepsAI_V1\node_modules\q\q.js:624:44 at runSingle (E:\dev\screepsAI_V1\node_modules\q\q.js:137:13) and no room will be displayed.
    • Unsolved RawMemory.foreignSegment should be more consistent
      • WarInternal

      1
      1
      Posts
      2614
      Views

      No one has replied

    • Unsolved Wrong badges in world view
      • Xenofix

      3
      3
      Posts
      4481
      Views

      Yup, latest one here by me.
    • Unsolved Tiny badges on creeps
      • Xenofix

      4
      4
      Posts
      5133
      Views

      I used to see this regularly in chrome but I haven't seen it for a while
    • Unsolved NPC Trains/Caravans get stuck entering disabled rooms
      • WarInternal

      5
      5
      Posts
      5882
      Views

      This is known issue but thanks for the report anyway
    • Steam version not working
      • Zolcsika

      9
      9
      Posts
      13054
      Views

      Close all the Steam tasks in the background will resolve the issue.
    • Solved Bad default zoom
      • Helam

      10
      10
      Posts
      10896
      Views

      @artch So much better! Thank you!
    • Solved One of room turn zombie, things freeze, no creeps move and their .ticksToLive are negative.
      • ART999

      2
      2
      Posts
      3135
      Views

      Thanks, fixed.
    • Solved Where to report security vulnerabilities?
      • JBYoshi

      2
      2
      Posts
      3262
      Views

      When logged into the screeps world, Top left next to the Screeps logo there's a menu button.Half way down the menu is "Report a Problem" https://support.screeps.com/hc/en-us/requests/new There is also an option to mark it Urgent if you feel its dire.
    • Solved Power Creeps - Others can enable power in my reserved rooms
      • Hernanduer

      30
      30
      Posts
      66814
      Views

      @davaned This mechanic is not supposed to be temporary. It's an opt-in mechanism which allows newcomers not to worry about the added complexity of this gameplay. We don't have plans to remove it anytime soon, including on new shards.
    • bug ? : room.energyAvailable counts inactive extensions
      • Finndibaen

      6
      6
      Posts
      7524
      Views

      I wrote a small constant array that has the "max E amounts" for each RCL. Not pretty and doesn't cover a lot of edge cases but works as a cheap workaround for this issue.
    • Solved Upscaling HD resolution causes bad scaling
      • Crusher48

      2
      2
      Posts
      3902
      Views

      @crusher48 Should be fixed now, update your client and try again.
    • Solved Rooms are really dark and visuals don't work.
      • Smokeman

      2
      2
      Posts
      3151
      Views

      This is fixed already. Please see this announcement thread.
    • Unsolved Used CPU gets rounded up to whole numbers, which penalises cross-shard bots and makes bucket-regen impossible at 1 CPU assigned
      • wtfrank

      6
      6
      Posts
      5418
      Views

      The other major problem with this is that it means you can't assign 1 CPU to a shard, as the bucket can never regenerate even if you do almost nothing in your tick.
    • Solved Cannot reassign CPU
      • Smokeman

      10
      10
      Posts
      10427
      Views

      @o4kapuk said in Cannot reassign CPU: I was able to reproduce the issue, and we're working on the fix Awesomesauce!
    • Solved WTF is wrong? My creeps just jumped a shard...
      • MrFaul

      4
      4
      Posts
      5369
      Views

      I have seen a bug where if you sit on shard1/E1N1 and change the url to shard2/E1N1; then use the minimap to look at a nearby room you end up on shard1 again. Not sure if that has caused your problem, but just in case it is related.
    • Unsolved PWR_SHIELD rampart graphic does not go away at expiry
      • Orlet

      6
      6
      Posts
      7240
      Views

      @kraiik said in PWR_SHIELD rampart graphic does not go away at expiry: @Orlet In my experience only destroying the last rampart in the room creates this graphical error, if there's still another rampart in the room the destroyed rampart disappears normally (though I haven't tested this with PWR_SHIELD). PWR_SHIELD probably just makes the existing issue more visible. I see, I haven't tried destroying all of ramparts yet @o4kapuk said in PWR_SHIELD rampart graphic does not go away at expiry: This is a known issue, we're working on it But thanks for reporting anyway Roger. Thanks for reply!
    • Solved Invaders suicide in unowned rooms with no player creeps
      • Tigga

      5
      5
      Posts
      5428
      Views

      The fix should be deployed atm.
    • Solved PowerCreeps - Sporadic Loss of PowerCreep.memory
      • Hernanduer

      9
      9
      Posts
      11718
      Views

      That explains it, I'm not checking if I'm the owner when I run foreach on all PCs in Game.powerCreeps.

    Move Topic