-
Notifications
You must be signed in to change notification settings - Fork 156
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
tower link placement mistakes #445
Comments
I guess you got the idea. Anyway will explain the basic idea :-): |
@TooAngel I understand the idea. The problem illustrated here is that the towerfiller (yellow "t") is being placed not-adjacent to the link (blue "Li") or the tower (blue "To") sometimes. |
Yes, agree, got it. Needs to be fixed :-) Good to have the issue ... If you or someone else will look into it at some point, I just want to reference the base idea how it should have looked it. Fixing would be cool, improving the idea - even better ;-) |
Is it important to have one link and filler per tower? It seems like most layouts have two of the towers close together. Combining them to use one link and two fillers seems trivial. Using one link and one filler would be a little trickier, but not much. |
True, we could also do more tower. Currently it iterates over all exit paths and places the combination on each. If there are less exits, we could extend the combination by more towers. |
https://github.com/TooAngel/screeps/blob/master/src/prototype_room_init.js#L192-L204 Problem is here. I'm going to re-work this. |
two example so far. I'll try to debug the code when I get a base far enough to build links.
The text was updated successfully, but these errors were encountered: