Участник:Triogenix/Sandbox 4 - История изменений

>Triogenix: /* Ships and Sizes */

2024-04-18T19:50:29Z

Ships and Sizes

← Предыдущая версия		Версия от 22:50, 18 апреля 2024
Строка 20:		Строка 20:
	The interstellar society that is the Orion spur - blah blah blah blah.		The interstellar society that is the Orion spur - blah blah blah blah.

	These are the corporate ~~shit~~ classes		These are the corporate ship classes

	Insert list here		Insert list here

>Triogenix: Replaced content with "=Ships and Stations= Spaceships in the 25th century are a common sight. Different star nations and alien powers use different models, designations, and hull types that makes specifics impossible. There are giant barges, small freighters, huge carriers and battleships, heavily armored cruisers, and more. The primary distinction between all ships is whether or not they are equipped with Bluespace Drives that allow them to use FTL outside the network of Bluespace Gates...."

2024-04-18T19:50:05Z

Replaced content with "=Ships and Stations= Spaceships in the 25th century are a common sight. Different star nations and alien powers use different models, designations, and hull types that makes specifics impossible. There are giant barges, small freighters, huge carriers and battleships, heavily armored cruisers, and more. The primary distinction between all ships is whether or not they are equipped with Bluespace Drives that allow them to use FTL outside the network of Bluespace Gates...."

Внесённые изменения

>Triogenix: /* Warp Gates */

2024-03-31T06:14:36Z

Warp Gates

← Предыдущая версия		Версия от 09:14, 31 марта 2024
Строка 77:		Строка 77:

	== Warp Gates ==		== Warp Gates ==
	Where bluespace gates form the highways of travel in the spur, warp gates are considered local roads. They are reliably found in every known inhabited system, and in conjunction with warp lanes, form a spider web of connection across the known galaxy. Significantly smaller and cheaper to run than bluespace gates, they’re seen as the mainstay of interstellar travel, even during the dominance of bluespace. A drive is not required to use a warp gate, and they are significantly shorter range than bluespace ones. However, a specific security key for their destination is needed for a vessel to travel between warp gates. These security keys are long strings of barely decipherable code, which “unlock” use of a gate on a ship by ship basis. Each warp-gate will house a AI who, in addition to processing the simplified navigational data on a warp route to ensure a zero-risk jump, has all the codes for other gates within range on hand, and will transmit them on a ship-to-ship basis, ensuring the right ship receives the right code. These AI, or some form of them, are used even by those in the spur who reject artificial intelligence. However, compared to the fully sentient, aware, and exponentially more powerful AI installed in bluespace gates; warp gate AI can be incredibly simple, allowing nations such as the Empire of Dominia to still utilize their warp gates with non-sentient AI. Nearly all organics cannot hope to achieve the raw computing power necessary to process even the simplified navigational data needed to ensure safe warping, however, there is a notable exception in the Nralakk Federation, who have created an organic alternative to use on warp gates, which can be read about [[here.]]		Where bluespace gates form the highways of travel in the spur, warp gates are considered local roads. They are reliably found in every known inhabited system, and in conjunction with warp lanes, form a spider web of connection across the known galaxy. Significantly smaller and cheaper to run than bluespace gates, they’re seen as the mainstay of interstellar travel, even during the dominance of bluespace. A drive is not required to use a warp gate, and they are significantly shorter range than bluespace ones. However, a specific security key for their destination is needed for a vessel to travel between warp gates. These security keys are long strings of barely decipherable code, which “unlock” use of a gate on a ship by ship basis. Each warp-gate will house a AI who, in addition to processing the simplified navigational data on a warp route to ensure a zero-risk jump, has all the codes for other gates within range on hand, and will transmit them on a ship-to-ship basis, ensuring the right ship receives the right code. These AI, or some form of them, are used even by those in the spur who reject artificial intelligence. However, compared to the fully sentient, aware, and exponentially more powerful AI installed in bluespace gates; warp gate AI can be incredibly simple, allowing nations such as the Empire of Dominia to still utilize their warp gates with non-sentient AI. Nearly all organics cannot hope to achieve the raw computing power necessary to process even the simplified navigational data needed to ensure safe warping, however, there is a notable exception in the Nralakk Federation, who have created an organic alternative to use on warp gates, which can be read about [[Nralakk_Federation#Computing \| here.]]

	Similarly to bluespace gates, warp gates are unaffected by the gravity well of a system, and are therefore normally placed in orbit of specific planets; such as the famous network above the port planet of Callisto.		Similarly to bluespace gates, warp gates are unaffected by the gravity well of a system, and are therefore normally placed in orbit of specific planets; such as the famous network above the port planet of Callisto.

>Triogenix: /* Bluespace Travel */

2024-03-28T08:03:17Z

Bluespace Travel

← Предыдущая версия		Версия от 11:03, 28 марта 2024
Строка 9:		Строка 9:
	Bluespace travel describes a process that uses phoron-powered engines to bore tunnels into the “bluespace dimension” so named for its characteristic blue hue. The vessel then uses onboard propulsion to enter the tunnel and begin travel. It was first discovered in 2341 by '''Luo Qiqiang''', a physicist employed with Einstein Engines. Qiqiang theorised that bluespace would revolutionise FTL travel, though he could not grasp its full implications, thinking it was just a more efficient version of the warp, rather than the separate dimension it is known to be today.		Bluespace travel describes a process that uses phoron-powered engines to bore tunnels into the “bluespace dimension” so named for its characteristic blue hue. The vessel then uses onboard propulsion to enter the tunnel and begin travel. It was first discovered in 2341 by '''Luo Qiqiang''', a physicist employed with Einstein Engines. Qiqiang theorised that bluespace would revolutionise FTL travel, though he could not grasp its full implications, thinking it was just a more efficient version of the warp, rather than the separate dimension it is known to be today.

	It was not until NanoTrasen’s discovery of phoron, and the further work of '''Samantha Tigard''', that bluespace was able to be better researched, understood, and applied. The high energy capacity of phoron allowed bluespace gates and drives to be easily used. As b propulsion ~~was~~ being developed, bluespace drives saw quick adoption, and plans were put in place to partially replace the prior generation of warp gates, with some scientists confidently declaring warp travel obsolete. However, even before the scarcity, maintaining bluespace drives and gates was an expensive endeavor, one which never saw a significant price drop; causing plans to phase out the warp gates in favor of bluespace ones to be canceled, and revised into the more modern system we know today.		It was not until NanoTrasen’s discovery of phoron, and the further work of '''Samantha Tigard''', that bluespace was able to be better researched, understood, and applied. The high energy capacity of phoron allowed bluespace gates and drives to be easily used. As early methods of propulsion were being developed, bluespace drives saw quick adoption, and plans were put in place to partially replace the prior generation of warp gates, with some scientists confidently declaring warp travel obsolete. However, even before the scarcity, maintaining bluespace drives and gates was an expensive endeavor, one which never saw a significant price drop; causing plans to phase out the warp gates in favor of bluespace ones to be canceled, and revised into the more modern system we know today.

	In the 2460s, circumstances have changed. The phoron scarcity brings doubt as to whether bluespace travel will remain a viable option in the future, andNanoTrasen and the Stellar Corporate Conglomerate have put great effort into alleviating the scarcity. After the SCCV Horizon discovered the “Orchard Moon” asteroid in the galactic region of Valley Hale, some of the drain on resources has been lessened, but only time will tell if bluespace travel is passing into the annals of history.		In the 2460s, circumstances have changed. The phoron scarcity brings doubt as to whether bluespace travel will remain a viable option in the future, andNanoTrasen and the Stellar Corporate Conglomerate have put great effort into alleviating the scarcity. After the SCCV Horizon discovered the “Orchard Moon” asteroid in the galactic region of Valley Hale, some of the drain on resources has been lessened, but only time will tell if bluespace travel is passing into the annals of history.

>Triogenix: /* Bluespace Travel */

2024-03-28T07:23:29Z

Bluespace Travel

← Предыдущая версия		Версия от 10:23, 28 марта 2024
Строка 5:		Строка 5:
	These divisions are split further by how faster-than-light travel is achieved, either using bluespace, or warp. Since 2462, and the beginning of the phoron scarcity, traveling via bluespace has become more expensive, and prices will continue to rise if the new phoron deposits of Orchard Moon cannot satisfy the market.		These divisions are split further by how faster-than-light travel is achieved, either using bluespace, or warp. Since 2462, and the beginning of the phoron scarcity, traveling via bluespace has become more expensive, and prices will continue to rise if the new phoron deposits of Orchard Moon cannot satisfy the market.

	=[[Bluespace]] Travel=		=Bluespace Travel=

	Bluespace travel describes a process that uses phoron-powered engines to bore tunnels into the “bluespace dimension” so named for its characteristic blue hue. The vessel then uses onboard propulsion to enter the tunnel and begin travel. It was first discovered in 2341 by '''Luo Qiqiang''', a physicist employed with Einstein Engines. Qiqiang theorised that bluespace would revolutionise FTL travel, though he could not grasp its full implications, thinking it was just a more efficient version of the warp, rather than the separate dimension it is known to be today.		Bluespace travel describes a process that uses phoron-powered engines to bore tunnels into the “bluespace dimension” so named for its characteristic blue hue. The vessel then uses onboard propulsion to enter the tunnel and begin travel. It was first discovered in 2341 by '''Luo Qiqiang''', a physicist employed with Einstein Engines. Qiqiang theorised that bluespace would revolutionise FTL travel, though he could not grasp its full implications, thinking it was just a more efficient version of the warp, rather than the separate dimension it is known to be today.

>Triogenix в 07:23, 28 марта 2024

2024-03-28T07:23:16Z

Внесённые изменения

>Triogenix: Replaced content with "== Major Ports and Shore Leave == Periodically the Horizon will be required to dock with the nearest major port to resupply its dwindled stores, during which the crew will be allowed a spell of shore leave. Alternating between a period of several days, the crew is allowed to disembark the Horizon for a few hours between these dockings - sometimes even days before reboarding before the Horizon leaves the next time it docks for a resupply. These major ports will be re..."

2024-02-29T01:40:21Z

Replaced content with "== Major Ports and Shore Leave == Periodically the Horizon will be required to dock with the nearest major port to resupply its dwindled stores, during which the crew will be allowed a spell of shore leave. Alternating between a period of several days, the crew is allowed to disembark the Horizon for a few hours between these dockings - sometimes even days before reboarding before the Horizon leaves the next time it docks for a resupply. These major ports will be re..."

@@ Строка 1: / Строка 1: @@
-== EVENT RULES AND REGULATIONS ==
+== Major Ports and Shore Leave ==
-=== MINI-EVENTS AND ARCS ===
+Periodically the Horizon will be required to dock with the nearest major port to resupply its dwindled stores, during which the crew will be allowed a spell of shore leave. Alternating between a period of several days, the crew is allowed to disembark the Horizon for a few hours between these dockings - sometimes even days before reboarding before the Horizon leaves the next time it docks for a resupply. These major ports will be relative to the region in which the Horizon currently is traveling.
-'''Mini Events can be defined as the following:'''
+The Horizon has scheduled resupplies every week until it leaves the system for another port of call, on the day(s): Sunday and Thursday.
-This differs from actual events and their arcs, which are much wider in scope in both lore impact and development time.
+'''The major port(s) are currently:''' [[Konyang]], specifically above the city of Point Verdant/Aoyama. Due to the ongoing emergency, transportation for shore leave is restricted to Aoyama's corporate district.

>Triogenix: /* EVENT RULES AND REGULATIONS */

2023-10-24T14:27:55Z

EVENT RULES AND REGULATIONS

← Предыдущая версия		Версия от 17:27, 24 октября 2023
Строка 52:		Строка 52:
	** In addition, the development process should be coordinated by a member of either the dev or species team running the arc, who acts as a manager for the technical side, ensuring that work is completed in a quick and organized fashion.		** In addition, the development process should be coordinated by a member of either the dev or species team running the arc, who acts as a manager for the technical side, ensuring that work is completed in a quick and organized fashion.
	** By the time everything has been entered into the appropriate fields, [https://forums.aurorastation.org/topic/16780-nbt-plotline-proposals/?do=findComment&comment=169697 the document should look something like this.]		** By the time everything has been entered into the appropriate fields, [https://forums.aurorastation.org/topic/16780-nbt-plotline-proposals/?do=findComment&comment=169697 the document should look something like this.]
	* Staff Complaints regarding event arcs, such as complaints regarding canon deaths, are to be handled by the ~~LTA. If the LTA is the target of complaints, they are to be handled by a head administrator or head developer~~.		* Staff Complaints regarding event arcs, such as complaints regarding canon deaths, are to be handled as per the respective rules.

>Triogenix: /* EVENT RULES AND REGULATIONS */

2023-10-14T02:43:56Z

EVENT RULES AND REGULATIONS

← Предыдущая версия		Версия от 05:43, 14 октября 2023
Строка 51:		Строка 51:
	** Technical Requirements such as sprites, code, maps, and other similar things should be compiled into a technical document, with the arcs name, and if approved, then forwarded to the Dev Team in a newly created channel for managing the technical side of the arc, who will work on it as part of their contribution to the staff team. Whenever possible reference images should be provided, and outlines of event maps made for the dev team.		** Technical Requirements such as sprites, code, maps, and other similar things should be compiled into a technical document, with the arcs name, and if approved, then forwarded to the Dev Team in a newly created channel for managing the technical side of the arc, who will work on it as part of their contribution to the staff team. Whenever possible reference images should be provided, and outlines of event maps made for the dev team.
	** In addition, the development process should be coordinated by a member of either the dev or species team running the arc, who acts as a manager for the technical side, ensuring that work is completed in a quick and organized fashion.		** In addition, the development process should be coordinated by a member of either the dev or species team running the arc, who acts as a manager for the technical side, ensuring that work is completed in a quick and organized fashion.
	** By the time everything has been entered into the appropriate fields, ~~the document should look something like~~ [https://forums.aurorastation.org/topic/16780-nbt-plotline-proposals/?do=findComment&comment=169697 this.]		** By the time everything has been entered into the appropriate fields, [https://forums.aurorastation.org/topic/16780-nbt-plotline-proposals/?do=findComment&comment=169697 the document should look something like this.]
	* Staff Complaints regarding event arcs, such as complaints regarding canon deaths, are to be handled by the LTA. If the LTA is the target of complaints, they are to be handled by a head administrator or head developer.		* Staff Complaints regarding event arcs, such as complaints regarding canon deaths, are to be handled by the LTA. If the LTA is the target of complaints, they are to be handled by a head administrator or head developer.

>Triogenix в 02:16, 14 октября 2023

2023-10-14T02:16:35Z

← Предыдущая версия		Версия от 05:16, 14 октября 2023
Строка 37:		Строка 37:

	==== EVENT RULES AND REGULATIONS ====		==== EVENT RULES AND REGULATIONS ====
	* Major Events and their arcs must be properly documented both on the forums before/during them, and then properly documented on the wiki afterward. This documentation should follow not only Arrow’s ~~Outline(hyperlink again)~~ for the scheduling of events themselves but also the Arc Outline Template that can be found here~~(hyperlink to wiki)~~.		* Major Events and their arcs must be properly documented both on the forums before/during them, and then properly documented on the wiki afterward. This documentation should follow not only [https://forums.aurorastation.org/topic/11560-how-to-events/#comment-110842 Arrow’s Guidelines] for the scheduling of events themselves but also [[Libération, Révolution et Évolution Arc \| the Arc Outline Template that can be found here]].
	* Arcs should also be announced with a general time of occurrence to the server as a whole two months before their scheduled time, to alert players of what might be coming next. Whenever possible, this should be kept OOC only.		* Arcs should also be announced with a general time of occurrence to the server as a whole two months before their scheduled time, to alert players of what might be coming next. Whenever possible, this should be kept OOC only.
	** An important part of this is ensuring that you will in fact be ready in two months. Announcing months ahead of time, only to be delayed constantly, will merely leave the player base waiting on their hands for the arc to begin, not as engaged as they might be.		** An important part of this is ensuring that you will in fact be ready in two months. Announcing months ahead of time, only to be delayed constantly, will merely leave the player base waiting on their hands for the arc to begin, not as engaged as they might be.