I stopped using built-in version and got latest private server version from Screeps Github (currently it is 4.2.3). So I am launching private server from command line and then use steam client to access it same way as I would connect to built-in private server in steam client. Until built-in server is fixed it is best option we have imho
Posts made by SteelHammer
-
RE: Private Server Completely Brokenposted in Technical Issues and Bugs
-
RE: Id<T>posted in Help
@adeptofnone said in Id<T>:
tslint
If I understand your question correctly the best solution would be to store two lists instead of one. First list/array to store all IDs and second list/array to store which structure types each ID belongs to. 1:1 relationship between indexes of both lists will be easy to maintain
-
RE: room.energyAvailable returns null on private serverposted in Technical Issues and Bugs
I also just recently started to use local private server (v4.2.3) on own PC and can confirm that after server stop and repeated start all spawns (own and for all default bots) are displaying 0/0 energy. No creeps can be produced in this state and only found solution is system.resetAllData() command execution to drop all your progress on private server and start all over until next server restart. Is there any fix scheduled for this issue?
Some details about PC I am running local private server on: OS: Linux Mint 19.3 Node: v12.19.0 (LTS) npx: 6.14.8 RAM: 32GB CPU: AMD Ryzen 7 3700X GPU: GeForce GTX 1650 4GB