Changes between Version 3 and Version 4 of content/BigShip

Timestamp:

Dec 9, 2013, 6:54:44 PM (10 years ago)

Author:

noep

Comment:

—

content/BigShip

@@ +1 @@
+= Big Ships =
+
 A BigShip should consist of multiple parts which can be individually destroyed, and the state of the individual parts should alter the behaviour of the entire vessels systems, such as shield, weapons or engines.
 
@@ -26 +28 @@
  * Sub-parts of the ship (subsequently referred to as ''!ShipPart''), which are attached to either a !BigShip or a !ShipPart. They can interact with their parent-part in many ways.
 
+=== Desired final form ===
+
+Big ships should easily be assembled in an XML template like any other ship.
+
+Here an example how this could look:
+{{{
+<BigShip [parameters]>
+
+    <engines>
+        ...
+    </engines>
+   
+    <attached>   
+        <Model [parameters] />
+       
+        <ShipPart [parameters]>
+            <attached>
+                <Model [parameters] />
+            </attached>
+            <collisionShapes>
+                ...
+            </collisionShapes>
+        </ShipPart>
+       
+        <ShipPart [parameters]>
+            ...
+        </ShipPart>
+    </attached>
+   
+    <collisionShapes>
+        ...
+    </collisionShapes>
+   
+<BigShip>
+}}}
+
+The parameters of !BigShip and !ShipPart describe how the parts interact with each other. This requires many different functions, here's a few examples:
+ * Damage-sharing
+
+=== !BigShip ===
+
+The !BigShip class could be an extension of the existing !SpaceShip class.[[br]]
+Additionally to a normal spaceships functions, 
+
+=== !ShipPart ===
+
+
+
 == Problems ==