Implements NumberOfDocks and DockingOffset# for BuildingTypes.
#790
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
CCHyper
force-pushed
the
feature/ra2/dockingoffset
branch
from
7727cb6
to
abf4a66
Compare
|
This comment is automaticly generated by Nightly.link and allows non-registered users to get download the artifacts for this pull request. These links are also updated when the pull request is pushed to. |
CCHyper
force-pushed
the
feature/ra2/dockingoffset
branch
2 times, most recently
from
d1f4d86
to
a554022
Compare
CCHyper
force-pushed
the
feature/ra2/dockingoffset
branch
from
a554022
to
3ea99ae
Compare
CCHyper
force-pushed
the
develop
branch
2 times, most recently
from
07c9446
to
379970b
Compare
CCHyper
force-pushed
the
develop
branch
3 times, most recently
from
48cd2ea
to
b789478
Compare
CCHyper
force-pushed
the
feature/ra2/dockingoffset
branch
from
3ea99ae
to
1856cb7
Compare
CCHyper
force-pushed
the
develop
branch
3 times, most recently
from
d649039
to
5a6cb19
Compare
CCHyper
force-pushed
the
feature/ra2/dockingoffset
branch
from
1856cb7
to
381911d
Compare
|
Tested on Freeware TS and the TS Client. The only one currently working on Freeware TS is the Helipad; the Refinery and Waste Facility do not use the offsets for docking. In the TS Client, newly constructed units from the Helipad do follow the DockingOffset values, but when trying to land, they either land on the Helipad itself or stay hovering in the air trying to land at the DockingOffset coords. The Refinery and Waste Facility do not use their docking offsets either |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #786
This pull request implements
NumberOfDocksandDockingOffset#for BuildingTypes.NOTE1: This feature currently only applies to the following BuildingTypes;
- Structures with
Helipad=yes, whereDockingOffset0adjusts the docking position for aircraft. ANumberOfDocksvalue greater than1has no additional effect at this time.- Structures with
Refinery=yesorWeeder=yes, whereDockingOffset0adjusts the docking position for the harvester. ANumberOfDocksvalue greater than1has no additional effect.NOTE2: The default docking coord is offset from the center of the building for the following BuildingTypes;
-
Refinery=yesis offset by 128 leptons on the x-axis.-
Weeder=yesis offset by 512 leptons on the x-axis, and 256 leptons on the y-axis[BuildingType](RULES.INI)NumberOfDocks=<integer>- The number of docking locations this building has. Defaults to1for buildings withHelipad=yes, and0for all other buildings.[Image](ART.INI)DockingOffset#=<X,Y,Z>- The coord offset from the center of the building for the respective docking location. This list must contain the same number of entries as defined byNumberOfDocks, with#being replaced by the docking position starting from zero. Each entry defaults to0,0,0.