鹦鹉螺：修订间差异

由圣盾动力制造的大型飞船
无编辑摘要
无编辑摘要
 
（未显示1个用户的5个中间版本）
第1行： 第1行：
{{等待翻译|翻译者=}}
{{Infobox vehicle
{{Infobox vehicle
| name = 鹦鹉螺
| name = 鹦鹉螺
| english = Nautilus
| english = Nautilus
| image = Nautilus - Deploying mines - Front Starboard.png
| image = Nautilus - Deploying mines - Front Starboard.png
| size = Large
| size = 大型
| manufacturer = AEGS
| manufacturer = AEGS
| role = Minelayer
| role = 布雷舰
| productionstate = 概念中
| productionstate = 概念中
| productionstatedesc =  
| productionstatedesc =  
第31行： 第30行：
}}
}}


[[Aegis|圣盾动力]] '''鹦鹉螺''' 是一艘大型布雷舰，具备完全集成的布雷、扫雷和拆除能力。最初于2549年引入使用，经过几个世纪的改进，于2949年重新推出以庆祝其400周年的服役。<ref name="ReferenceA">{{Cite RSI|url=comm-link/transmission/17203-Aegis-Nautilus|text=Aegis Nautilus Comm-link}}</ref>
[[Aegis Dynamics]] '''鹦鹉螺''' 是一艘大型布雷舰，具备完全集成的布雷、扫雷和拆除能力。最初于2549年引入使用，经过几个世纪的改进，于2949年重新推出以庆祝其400周年的服役。<ref name="ReferenceA">{{Cite RSI|url=comm-link/transmission/17203-Aegis-Nautilus|text=Aegis Nautilus Comm-link}}</ref>


== 手册说明 ==
== 手册说明 ==
第39行： 第38行：


<tabber>
<tabber>
Avionics & Systems=
飞船设备&系统=
{{Vehicle avionics
{{Vehicle avionics
| radarcount = 1
| radarcount = 1
第70行： 第69行：
}}
}}
|-|
|-|
Propulsion & Thrusters=
航行设备&推进系统=
{{Vehicle propulsion
{{Vehicle propulsion
| fuelintakecount = 1
| fuelintakecount = 1
第104行： 第103行：
| mainthruster1size = 3
| mainthruster1size = 3
| mainthruster1manufacturer =  
| mainthruster1manufacturer =  
| mainthruster1name = Main Thruster
| mainthruster1name = 主推进器
| mainthruster2quantity = 4
| mainthruster2quantity = 4
| mainthruster2size = 3
| mainthruster2size = 3
| mainthruster2manufacturer =  
| mainthruster2manufacturer =  
| mainthruster2name = VTOL Thruster
| mainthruster2name = 垂直推进器
| maneuveringthruster1quantity = 2
| maneuveringthruster1quantity = 2
| maneuveringthruster1size = 3
| maneuveringthruster1size = 3
| maneuveringthruster1manufacturer =  
| maneuveringthruster1manufacturer =  
| maneuveringthruster1name = Retro Thruster
| maneuveringthruster1name = 反推进器
| maneuveringthruster2quantity = 12
| maneuveringthruster2quantity = 12
| maneuveringthruster2size = 2
| maneuveringthruster2size = 2
| maneuveringthruster2manufacturer =  
| maneuveringthruster2manufacturer =  
| maneuveringthruster2name = Fixed Maneuvering Thruster
| maneuveringthruster2name = 固定机动推进器
}}
}}
|-|
|-|
Weaponry=
武器=
{{Vehicle weaponry
{{Vehicle weaponry
| weaponcount = 0
| weaponcount = 0
第159行： 第158行：
</tabber>
</tabber>


== Features ==
== 功能 ==


*'''Mine Control Room''': A fully-developed control room for the queuing and deployment of the Nautilus' payload.
*'''完善的水雷控制室''': 一个完整的控制室，用于对鹦鹉螺的载荷进行排序和部署。
*'''Crew Comfort''': A mess hall, crew quarters, and captain's quarters are designed for long-term comfort on deep-space missions and operations.
*'''舒适的生活环境''': 一间餐厅，船员居住区和舰长宿舍为长期的深空任务提供了舒适度的保障
*'''Defensive Turrets''': three manned turrets with 2x S3 guns each, and a front-mounted manned turret with S7 guns keeps the Nautilus protected in the hottest of deployment or disarming zones.<ref name="ReferenceA">{{Cite RSI|url=comm-link/transmission/17203-Aegis-Nautilus|text=Aegis Nautilus Comm-link}}</ref>
*'''充沛的自卫火力''': 配备了三个载人炮塔，每个炮塔上装有两门S3型号的火炮，以及前置的载人炮塔，装备有两门S7型号的火炮，以确保在最危险的布雷或排雷区域中保护鹦鹉螺的安全。<ref name="ReferenceA">{{Cite RSI|url=comm-link/transmission/17203-Aegis-Nautilus|text=Aegis Nautilus Comm-link}}</ref>


=== Deployables ===
=== 可部署物 ===


{| class="wikitable"
{| class="wikitable"
!Image
!图片
!Type
!类型
!Description
!描述
|-
|-
|[[File:Nautilus - Homing Mine - TransparentCropped.png|center|frameless|100x50px]]
|[[File:Nautilus - Homing Mine - TransparentCropped.png|center|frameless|100x50px]]
|Homing Mine
|制导水雷
|The [[Firestorm Kinetics]] [[Tephra Homing Mine]] is a mine that once within range, will move towards the target and detonate. Its primary role is to establish a defensive perimeter. This mine has the same destructive power as a size 5 torpedo.
|[[Firestorm Kinetics|火焰风暴动力学]]的 [[Tephra Homing Mine｜火山灰水雷]]会在敌对目标进入范围后向目标移动并引爆，其主要作用是建立外围防御。这种水雷的主要作用是建立外围防御。它具有与一枚5号鱼雷相当的破坏力。<br>
|-
|-
|[[File:Nautilus - Nemo Drone - TransparentCropped.png|center|frameless|100x50px]]
|[[File:Nautilus - Nemo Drone - TransparentCropped.png|center|frameless|100x50px]]
|NEMO Drone
|"尼莫"无人机
|The [[Saga Datasystems]] [[NEMO Drone]] (Neutralize and Employ Mine Ordnance) is a drone specifically designed for the task of identifying, deactivating and collecting deployed mines. In accordance with amendment 17c1 of the [[Militia Mobilization Initiative]], a mine retrieval device must be present and functional aboard all armed minelaying craft.
|[[Saga Datasystems|萨迦数据系统]]的[[NEMO Drone|尼莫无人机]]是一种专门设计用于识别、停用和收集已部署地雷的无人机。根据民兵动员计划的17c1修正案，所有装备有布雷功能的武装布雷船只必须配备并正常运行水雷回收装置。
|-
|-
|[[File:Nautilus - Sentry Mine - TransparentCropped.png|center|frameless|100x50px]]
|[[File:Nautilus - Sentry Mine - TransparentCropped.png|center|frameless|100x50px]]
|Sentry Mine
|哨戒水雷
|The [[Behring]] [[VLR-11 Sentry Mine]] is a mine fitted with weapons that will fire on hostile targets when within range. Its primary role is perimeter defense. The sentry can house 2x size 2 guns.
|[[Behring|贝林财团]]的[[VLR-11 Sentry Mine｜VLR-11哨戒水雷]]是一种装备了武器的水雷，当敌对目标进入其射程范围时，它会对其进行攻击。其主要作用是建立外围防御，其可以搭载两门尺寸2的火炮。
|}
|}


== History ==
== 历史 ==


<tabber>
<tabber>
  Debut=
  首次亮相=
{| class="wikitable"
{| class="wikitable"
|-
|-
The Nautilus was introduced in [[26th century|2549]], at a time when tensions between the [[UEE]] and the recently discovered [[Xi'an empire]] had increased. Before that time, space mines were slowly coming to prominence as an effective form of defense. Particularly during the [[First Tevarin War]], where combat engineers utilized repurposed freighters and troop transporters to deploy improvised proximity mines. Taking this as inspiration, initial concepts of the ship featured expansive holds for large volumes of explosive distribution. However, feedback from the crew themselves led Aegis to focus on precision over volume instead.
鹦鹉螺于[[26th century|2549]]年推出，当时UEE与新发现的希安帝国之间的紧张局势加剧。在此之前，太空水雷作为一种有效的防御形式逐渐崭露头角。特别是在第一次塔维因战争期间，作战工程师利用改装过的货船和部队运输舰部署了临时的近炸水雷。受此启发，该船最初的概念中设有宽敞的货舱，用于储存大量的爆炸物。然而，来自机组人员的反馈使得圣盾动力公司决定将制导的精确性置于负载之上。
|}
|}
|-|
|-|
  Perry Line=
  佩里防线=
{| class="wikitable"
{| class="wikitable"
|-
|-
After its debut, in the midst of the Human-Xi'an conflict, the ship was utilized in countless successful missions along the [[Perry Line]] between 2550 and 2793. Despite this, the Nautilus ships were far from refined. Aegis would remedy that over the following generations. One such improvement was the addition of a conveyor belt in 2555. This would move mines into place for deployment. Previously this would have been done with a trolley system, and proved too slow and cumbersome. But even the belts had its problems, as they would often jam. In 2601 this was replaced with an overhead rail system. This system proved itself very useful in [[Operation Blindside]] by the naval ship [[Peace]]. This operation is noted for the heavy mining of the [[Tohil system|Tohil]] asteroid belt that resulted in the accidental elimination of the violent pirate crew the [[Big Hats]].
在其首次亮相后，在人类与希安人的冲突中，该船在2550年至2793年之间于[[Perry Line]]进行了无数次成功的任务。尽管如此，鹦鹉螺的系统远未完善。圣盾动力在后续的几代中进行了改进以解决这个问题。其中一项改进是在2555年增加了一个传送带。该传送带用于将水雷放置到指定位置。之前这是通过一个推车系统完成的，速度过慢且笨重。然而，即使有了传送带，也存在问题，因为它们经常会卡住。在2601年，这个系统被一个高架轨道系统所替代。这个系统在[[Operation Blindside|盲点行动]]中由海军舰船[[Peace|UEES 和平号]]证明了其作用。该行动以对[[Tohil system|Tohil|托希尔系统]]的小行星带的大规模布雷而闻名，结果意外消除了暴力海盗团队[[Big Hats|大帽子]]。


Later revisions saw the addition of a sentry mine, which proved successful in being a more sustainable and less destructive counterpart to the proximity mines. Even the onboard facilities evolved much over time. Original Nautilus models had a lower payload capacity, because they were mostly designed for short runs. As technology advanced, and crews became more precise and strategic, the need to return home to rearm was decreased. The quarters and facilities were soon expanded for much longer tours.
后续的修改版本中增加了哨戒水雷*自行防空炮*，这是一种更可持续且破坏性较小的近炸鱼雷的替代品，并取得了成功。即使船上的设施也随着时间的推移而发展。最初的鹦鹉螺型号由于主要设计用于短期任务，所以其有效载荷能力较低。随着技术的进步和机组人员变得更有经验，他们减少了返回基地重新装备的需求。船内的住宿和设施很快扩展到让鹦鹉螺可以进行更长时间的巡航的程度。
|}
|}
|-|
|-|
Second Tevarin War=
第二次塔维因战役=
{| class="wikitable"
{| class="wikitable"
|-
|-
During the [[Second Tevarin War]], the Nautilus was given its first real test in open warfare. The ship was originally designed to deter traditional battles rather than to participate in them. The extreme aggression of the [[Tevarin]] forced Aegis to adapt and refine their proximity mines. Homing functionality saw its first iterations, and proved useful and enduring. In spite of (and thanks to) a handful of missteps (like a backfiring mine during the battle of [[Voska]]), this period provided an unprecedented opportunity to refine form and function of the Nautilus.
在[[Second Tevarin War|第二次塔维因战争]]期间,鹦鹉螺首次在公开战争中面临了实战考验。这艘船最初的设计目的是喝止传统战斗的发生，而不是参与其中。然而塔维因人的极端攻击手段迫使圣盾动力不得不对其近炸水雷进行调整和改进。水雷自导功能自此亮相，并证明其在战斗中的效用和持久性。尽管在[[Voska|沃斯卡]]战役中遭遇了一些挫败（比如地误伤友军的水雷），但这一时期为完善鹦鹉螺的形态和功能提供了前所未有的机会。


{{Quote|As our situation changes, we must adapt in order to effectively address the shifting priorities, strategies, and ferocity of our enemies, whoever they may be. As we strive to adapt designs to suit these ends, we hope to use the combined knowledge of past contention to continue refining the Nautilus, its systems, and its capabilities, with the ultimate goal of creating a package versatile enough to effortlessly adapt on the fly to any conceivable threat or situation.|[[Mila Aukerman]], Lead Development Engineer<ref name="ReferenceA">{{Cite RSI|url=comm-link/transmission/17203-Aegis-Nautilus|text=Aegis Nautilus Comm-link}}</ref>}}
{{Quote|随着战局的变化，我们必须适应以有效地应对不断变化的优先事项、战术和敌人的凶猛攻击，无论他们是谁。在努力调整设计以适应这些目标的同时，我们希望利用过去战役的综合知识来不断完善鹦鹉螺的系统和能力，最终目标是创建一艘多功能的“解决方案”，并能够轻松应对任何可想象的威胁或情况。|[[Mila Aukerman｜米拉·奥克曼]]，首席开发工程师<ref name="ReferenceA">{{Cite RSI|url=comm-link/transmission/17203-Aegis-Nautilus|text=Aegis Nautilus Comm-link}}</ref>}}
   
   
The [[Centauri system|Battle of Centauri]] also featured a primary role for the Nautilus, although often not covered in schooling. In the time preceding the famous battle, valuable intel was intercepted detailing the enemy's attack plans, and a sapper squadron named the [[Blackhearts]], used this intel to lay fields of proximity charges at key entry points around the system. They intentionally left subtle routes through this 'maze' that allowed UEE interdiction units to lure the enemy into the minefield. This destruction caused a large portion of the enemy forces to not reach the battle and ultimately lead to the UEE's victory.
[[Centauri system|Battle of Centauri｜半人马之战]]一样给了鹦鹉螺一次证明自己的机会尽管这通常没有被提及。在这场著名战斗之前，一些有价值的情报被截获，详细描述了敌人的攻击计划，一个名为[[Blackhearts｜黑心]]的工兵中队利用这些情报在系统周围的关键跳跃点布置了近炸装置。他们有意在这个“迷宫”中留下一些微妙的路径，让UE的拦截部队将敌人引入水雷区。这一破坏行动导致敌军的大部分力量未能到达战场，最终帮助人类取得了胜利。
|}
|}
|-|
|-|
Vanduul War=
剜度氏族之战=
{| class="wikitable"
{| class="wikitable"
|-
|-
Even since the fateful [[Vega system|Vega]] conflict with the [[Vanduul]] in [[30th century|2945]], the Nautilus played a crucial role in many battles in the ongoing [[Vanduul War]], even though much of the sapper crews came and went unnoticed. One such example is the mission known as the [[Hellkite Run]]. Its purpose was to cut off Vanduul escape routes out of [[Oberon system|Oberon]]. An entire Vanduul squadron was eliminated trying leave the system to refuel and rearm. To this day, Nautilus sapper crews continue to maintain defense of the Oberon system, amongst others.
自从[[30th century|2945]]年起，在[[Vega system|Vega|维加系统]]中与[[Vanduul]]的战役从未休止过 鹦鹉螺在许多[[Vanduul War]]中发挥了关键作用，尽管许多工兵人员往来无闻。其中一个例子是被称为[[Hellkite Run]]的任务。它的目的是切断Vanduul在[[Oberon system|Oberon\奥伯龙系统]]中的逃生路线. 整个剜度中队试图离开该系统进行加油和补给时被消灭。直至今日，鹦鹉螺的船员们仍在继续维护该系统的防御工作。
|}
|}
|-|
|-|
Militia Mobilization Initiative=
民兵动员计划=
{| class="wikitable"
{| class="wikitable"
|-
|-
When the UEE announced their [[Militia Mobilization Initiative]] in 2946, Aegis started declassifying and marketing the ship to the general public. Due to several incidents involving private ships being damaged and lost when visiting systems previously touched by war, one amendment to the initiative stipulates that all currently in-production ships with minelaying functionality must be equipped with the means to disarm and/or remove their payloads. One example of such an incident is the loss of astronomer [[Katherine Ellen]] and her crew. their ship was destroyed during a live broadcast detailing the dangers of travel routes through the [[Hadrian system]], caused by a disturbed mine. After the amendment, previously dangerous locations can be more easily cleared of residual ordnance. The latest 2949 edition of the Nautilus therefore comes standard with a minesweeping drone.
当UEE于2946宣布[[Militia Mobilization Initiative|民兵动员计划]]时，圣盾动力开始解密一部分鹦鹉螺的机密技术并向普通公众进行市场推广。由于涉及私人船只在之前受到战争影响的星系中遭受破坏和丧失的事件，民兵动员计划的一项修正规定，所有目前正在生产的具有布雷功能的船只必须配备解除和/或清除其载荷的手段。其中一个例子是天文学家[[Katherine Ellen|凯瑟琳艾伦]]和她的船员在一次介绍[[Hadrian system｜哈德良系统]]的危险性的现场直播中被诡雷爆炸波及死亡, 修正案通过之后，战前危险的地点可以更容易地被“善后”。因此，最新的2949版鹦鹉螺配备了一台扫雷无人机作为其标准配置。
<ref name="ReferenceA">{{Cite RSI|url=comm-link/transmission/17203-Aegis-Nautilus|text=Aegis Nautilus Comm-link}}</ref>
<ref name="ReferenceA">{{Cite RSI|url=comm-link/transmission/17203-Aegis-Nautilus|text=Aegis Nautilus Comm-link}}</ref>
|}
|}
</tabber>
</tabber>


== Model ==
== 模型 ==


=== Special editions ===
=== 特殊版本 ===


'''Nautilus Solstice Edition"'''
'''冬至鹦鹉螺"'''
{| class="wikitable"
{| class="wikitable"
|-
|-
|[[File:Nautilus - Solstice Skin - Transparent - Front Starboard.png|center|frameless|100x67px]]
|[[File:Nautilus - Solstice Skin - Transparent - Front Starboard.png|center|frameless|100x67px]]
|Limited edition exclusive to members of the [[Chairman's Club]] and includes sequential serial numbering according to production order.<ref>{{Cite RSI|url=https://robertsspaceindustries.com/pledge/ships/aegis-nautilus/Nautilus-Solstice-Edition|text=Nautilus Solstice Edition - pledge store|accessdate=2020-03-28}}</ref>
|限量版供应，仅供礼宾俱乐部购买，根据出厂顺序进行编号<ref>{{Cite RSI|url=https://robertsspaceindustries.com/pledge/ships/aegis-nautilus/Nautilus-Solstice-Edition|text=Nautilus Solstice Edition - pledge store|accessdate=2020-03-28}}</ref>
|}
|}


== Pledge price history ==
== 购买价格历史 ==


{| class="wikitable"
{| class="wikitable"
!Date
!Date
!Pledge cost (USD)
!购买价格 (USD)
!Insurance
!保险
!Availability
!可用性
!Sale
!出售时间
|-
|-
|2020-05-26
|2020-05-26
|725
|725
|120 months
|120月
|Time-limited
|限时
|Invictus 2950 <ref>{{Cite RSI|url=comm-link/transmission/17595-Invictus-2950|text=Invictus 2950 Sale}}</ref>
|Invictus 2950 <ref>{{Cite RSI|url=comm-link/transmission/17595-Invictus-2950|text=Invictus 2950 Sale}}</ref>
|}
|}


== Gallery ==
== 画廊 ==
{{for|a full gallery|:Category:Nautilus images}}
{{for|a full gallery|:Category:Nautilus images}}


<tabber>
<tabber>
  Official=
  官方=
{{gallery
{{gallery
|Nautilus - In formation attacking in battle - Port.jpg
|Nautilus - In formation attacking in battle - Port.jpg
第285行： 第284行：
}}
}}
|-|
|-|
In-game=
游戏内=
{{gallery
{{gallery
|IAE2950-day2-holosuite-nautilus.jpg
|IAE2950-day2-holosuite-nautilus.jpg
第296行： 第295行：
</tabber>
</tabber>


== References ==
== 引用 ==
{{Reflist}}
{{Reflist}}


2024年3月25日 (一) 20:07的最新版本

Nautilus - Deploying mines - Front Starboard.png
生产状态
概念中
鹦鹉螺
制造商圣盾动力 (AEGS)
英文名Nautilus
定位布雷舰
尺寸大型
借用载具锤头鲨, 复仇者 泰坦
载量
载人量4 – 8
载货量64 SCU
价格
购买
无法购买
单船价格
$725
原始售价
$725
战争债券
$675
原始战争债券售价
$675
可用性
限时销售
索赔时间
不可用
租用
无法租用
规格数据
长度
125 m
宽度
72 m
高度
21.6 m
质量
13,526,320 kg
载具血量
未获取数据
最大氢燃料量
未获取数据
最大速度
未获取数据
传闻
初次出现公元2549年; 405年 前 (2549)
WikimediaUI-Globe.svg相关网站

官方网站

圣盾动力 鹦鹉螺 是一艘大型布雷舰，具备完全集成的布雷、扫雷和拆除能力。最初于2549年引入使用，经过几个世纪的改进，于2949年重新推出以庆祝其400周年的服役。[1]

手册说明

尽管不像圣盾动力最著名的一些退役军舰那样具备经典的吸引力，且最初被划分为为在边缘地区执行任务的舰船，其强大的火力和持久的续航使鹦鹉螺常常能给敌方出其不意的一击

规格

Radarnav.svg雷达
1x
S3
L 雷达
N/A
Computernav.svg电脑
2x
S2
M 计算机
N/A
Powerplantnav.svg发电机
2x
S3
L 发电机
N/A
Coolernav.svg冷却器
2x
S3
L 冷却器
N/A
Shieldgeneratornav.svg护盾生成器
3x
S3
L 护盾
N/A

Quantumdrivenav.svg量子驱动器
1x
S3
L 量子引擎
N/A
Jumpdrivenav.svg跳跃驱动器
1x
S3
L 跳跃模块
N/A
Fuelintakenav.svg加油口
2x
S3
L 燃料进气口
N/A
Fueltanknav.svg燃料箱
1x
S3
L 燃料箱
N/A
Quantumfueltanknav.svg量子燃料箱
2x
S3
L 量子燃料箱
N/A
文件:Mainthrusternav.svg推进器
2x
S3
主推进器
N/A
4x
S3
垂直推进器
N/A
2x
S3
反推进器
N/A
12x
S2
固定机动推进器
N/A

Turretnav.svgTurrets
1x
S7
Manned Turret Forward-Facing
N/A
2x
SX
Empty hardpoint
N/A
2x
S3
Side Turret
N/A
4x
SX
Empty hardpoint
N/A
1x
S3
Belly Turret (Missile Racks)
N/A
2x
SX
Empty hardpoint
N/A

功能

  • 完善的水雷控制室: 一个完整的控制室，用于对鹦鹉螺的载荷进行排序和部署。
  • 舒适的生活环境: 一间餐厅，船员居住区和舰长宿舍为长期的深空任务提供了舒适度的保障
  • 充沛的自卫火力: 配备了三个载人炮塔，每个炮塔上装有两门S3型号的火炮，以及前置的载人炮塔，装备有两门S7型号的火炮，以确保在最危险的布雷或排雷区域中保护鹦鹉螺的安全。[1]

可部署物

图片 类型 描述
Nautilus - Homing Mine - TransparentCropped.png
 制导水雷 火焰风暴动力学的 Tephra Homing Mine｜火山灰水雷会在敌对目标进入范围后向目标移动并引爆，其主要作用是建立外围防御。这种水雷的主要作用是建立外围防御。它具有与一枚5号鱼雷相当的破坏力。
Nautilus - Nemo Drone - TransparentCropped.png
 "尼莫"无人机 萨迦数据系统的尼莫无人机是一种专门设计用于识别、停用和收集已部署地雷的无人机。根据民兵动员计划的17c1修正案，所有装备有布雷功能的武装布雷船只必须配备并正常运行水雷回收装置。
Nautilus - Sentry Mine - TransparentCropped.png
 哨戒水雷 贝林财团的VLR-11 Sentry Mine｜VLR-11哨戒水雷是一种装备了武器的水雷，当敌对目标进入其射程范围时，它会对其进行攻击。其主要作用是建立外围防御，其可以搭载两门尺寸2的火炮。

历史

鹦鹉螺于2549年推出，当时UEE与新发现的希安帝国之间的紧张局势加剧。在此之前，太空水雷作为一种有效的防御形式逐渐崭露头角。特别是在第一次塔维因战争期间，作战工程师利用改装过的货船和部队运输舰部署了临时的近炸水雷。受此启发，该船最初的概念中设有宽敞的货舱，用于储存大量的爆炸物。然而，来自机组人员的反馈使得圣盾动力公司决定将制导的精确性置于负载之上。

在其首次亮相后，在人类与希安人的冲突中，该船在2550年至2793年之间于佩里防线进行了无数次成功的任务。尽管如此，鹦鹉螺的系统远未完善。圣盾动力在后续的几代中进行了改进以解决这个问题。其中一项改进是在2555年增加了一个传送带。该传送带用于将水雷放置到指定位置。之前这是通过一个推车系统完成的，速度过慢且笨重。然而，即使有了传送带，也存在问题，因为它们经常会卡住。在2601年，这个系统被一个高架轨道系统所替代。这个系统在盲点行动中由海军舰船UEES 和平号证明了其作用。该行动以对Tohil|托希尔系统的小行星带的大规模布雷而闻名，结果意外消除了暴力海盗团队大帽子。 后续的修改版本中增加了哨戒水雷*自行防空炮*，这是一种更可持续且破坏性较小的近炸鱼雷的替代品，并取得了成功。即使船上的设施也随着时间的推移而发展。最初的鹦鹉螺型号由于主要设计用于短期任务，所以其有效载荷能力较低。随着技术的进步和机组人员变得更有经验，他们减少了返回基地重新装备的需求。船内的住宿和设施很快扩展到让鹦鹉螺可以进行更长时间的巡航的程度。

在第二次塔维因战争期间,鹦鹉螺首次在公开战争中面临了实战考验。这艘船最初的设计目的是喝止传统战斗的发生，而不是参与其中。然而塔维因人的极端攻击手段迫使圣盾动力不得不对其近炸水雷进行调整和改进。水雷自导功能自此亮相，并证明其在战斗中的效用和持久性。尽管在沃斯卡战役中遭遇了一些挫败（比如地误伤友军的水雷），但这一时期为完善鹦鹉螺的形态和功能提供了前所未有的机会。

"随着战局的变化，我们必须适应以有效地应对不断变化的优先事项、战术和敌人的凶猛攻击，无论他们是谁。在努力调整设计以适应这些目标的同时，我们希望利用过去战役的综合知识来不断完善鹦鹉螺的系统和能力，最终目标是创建一艘多功能的“解决方案”，并能够轻松应对任何可想象的威胁或情况。"
Mila Aukerman｜米拉·奥克曼，首席开发工程师[1]

Battle of Centauri｜半人马之战一样给了鹦鹉螺一次证明自己的机会尽管这通常没有被提及。在这场著名战斗之前，一些有价值的情报被截获，详细描述了敌人的攻击计划，一个名为Blackhearts｜黑心的工兵中队利用这些情报在系统周围的关键跳跃点布置了近炸装置。他们有意在这个“迷宫”中留下一些微妙的路径，让UE的拦截部队将敌人引入水雷区。这一破坏行动导致敌军的大部分力量未能到达战场，最终帮助人类取得了胜利。

自从2945年起，在Vega|维加系统中与剜度氏族的战役从未休止过 鹦鹉螺在许多剜度氏族之战中发挥了关键作用，尽管许多工兵人员往来无闻。其中一个例子是被称为Hellkite Run的任务。它的目的是切断Vanduul在Oberon\奥伯龙系统中的逃生路线. 整个剜度中队试图离开该系统进行加油和补给时被消灭。直至今日，鹦鹉螺的船员们仍在继续维护该系统的防御工作。

当UEE于2946宣布民兵动员计划时，圣盾动力开始解密一部分鹦鹉螺的机密技术并向普通公众进行市场推广。由于涉及私人船只在之前受到战争影响的星系中遭受破坏和丧失的事件，民兵动员计划的一项修正规定，所有目前正在生产的具有布雷功能的船只必须配备解除和/或清除其载荷的手段。其中一个例子是天文学家凯瑟琳艾伦和她的船员在一次介绍Hadrian system｜哈德良系统的危险性的现场直播中被诡雷爆炸波及死亡, 修正案通过之后，战前危险的地点可以更容易地被“善后”。因此，最新的2949版鹦鹉螺配备了一台扫雷无人机作为其标准配置。 [1]

模型

特殊版本

冬至鹦鹉螺"

Nautilus - Solstice Skin - Transparent - Front Starboard.png
 限量版供应，仅供礼宾俱乐部购买，根据出厂顺序进行编号[2]

购买价格历史

Date 购买价格 (USD) 保险 可用性 出售时间
2020-05-26 725 120月 限时 Invictus 2950 [3]

画廊

WikimediaUI-ArticleDisambiguation-ltr.svg
对于a full gallery，请参阅Category:Nautilus images。
Nautilus - In formation attacking in battle - Port.jpg
Nautilus - Deploying mines - Rear Port.jpg
Nautilus - x7 Laying mines over world - Front.jpg
Nautilus - Schematic - Starboard.jpg
Nautilus - Schematic - Deck Plan.jpg
Nautilus - with drone - Front Below.jpg
Nautilus - x3 Landed with 1 taking off.jpg
Nautilus - On assembly line - Front.jpg
Nautilus - Schematic - Top Deck.png
Nautilus - Bridge area - Above.jpg
Nautilus - Transparent Back - Front Starboard.png
Nautilus - Schematic - Main Deck.png
Nautilus - Bridge.png
Nautilus - Schematic - Sweep Deck.png
Nautilus - Engineering.jpg
Nautilus - Senrty Mines attacking Blades.jpg
Tephra Homing Mine - Diagram.jpg
Nautilus - Homing Mine - Transparent.png
Valor Sentry Mine - Diagram.jpg
Nautilus - Sentry Mine - Transparent.png
Nemo Drone - Diagram.jpg
Nautilus - Nemo Drone - Transparent.png
Kraken - x2 Flying through mine field.jpg
Nautilus - Deploying mines - Front Starboard.png

IAE2950-day2-holosuite-nautilus.jpg
Invictus-2950-hologram-nautilus-01.jpg
Invictus-2950-hologram-nautilus-02.jpg
Invictus-2950-hologram-nautilus-03.jpg
Invictus-2950-hologram-nautilus-04.jpg
Invictus-2950-hologram-nautilus-05.jpg

引用

  1. ↑ 1.0 1.1 1.2 1.3 RSIsite.svgAegis Nautilus Comm-link. 通讯链接
  2. ↑ RSIsite.svgNautilus Solstice Edition - pledge store. Pledge Store. Retrieved 2020-03-28
  3. ↑ RSIsite.svgInvictus 2950 Sale. 通讯链接
取自“https://citizenwiki.cn/index.php?title=鹦鹉螺&oldid=56563”
Debug data: