-
-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Complier compliance & BandAid fix for operator.ts #775
Complier compliance & BandAid fix for operator.ts #775
Conversation
WIP for invader threat assessment See TODO
oops added notmycreeps.invader, this addition doesn't break anything as it still passes invaders to enemy |
I like idea of notMyCreeps including invaders :) |
I'm experiencing zero issues with constants on the unstable branch without using this PR. What is the reason behind the relative imports? I like the invader thing. Could you make a separate PR for that please? I will happily merge that ASAP |
On node 16.20.2, and 20.10.0 This was occurring for me, with no changes to the unstable branch |
Adding relative imports took away the require that was present on the top of the file after the banner |
Which file and which banner? sorry. |
v16.17.1, no issues for me |
Build output. Complied main.js output Banner comes from rollup cfg |
Node v16.17.1 same issue without PR. Unsure why its doing this |
277472c
into
The-International-Screeps-Bot:unstable
Changed all constants/general imports to use relative importing to file importing it
Changed constants/general.ts and commented a non power task. if we take this approach ALL tasks must have all task function declarations in the role files. Going forward, add these and maybe error with not implemented and creep debug info to see what called it because it shouldn't be called. This is generally avoided because creeps individually select tasks and are not assigned. We will likely never see this.