Skip to content

Latest commit

 

History

History
177 lines (123 loc) · 9.29 KB

README.md

File metadata and controls

177 lines (123 loc) · 9.29 KB
Raw

KarateSnoopy's Tutorial Conversion to 2021 (attempt)

ScreepsImg

What me added

Screeps-Inscribe from (resir014)

Logger from (resir014)

Console Commands

Commands are defined in Consolecommands.ts Test if they work by typing in

cc.test()

in the Console.

This is all WIP and there will be no guarantee that the committed code is working ;)

I own Screeps since 2017 but never rly digged into it. And as i Am not rly a Programmer it is hard for me to get into the Game. I found this great Tutorial:

and this will be my attempt to understand and convert it to Screeps 2021. This will be much try and error, so i am not capable to do a video tut as he did. (maybe in the future i will) U can get the Code for his Episodes here:

and the Video Tutorial is on Youtube here:

My Code will start on EP3 and i will try to Commit the Episodes like he did.

Here you will get the Commits from me: (Commits)

Actual Progress

i had a lot of trouble so always use the last Commit of a specific Episode, sry 4 that one.

  • EP-03 -> done | 27.10.2021
  • EP-04 -> done | 28.10.2021
  • EP-05 -> done | 29.10.2021
  • EP-06 -> done | 01.11.2021
  • EP-07 -> done | 02.11.2021
  • EP-08 -> done | 05.11.2021
  • EP-09 -> done | 05.11.2021
  • EP-10 -> done | 05.11.2021
  • EP-11 -> done | 07.11.2021
  • EP-12 -> done | 07.11.2021
  • EP-13 -> done | 09.11.2021
  • EP-14 -> done | 09.11.2021
  • EP-15 -> done | 10.11.2021
  • EP-16 -> Just the Setup of the Server etc
  • EP-17 and on: -> Your work here:

Info Current Project Issues/errors

  • EP-03-06 I don't know where exact this error is, but the Miner's didn't fill the Containers. Thats fixed now in EP-09, here is the Correction which should work when u first write the Code for the Miners: MinerError;
  • EP-06 End: The Code for calculating the amount of energy a Creep is carrying was wrong. It's fixed now. Behavior was that Creeps only mined 4% Energy and ran away afterwards.
  • EP-06 End: I still don't know how to get around the delta operand error in memoryInit(). Loading a new Mem version seems not to work properly. Workaround for now: open the Creeps Memory and append a new Property giving them: role:3 for Miners and role:2 for Builders. In that way the CreepsMemory will fix it self afterwards. After some more Try and Error it seems that it works for now. Will keep an eye on it.
  • EP-07: had to change the memoryInit() again. I hope now its working. Added 2 more Console Commands: setMem(number) To set new Memory version on the Fly | getMem() To get the actual Memory version
  • EP-08 End: The clearing memory is working Properly, had a look at it the last 2 Episodes.
  • EP-09 End: i decided to restructure the Folders a bit to get an better overview. The Main Roommanager -Methods are in Roommanager. The Sub-Methods in the Lib.
  • EP-10 End: I recognized that exporting Creep[], Builder[] and all that stuff doesn't work, cause it always returns empty objects. So i changed the Code at many parts. To get the Problems just change the line 
    export let creeps: Creep[]
    to 
    let creeps: Creep[]
    and see where the failures pop up.
  • EP-13 End: It took me again some try and Error cause the Original Code forced some Trouble. But Builders now build Extensions and Roads as they should.
  • EP-14 End: If u just update to the new Code and load it up you'll get a undefined error when pushing rm.extensionIdsAssigned. Just change the Memory-Version to get rid of it. Via ingame: cc.setMem(number) or direct in the Code in the Memory.ts.
  • EP-15 End: I had trouble again cause of the notRoadNeedingRepair variable which again is exported Empty from RoomManager. To keep it simple i just copied the Code from scanRoom to the builder. its not pretty, but it works.
  • EP-End: The Code should work correct. Anyway, i watched the last Commits of KarateSnoopy and he changed a lot compared to his last episode code. I think it's more easy to download his actual code and read it with your knowlege now, than rewrite all. There are LOTS of changes. Feel free to go from here on your own. either rewrite the code using his last commit, or download it, or try to go on from here on your own. GLHF.

Helper

+-------------------------------------------------------------------------------------+ |R | R | C | S | E | R | W | T | S | L | E | L | T | O | P| |C | o | o | p | x | a | a | o | t | i | x | a | e | b | S| |L | a | n | a | t | m | l | w | o | n | t | b | r | s | p| | | d | t | w | e | p | l | e | r | k | r | o | m | e | a| | | | a | n | n | a | s | r | a | | a | r | i | r | w| | | | i | | s | r | | | g | | k | y | n | v | n| |-------------------------------------------------------------------------------------+ |0 | 0 | 5 | 1 | 0 | 0 | 0 | 0| 0 | 0 | 0 | 0 | 0 | 0 | 0| |1 | 200 | 5 | 1 | 0 | 0 | 0 | 0| 0 | 0 | 0 | 0 | 0 | 0 | 0| |2 | 45 | 5 | 1 | 5 | 300000 | 1 | 0| 0 | 0 | 0 | 0 | 0 | 0 | 0| |3 | 135 | 5 | 1 | 10 | 1000000 | 1 | 1| 0 | 0 | 0 | 0 | 0 | 0 | 0| |4 | 405 | 5 | 1 | 20 | 3000000 | 1 | 1| 1 | 0 | 0 | 0 | 0 | 0 | 0| |5 | 1215000 | 5 | 1 | 30 | 10000000 | 1 | 2| 1 | 2 | 0 | 0 | 0 | 0 | 0| |6 | 3645000 | 5 | 1 | 40 | 30000000 | 1 | 2| 1 | 3 | 1 | 3 | 1 | 0 | 0| |7 | 10935000| 5 | 2 | 50 | 100000000| 1 | 3| 1 | 4 | 1 | 6 | 1 | 0 | 0| |8 | 99999999| 5 | 3 | 60 | 300000000| 1 | 6| 1 | 6 | 1 | 10| 1 | 1 | 1| +-------------------------------------------------------------------------------------+ */

Useful Links

(https://screeps.fandom.com/wiki/Creep#Body_Parts)

(https://screepspl.us/services/creep-calculator/)

Origin from here

Screeps Typescript Starter

Screeps Typescript Starter is a starting point for a Screeps AI written in Typescript. It provides everything you need to start writing your AI whilst leaving main.ts as empty as possible.

Basic Usage

You will need:

  • Node.JS (10.x || 12.x)
  • A Package Manager (Yarn or npm)
  • Rollup CLI (Optional, install via npm install -g rollup)

Download the latest source here and extract it to a folder.

Open the folder in your terminal and run your package manager to install the required packages and TypeScript declaration files:

# npm
npm install

# yarn
yarn

Fire up your preferred editor with typescript installed and you are good to go!

Rollup and code upload

Screeps Typescript Starter uses rollup to compile your typescript and upload it to a screeps server.

Move or copy screeps.sample.json to screeps.json and edit it, changing the credentials and optionally adding or removing some of the destinations.

Running rollup -c will compile your code and do a "dry run", preparing the code for upload but not actually pushing it. Running rollup -c --environment DEST:main will compile your code, and then upload it to a screeps server using the main config from screeps.json.

You can use -cw instead of -c to automatically re-run when your source code changes - for example, rollup -cw --environment DEST:main will automatically upload your code to the main configuration every time your code is changed.

Finally, there are also NPM scripts that serve as aliases for these commands in package.json for IDE integration. Running npm run push-main is equivalent to rollup -c --environment DEST:main, and npm run watch-sim is equivalent to rollup -cw --dest sim.

Important! To upload code to a private server, you must have screepsmod-auth installed and configured

Typings

The type definitions for Screeps come from typed-screeps. If you find a problem or have a suggestion, please open an issue there.

Documentation

We've also spent some time reworking the documentation from the ground-up, which is now generated through Gitbooks. Includes all the essentials to get you up and running with Screeps AI development in TypeScript, as well as various other tips and tricks to further improve your development workflow.

Maintaining the docs will also become a more community-focused effort, which means you too, can take part in improving the docs for this starter kit.

To visit the docs, click here.

Contributing

Issues, Pull Requests, and contribution to the docs are welcome! See our Contributing Guidelines for more details.