-
Notifications
You must be signed in to change notification settings - Fork 66
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
Use RANGE_* constants #6
base: master
Are you sure you want to change the base?
Conversation
why |
@JestDotty My guess is that it would allow them to have different ranges should a private server choose to do so. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Verified
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. |
clone and fixed merge conflicts of screeps/engine PR screeps#6 by PostCrafter added RANGE_* constants for PowerCreeps
clone and fixed merge conflicts of screeps/engine PR screeps#6 by PostCrafter added RANGE_* constants for PowerCreeps
clone and fixed merge conflicts of screeps/engine PR screeps#6 by PostCrafter added RANGE_* constants for PowerCreeps
I've rebased the branch and added |
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 |
This implements the range limitations by the constants RANGE_* that are added with PR#2 in screeps/common.