Repository navigation
KRPC.Bridge 2.1.0 and TowerCatch 1.1.0
This release still needs kRPC 0.7.0 (it does not load on kRPC 0.6.x). Two things change since 2.0.0:
- MechJeb leaves the bridge. The
conn.mech_jebservice and its pluginKRPC.Bridge.MechJeb.dll
are removed. If you still use them, stay on KRPC.Bridge 2.0.0. - The booster catch tower is entirely in
TowerCatch. The tower's plugin,KRPC.Bridge.Tower.dll
(the servicesconn.towerandconn.tower_site, unchanged), moves fromGameData/KRPC.Bridgeinto
GameData/TowerCatch/Plugins.KRPC.Bridgenow holds nothing of the tower; if you do not fly a tower you
install nothing more than the bridge, andTowerCatchis the tower's parts, its craft and its services in
one optional download. The plugin declares a dependency on the bridge's Core, so KSP loads it after it.
The release has two downloads, as before:
| File | What it is |
|---|---|
KRPC.Bridge-2.1.0.zip |
The mod. Required. |
TowerCatch-1.1.0.zip |
The whole booster catch tower: ModuleManager patch, craft and plugin. Optional. Needs KRPC.Bridge 2.1.0 or later. |
Upgrading from 2.0.0 (read this if you update by hand)
Delete your old GameData/KRPC.Bridge folder before you unzip the new one. If you prefer to update in
place, you must at least delete these four files from GameData/KRPC.Bridge/Plugins:
KRPC.Bridge.Tower.dllandKRPC.Bridge.Tower.xmlKRPC.Bridge.MechJeb.dllandKRPC.Bridge.MechJeb.xml
Why: the tower's plugin now lives in GameData/TowerCatch/Plugins. If the 2.0.0 copy stays in
GameData/KRPC.Bridge/Plugins, two assemblies declare the kRPC service Tower and TowerSite; kRPC refuses
the duplicate, and that takes the whole kRPC server down, not only the tower. (MechJeb's plugin is
harmless left in place, but nothing uses it any more.)
If you use a tower, install TowerCatch-1.1.0.zip too, the same way (GameData/TowerCatch/), and delete
GameData/TowerCatch of 1.0.0 first if you have it. Never keep a second copy of TowerCatch.cfg: two copies
make every tower part twice. If an older bridge left GameData/KRPC.Bridge/Patches and
GameData/KRPC.Bridge/Crafts, delete those two folders as well. The TG.* part names did not change: a tower
already in a save loads as before.
CKAN does all of this for you: TowerCatch 1.1.0 depends on KRPC-Bridge 2.1.0, and KRPC-Bridge 2.1.0
conflicts with TowerCatch 1.0.0 (whose plugin it no longer carries).
Requirements
- Kerbal Space Program 1.12.x (checked on 1.12.5)
- kRPC 0.7.0, and its Python client:
pip install "krpc>=0.7,<0.8" - Optional, each one only for its own service: FMRS Continued, Trajectories, OfCourseIStillLoveYou with
HullCamera VDS Continued. A mod you do not have makes its service reportavailable = False. - For
TowerCatchonly: ModuleManager, Modular Launch Pads, HullCamera VDS Continued, and the two paid
expansions Breaking Ground and Making History (CKAN can detect them, not install them).
Installation
-
Unzip
KRPC.Bridge-2.1.0.zipinto your KSP folder, so thatGameData/KRPC.Bridge/appears inGameData/
(after deleting the old folder, see above). Keep each.xmlnext to its.dll: kRPC reads it to build
the Python docstrings. -
Optional: unzip
TowerCatch-1.1.0.zipthe same way (GameData/TowerCatch/). -
Start KSP, start the kRPC server, and check:
import krpc conn = krpc.connect() print(conn.bridge.ping()) # "pong" print(hasattr(conn, "tower"), hasattr(conn, "tower_site")) # True True with TowerCatch, False False without
CKAN
The two records (distribution/KRPC.Bridge.netkan, distribution/TowerCatch.netkan) pick their own zip of
this shared release by name and take their own version from it (KRPC-Bridge 2.1.0, TowerCatch 1.1.0), ask
for kRPC v0.7.0 as CKAN numbers it, and TowerCatch declares the Making History and Breaking Ground
expansions (MakingHistory-DLC, BreakingGround-DLC).
See CHANGELOG.md for the detail.
Files
| File | Size | sha256 |
|---|---|---|
KRPC.Bridge-2.1.0.zip |
458 295 bytes | bc57018c4d3c500a41a57feb1a29ec2770bd6d1e75b4a3db0d9a1f183d4a2f10 |
TowerCatch-1.1.0.zip |
92 335 bytes | da73b9a9b982ad0955b0920fd4f6cae4886a574c90d4d9904553b4c22ead1083 |
Both zips were built from commit 7292b0bd93a7129f7263450fbbbc9bc19b12ea0d; the manifest.json inside each
gives the sha256 of every file it ships.