Difference between revisions of "SAC 3"
From FreeSpace Wiki
(Container info added) |
Muninn Crow (talk | contribs) |
||
(2 intermediate revisions by the same user not shown) | |||
Line 21: | Line 21: | ||
| 243 m | | 243 m | ||
|} | |} | ||
+ | ==Modding Resources== | ||
+ | {{shipimage|image=[[Image:HTLSAC3.png]]|caption=4.5.10 SC SAC3}} | ||
+ | '''Retail''':<br> | ||
+ | :$POF File: cargo2s-01.pof <br> | ||
+ | :Textures: tile1, cargo1, cargo 2, tile 1c, cargo1c, cargo2c, damage<br> | ||
+ | '''MediaVP 4.5.10''':<br> | ||
+ | :$POF File: cargo2s-01.pof<br> | ||
+ | :Textures: cargo1, CorvSTile1, tile3, CorvSTile4, tile 4, CorvSTile5<br> | ||
+ | Credits: Galemp, StratComm | ||
+ | [History]<br> | ||
+ | First WIP Post: Galemp on Dec14, 2005<br> | ||
+ | First In-Game Model: ??? on ???<br> | ||
+ | Completed In-Game Model: ??? on ???<br> | ||
+ | Final Corrections: StratComm on Jan13, 2006<br> | ||
[[Category:Ship]] | [[Category:Ship]] |
Latest revision as of 20:39, 9 October 2023
| ||||||||
|
SAC 3 |
---|
The SAC 3 is carried by SFr Dis.
Contents
Description:
FS2 Tech Room Description
The SAC 3 is the most common Shivan cargo container found thus far. Its thin plating is barely enough to maintain the interior atmospheric integrity against the vacuum of space. As no additional effort was made to armor these containers against attack, it is assumed that only items of low value or importance are carried within. Nevertheless, standing orders are to capture these containers at every opportunity, unless mission orders specifically dictate otherwise.
Developer Notes
N/A
Statistics
Hitpoints | 300 |
Length | 243 m |
Modding Resources
4.5.10 SC SAC3 |
---|
Retail:
- $POF File: cargo2s-01.pof
- Textures: tile1, cargo1, cargo 2, tile 1c, cargo1c, cargo2c, damage
MediaVP 4.5.10:
- $POF File: cargo2s-01.pof
- Textures: cargo1, CorvSTile1, tile3, CorvSTile4, tile 4, CorvSTile5
Credits: Galemp, StratComm
[History]
First WIP Post: Galemp on Dec14, 2005
First In-Game Model: ??? on ???
Completed In-Game Model: ??? on ???
Final Corrections: StratComm on Jan13, 2006