Skip to content

Add RANGE_* constants #2

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.

Sign up for GitHub

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

Open
wants to merge 7 commits into
base: master
Choose a base branch
from
Open

Add RANGE_* constants #2

Changes from 1 commit
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
7d09c5b
Add RANGE_* constants
RiftLurker Dec 19, 2016
f94ac13
Remove unused RANGE_DROP
RiftLurker Jun 20, 2017
57a5def
Merge branch 'master' into master
RiftLurker Dec 14, 2017
204432b
Merge branch 'master' into pr2
o4kapuk Sep 25, 2018
b5f1fa8
feat: add RANGE_UNBOOST_CREEP constant
o4kapuk Sep 25, 2018
c3b1703
Add RANGE_RENEW_POWERCREEP
RiftLurker Oct 27, 2020
f870057
Add RANGE_HARVEST_DEPOSIT
RiftLurker Oct 27, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 25 additions & 0 deletions lib/constants.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -94,6 +94,31 @@ module.exports = {
"claim": 600
},

RANGE_ATTACK: 1,
RANGE_ATTACK_CONTROLLER: 1,
RANGE_BOOST_CREEP: 1,
RANGE_BUILD: 3,
RANGE_CLAIM_CONTROLLER: 1,
RANGE_DISMANTLE: 1,
RANGE_DROP: 1,
Copy link

@bastianh bastianh Jun 19, 2017 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

RANGE_DROP: I don't think this is used anywhere .. and I think it's not quite correct :)

Copy link

@DissiNL DissiNL Jun 19, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree, RANGE_DROP seems weird. You can not give a position to where you'd want to drop resources.

Copy link
Author

@RiftLurker RiftLurker Jun 19, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's possible that I just mindlessly added RANGE_ constants for all of the actions, it obviously doesn't make any sense for drop.
I'll update the PR later on.

RANGE_GENERATE_SAFEMODE: 1,
RANGE_HARVEST_MINERAL: 1,
RANGE_HARVEST_SOURCE: 1,
RANGE_HEAL: 1,
RANGE_PICKUP: 1,
RANGE_RANGED_ATTACK: 3,
RANGE_RANGED_HEAL: 3,
RANGE_RANGED_MASS_ATTACK: 3,
RANGE_RECYCLE_CREEP: 1,
RANGE_RENEW_CREEP: 1,
RANGE_REPAIR: 3,
RANGE_RESERVE_CONTROLLER: 1,
RANGE_RUN_REACTION: 2,
RANGE_SIGN_CONTROLLER: 1,
RANGE_TRANSFER: 1,
RANGE_UPGRADE_CONTROLLER: 3,
RANGE_WITHDRAW: 1,

WORLD_WIDTH: 162,
WORLD_HEIGHT: 162,

Expand Down