Private server not working since update to v4

  • Dear Screeps,

    Since updating to v4 of the screeps server, there seem to be some strange issues abound.

    Receiving an error in the console:
    TypeError: Cannot read property 'energy' of undefined
    at makeGameObject (:17067:77)
    at Object.init (:17239:49)
    at :16435:22
    at ()
    at make (/home/screeps/world/node_modules/@screeps/driver/lib/runtime/make.js:142:34)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)

    The world doesn't seem to have initialized correctly. Is this a known issue?

    Here's how connecting via the client looks like: 0_1571577166500_b8bfc564-ffa3-48d8-ac7d-927fd2d75d9d-image.png

    Assistance would be welcome.

    Kind regards,


  • Dev Team

    @atavus Any idea how this may be reproduced?

  • @o4kapuk so this is not a common occurrence?

    I simply had v3 installed before and upgraded to v4.

    The only other interesting thing is that I'm using an AWS EC2 A1 instance.

  • Dev Team

    Do you have logs from the date you upgraded the server? That would be helpful to check storage log files.

  • @artch

    Not much in there:

    Loading mods from "/home/screeps/world/mods.json"
     - /home/screeps/world/node_modules/screepsmod-auth/index.js
     - /home/screeps/world/node_modules/screepsmod-mongo/index.js
     - /home/screeps/world/node_modules/screepsmod-admin-utils/index.js
     - /home/screeps/world/node_modules/screepsmod-features/index.js
    Starting storage server
    Storage listening on storage.sock

  • @artch

    more interesting logs appear in processor:

    Error processing room W9N6: TypeError: Cannot read property 'energy' of undefined
        at module.exports (/home/screeps/world/node_modules/@screeps/engine/dist/processor/intents/spawns/tick.js:51:87)
        at /home/screeps/world/node_modules/@screeps/engine/dist/processor.js:423:83
        at /home/screeps/world/node_modules/lodash/index.js:3073:15
        at baseForOwn (/home/screeps/world/node_modules/lodash/index.js:2046:14)
        at /home/screeps/world/node_modules/lodash/index.js:3043:18
        at Function.<anonymous> (/home/screeps/world/node_modules/lodash/index.js:3346:13)
        at /home/screeps/world/node_modules/@screeps/engine/dist/processor.js:410:11
        at _fulfilled (/home/screeps/world/node_modules/q/q.js:854:54)
        at /home/screeps/world/node_modules/q/q.js:883:30
        at Promise.promise.promiseDispatch (/home/screeps/world/node_modules/q/q.js:816:13)

  • Dev Team

    @atavus Is it your current log file or the file from the moment you've launched v4.x.x for the first time?

  • YP

    have you updated screeps-mongo to the latest version? I'm currently running screeps server v4.0.3 with screeps-mongo without seeing this error.

  • Dev Team

    Oh right, I've just noticed you use screepsmod-mongo. This is it, we don't support it, please contact the mod maintainer @ags131

  • @artch @o4kapuk that was it! Thanks for the assist.