MOUSE INTO SPACE MODULAR ROCKET
Version 0.1.0 - for Kerbal Space Program 1.12.x

This is a modular, fan-made reconstruction of the rocket in the supplied Tom
and Jerry short, Mouse into Space. The red and white stages are separate fuel
tank parts with open engine bays. Attach your own stock or mod engines. The
gold nose is optional: add another stage or a payload in its place.

The package contains 18 original parts, three engine-free craft assemblies,
editable mesh/source files, and a timestamped visual reference sheet.

INSTALL

1. Close KSP.
2. Copy the MouseIntoSpace folder inside this package's GameData folder into
   your KSP installation's GameData folder. The result must be:
   GameData/MouseIntoSpace/Parts and GameData/MouseIntoSpace/Models.
3. To use the assembly templates, copy the .craft files from Ships/VAB into
   saves/<your save>/Ships/VAB inside your KSP installation.
4. Start KSP and search for MIS in the VAB. The stage bodies are in Fuel Tanks,
   release rings in Coupling, adapters in Structural, and the gold command
   nose/inline avionics in Pods.

There are no required plugins, ModuleManager patches, DLC parts, or bundled
third-party engine parts. The playable parts use stock KSP modules and shaders.
Your chosen engine mod must be installed if you use its engines.

The provided craft are ASSEMBLY TEMPLATES. Their engine sockets are empty.
They are not ready to launch until you install engines and arrange ignition.

PARTS AND SCALE

The scale uses a 3.75 m base diameter. It is a gameplay choice based on the
drawn proportions, not a claim about the cartoon rocket's real dimensions.
The circular bodies have 24 sides.

Primary stages, listed from bottom to top:

  MIS 1 - White Launch Stage
    Height 4.15 m; diameter 3.75 m below to 3.50 m above.
    Engine mounting deck 0.65 m above the bottom rim.
    LiquidFuel 2250 units; Oxidizer 2750 units; dry mass 3.125 t.

  MIS 2 - Red Sustainer Stage
    Height 4.90 m; diameter 3.50 m below to 3.125 m above.
    Engine mounting deck 2.20 m above the bottom rim.
    LiquidFuel 1260 units; Oxidizer 1540 units; dry mass 1.750 t.

  MIS 3 - White Upper Stage
    Height 3.35 m; diameter 3.125 m below to 2.50 m above.
    Engine mounting deck 1.30 m above the bottom rim.
    LiquidFuel 630 units; Oxidizer 770 units; dry mass 0.875 t.

  MIS 4 - Red Orbital Stage
    Height 2.25 m; diameter 2.50 m below to 1.625 m above.
    Engine mounting deck 0.80 m above the bottom rim.
    LiquidFuel 180 units; Oxidizer 220 units; dry mass 0.250 t.

Optional repeat stages:

  MIS R - Repeatable Red Stage
  MIS W - Repeatable White Stage
    Each is 2.60 m high and 1.625 m in diameter at both ends.
    Each engine mounting deck is 1.00 m above the bottom rim.
    Each holds LiquidFuel 180 units and Oxidizer 220 units; dry mass 0.250 t.

Other parts:

  Five hollow interstage release rings: 3.75, 3.50, 3.125, 2.50 and 1.625 m.
  One gold command nose: 1.625 m base, 1.35 m high.
  One flat inline avionics ring: 1.625 m diameter, 0.16 m high.
  Five structural adapters from 1.625 m to 1.25, 2.50, 3.125, 3.50 and 3.75 m.

The gold nose and inline avionics both provide uncrewed control, SAS,
1.5 kNm reaction wheels, 250 EC and a stock internal antenna. They have no crew
seats or IVA. Add electrical generation and an appropriate antenna for longer
missions. A bare stage is a fuel tank and does not provide command authority.

BUILD THE REFERENCE ROCKET

The simplest starting point is MIS_Four_Stage_Assembly.craft. Its nine parts
are already attached, and its four release rings have staging enabled.

For manual assembly, work from the gold nose downward:

1. Gold command nose.
2. 1.625 m release ring.
3. Red orbital stage (MIS 4).
4. 2.50 m release ring.
5. White upper stage (MIS 3).
6. 3.125 m release ring.
7. Red sustainer stage (MIS 2).
8. 3.50 m release ring.
9. White launch stage (MIS 1).

Each stage has THREE stack nodes. The top node accepts the next part above.
The lowest bottom-rim node accepts the release ring below. The separate
ENGINE node sits higher inside the open aft bay. Attach the engine's top node
to this inner node. Attach the release ring to the lower rim node, not to the
engine. The engine and the release ring are separate branches of the upper
tank's attachment tree.

To access an inner engine socket in the VAB, temporarily remove the lower
subassembly, attach the engine to the visible recessed deck, then reattach the
lower subassembly to the outer bottom-rim node. Inspect the side view before
launch: the upper engine bell must fit inside its own stage's bay above the
next tank's top. The lowest engine may protrude below the launch stage.

The rings release their TOP joint. Each ring remains with the discarded lower
tank; the upper engine remains attached to its own tank. Fuel crossfeed across
the rings is disabled, so lower engines cannot drain upper-stage tanks through
the stack. Fuel still flows normally between an engine and its own tank.

ENGINES AND CLEARANCE

There are no modeled engine bells or active engines in the supplied stage
bodies. The engine part you attach supplies thrust, gimbal, fuel demand, sounds
and plumes. The stock Mainsail, Swivel, Terrier and Spark are useful families to
consider for the progressively smaller bays, but this release does not assert
that every model, variant or mod replacement fits those bays or provides a
suitable thrust-to-weight ratio. Check both dimensions and performance.

For each upper engine, compare its full length below its top attachment node
against the bay depth above. Include the engine bell's width and gimbal sweep.
The compact repeat-stage bays have approximately 1.50 m minimum clear diameter;
use centered compact engines and inspect their actual bell shape. A nominal
1.25 m engine can have a bell wider than its nominal attachment diameter.

Stock or mod engines are mechanically attachable, but fuel compatibility is
separate. These tanks contain LiquidFuel/Oxidizer in the stock 9:11 ratio. An
engine that burns hydrogen, methane, xenon, solid fuel or another resource
requires the appropriate fuel supply or a compatible fuel-switch setup.

Full tank capacity does not guarantee adequate thrust with a small engine.
Use the VAB's stage delta-v and TWR display with your chosen engines, or use
your installed flight-planning mod. Reduce fuel, select stronger engines, or
alter the mission when needed. This version includes no claimed orbital
performance, payload rating, or completed flight test.

Do not attach a lower stage through an engine's lower node if you want the
custom shell's separation behavior. If an engine automatically generates its
own overlapping shroud, disable that shroud in the engine's part window when
the engine supports this option.

STAGING

Ignition and separation are separate actions. Shut down a running lower-stage
engine before releasing its stage. After release, allow visible clearance
before igniting the upper engine. Do not put an upper engine's ignition into
the same staging event as its surrounding lower stack's release.

In the four-stage template, the release rings are assigned to stages 6, 4, 2
and 0. After adding your engines, arrange the following sequence in the VAB
(higher stage numbers fire first):

  Stage 7: ignite MIS 1's engine.
  Stage 6: release MIS 1 at the 3.50 m ring.
  Stage 5: ignite MIS 2's engine after clearance.
  Stage 4: release MIS 2 at the 3.125 m ring.
  Stage 3: ignite MIS 3's engine after clearance.
  Stage 2: release MIS 3 at the 2.50 m ring.
  Stage 1: ignite MIS 4's engine after clearance.
  Stage 0: release the gold command nose at the 1.625 m ring.

KSP can renumber or compress stages when empty slots are removed or new engines
are attached. Verify the event order and the individual icons after building.
No automatic staging plugin or elapsed-time script is included.

REPLACE THE CONE WITH ANOTHER STAGE

The top of MIS 4 and both repeat stages is 1.625 m. Red or white repeat stages
can be installed there using a 1.625 m release ring. Repeat them in any chosen
order, or use one of the adapters to mount another primary stage or payload.

For a larger MIS primary stage, place the appropriate rigid adapter above the
1.625 m top, then the matching release ring, then the new stage's bottom rim.
The correctly sized ring is immediately BELOW the added stage's bottom lip;
the adapter is BELOW that ring:

  Additional MIS 4: 1.625-to-2.50 m adapter and 2.50 m MIS ring.
  Additional MIS 3: 1.625-to-3.125 m adapter and 3.125 m MIS ring.
  Additional MIS 2: 1.625-to-3.50 m adapter and 3.50 m MIS ring.
  Additional MIS 1: 1.625-to-3.75 m adapter and 3.75 m MIS ring.

The adapters are hollow flares. If an engine extends below its own stage's
bay, its entire bell and gimbal envelope must fit through the release ring
and inside the actual flare/throat, and must clear the lower stage. An adapter's
large top diameter does not imply that the same diameter is available through
its narrower throat. Inspect the completed stack before flight.

The 1.25 m adapter accepts standard-sized payloads; use your own 1.25 m
decoupler if separation is wanted. These adapters are fixed structures and do
not stage by themselves. A larger added upper stage can make the vehicle
top-heavy and alter aerodynamics; size its engines and lower stages accordingly.

When the gold nose is omitted, add the inline avionics ring or another command
part. The avionics ring is solid: place it above the topmost powered stage,
never under an engine or in its exhaust path. MIS_Open_Top_Stage_Swap.craft
demonstrates this: the rocket ends in inline avionics above a red then a white
repeat stage, leaving the top node for your own
payload. Its release events are 9, 7, 5, 3 and 1; assign the six engine ignitions
to 10, 8, 6, 4, 2 and 0 respectively.

MIS_Repeated_Stage_Assembly.craft keeps the gold nose above both repeat stages.
Its six release events are 10, 8, 6, 4, 2 and 0; assign the six engine ignitions
to 11, 9, 7, 5, 3 and 1. These alternatives are customizable examples, not a
claim that six body bands are visible in the original pad shot.

REFERENCE INTERPRETATION

The supplied video is MIS edited.ia (1).mp4. The pad view near 01:10 shows four
colored body sections beneath a yellow cone. The first bottom section detaches
around 01:59.9-02:00.0. The rapid sequence around 02:08-02:12 repeatedly sheds
whole red and white sections, and the yellow cone is alone by about 02:13.2.
The repeated drops exceed the number of body bands visible on the launch pad.

This mod therefore separates the four-section pad reconstruction from optional
repeatable stages. It does not treat the transverse stage bodies as split
fairing halves. The sampled pad/ascent views do not show fins. The inhabited
cartoon cone is adapted here as an optional uncrewed KSP control part.

Timestamps identify decoded still-frame seek targets, not independently
verified exact presentation timestamps. See Reference/reference_notes.txt
and Reference/final_reference_sheet.png for the visual evidence. The complete
video and its audio are not redistributed in this package.

VALIDATION AND LIMITS

The release includes binary mesh checks and static configuration/craft checks.
They check exported assets and connections, but do not replace loading the
mod in the actual game. KSP was not run in this build environment. In-game
part loading, physics separation, aerodynamic balance, heat behavior, command
signal, engine clearance and a completed flight remain unverified.

The nose is not an ablative reentry capsule, has no parachute, and has no IVA.
Attach mission-specific recovery, communications and power hardware as needed.
No animated cone hatch, cartoon characters, or custom engine implementation is
included in this version.

SOURCE AND LICENSING

Source/ contains the mesh-building scripts, dimensional specification, OBJ
exports and configuration/craft builder. Source/io_object_mu/mu.py comes from
taniwha/io_object_mu, with its GPL-2.0-or-later notice preserved and its full
license in Source/io_object_mu/COPYING. Its upstream provenance is recorded in
Source/upstream_provenance.json. Keep these files and notices with the source.
The reference-film frames are evidence supplied by the user and are not relicensed
by the bundled exporter's software license. This fan reconstruction is unaffiliated
with the cartoon's rights holders or the developers of KSP.

Technical references:
  https://github.com/taniwha/io_object_mu
  https://kspmoddinglibs.github.io/KSPDocsSite/class_module_decouple.html
  https://github.com/KSP-RO/RealismOverhaul/blob/master/GameData/RealismOverhaul/RO_RecommendedMods/Procedurals/RO_pFairings.cfg

CHANGELOG

0.1.0 - 2026-11-11
  Initial original-mesh reconstruction from the supplied video.
  Four tapered red/white stages and two repeatable compact stages.
  Separate engine mounting nodes and open aft engine bays.
  Five staged release rings, five adapters, optional cone and inline avionics.
  Three engine-free assembly templates with explicit release-event assignments.
  Source files, selected visual references and static validation reports.
