Q&A: Crusader Mercury
September 12th 2018
Q&A: Crusader Mercury
Following the launch of the Mercury Star Runner from Crusader Industries, we took your top voted questions to our designers in an effort to get you more information about this recently revealed data runner.
If you haven’t watched the recent Ship Shape on the Mercury, you can do so here. We also sat down with the developers behind the ship in a special Townhall Q&A, LIVE from Gamescom which you can watch here.
Special thanks to John Crewe and Todd Papy for taking the time to answer questions.
Dedicated scanning ships, or ships equipped with dedicated scanners are built around that gameplay, which is not what the Mercury is built for. The Mercury’s scanners are only good enough to intercept local communications, rather than scanning of unknown areas or picking up low signatures at distance like the Terrapin can. The Terrapin, when crewed effectively, will always surpass the Mercury in terms of scanning efficiency. Think of the Mercury as a hybrid cargo ship, between freight and data.
As always, all stats are subject to change and if we find out during production the Mercury isn’t fast enough to fulfil its role we’ll adjust as necessary. Generally as ships get larger they get slower in the current design, so as the Mercury sits in between the Freelancer and Cutlass, it currently sits in between their speed ranges, although there are a whole host of parameters aside from top speed we use but don’t show to adjust their handling characteristics.
Having a dedicated e-war suite was not part of the original design for the ship and at this time is not being considered for addition, instead leaving the functionality on other ships such as the Herald and Sentinel. However, a dedicated e-war suite is not a requirement for data hacking.
Keep an eye on the roadmap for more information on when this ship will enter production. The design work done on the Star Runner and Starlifter will both be used as reference for the larger ships, such as the Starliner.
Jump point sizing and categorisation is still being worked out, but we expect the Mercury to fit through the same size jump points as the Freelancer.
The back ramp is the only entrance to the ship, and it has no docking collar or secondary lift entrances.
This was an intentional choice to make players choose between the roles. There is actually 5 distinct stations on the ship (Pilot, CoPilot, Scanning, 2x Turret) and we want players to react and choose what they want to do in various scenarios. Increasing the crew capacity means significant other knock-ons to ship design in terms of size and features, and we want to keep this ship relatively compact and focused.
There are no plans to have any additional variants or modules at this time. The original brief was for a ship to do these two specific roles (cargo and data running) rather than be modular and changed into different roles.
An example of legal data collection in PvE would be a mission along the lines of scanning a certain location for information, such as asteroid composition/density. Alternatively, you may recieve a mission to find specific player owned ships & their locations, which will need to be reported back the mission giver. Illegal data collection would be something more along the lines of intercepting sensitive information between two ships for PvE or intercepting and beating another player to delivery on an existing data running mission.
The bathroom, kitchen, dining table and gun racks are shared between all crew members. Each crew member also has their own suit storage locker near their bunk.
There is no secondary entrance/exit, so the cargo room must be decompressed to enter or exit the ship in space. There is an airlock to the rest of the ship, and the turrets are sealed off to prevent further decompression.
SettingsOne column Two columns Oldest first Newest first Most appreciated first