Skip to content

Conversation

@RiftLurker
Copy link
Contributor

This implements the range limitations by the constants RANGE_* that are added with PR#2 in screeps/common.

@JestDotty
Copy link

why RANGE_HARVEST_MINERAL & RANGE_HARVEST_SOURCE? The command for both is harvest & same range, wouldn't it make more sense to just be RANGE_HARVEST?

@TheRealMaxion
Copy link

@JestDotty My guess is that it would allow them to have different ranges should a private server choose to do so.

Copy link
Contributor

@o4kapuk o4kapuk left a comment

Choose a reason for hiding this comment

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

Verified

@semperrabbit
Copy link

This is over 2 years old. Is there going to be any movement on this? It looks like the conflicting files still need to get fixed. it is approved though.

semperrabbit added a commit to semperrabbit/screeps_engine that referenced this pull request Jul 16, 2019
clone and fixed merge conflicts of screeps/engine PR screeps#6 by PostCrafter
added RANGE_* constants for PowerCreeps
RiftLurker pushed a commit to RiftLurker/screeps-engine that referenced this pull request Oct 27, 2020
clone and fixed merge conflicts of screeps/engine PR screeps#6 by PostCrafter
added RANGE_* constants for PowerCreeps
RiftLurker and others added 3 commits October 27, 2020 10:44
@RiftLurker
Copy link
Contributor Author

I've rebased the branch and added RANGE_RENEW_POWERCREEP and RANGE_HARVEST_DEPOSIT (see corresponding changes in screeps/common#2).

@semperrabbit
Copy link

dang, im excited, this would be a culmination of a set of almost 4 yr PRs. I hope this gets through, @o4kapuk, as this will allow more possible changes for follow-on seasonal servers 👍.

Ideas include combat, but adjusted ranged heal and increased RANGE_ATTACK or GCL race, but different attackController, upgradeController, claimController and upgradeController ranges...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants