| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
| cw4:cmod:docs:6bff7473-183e-4731-b28a-c4905d87fb9f [2022/05/02 21:28] – Forum page redirection. Vertu | cw4:cmod:docs:6bff7473-183e-4731-b28a-c4905d87fb9f [2022/08/30 01:34] – [-Role-] More clear categorizing and better visual spacing Vertu |
|---|
| <=[[cw4:info:start#custom_units| Index]] | <=[[cw4:info:start#custom_units| Index]]\\ |
| | <=[[cw4:cpack:docs:7f65b557-95b9-47d0-807a-5d05b1b426db| VAU CPACK]]\\ |
| ====== [VAU CPack] Fighter (VGPSF) ====== | ====== [VAU CPack] Fighter (VGPSF) ====== |
| :WARNING: This page is currently being worked on. | |
| :TODO: Metal note: Implement all cross references including in V-Power pages. | |
| |
| |
| | {{:cw4:cmod:docs:vgpsf.jpg?nolink&400 |}}\\ |
| The Vertu General Purpose Space Fighter is a take on the concept originally made an example by evolutionary emergence of "specialized to be general purposed". It is so general purposed, no alterations where necessary to enable the VGPSF to be effective against Creeper by no more than charging it's Photon Cannons rather than their default mode. The VGPSF is a shinning icon of the Vertu Empire, being tough enough to rival the endurance of entire battleships of primitive races. The only brand of weapon that can damage Vertu Fighters are those created by Vertu, or exceedingly upscaled primitive weapons that //somehow// landed a hit because by the fundamentals of kinetics, a big enough bullet will go through even the Neutronium((What is Neutronium? <fc #ff0000><fs large>SCIENCE LESSION TIME!</fs></fc> :WARNING: <color #ffaaaa>You have been warned.</color> | The Vertu General Purpose Space Fighter is a take on the concept originally made an example by evolutionary emergence of "specialized to be general purposed". It is so general purposed, no alterations where necessary to enable the VGPSF to be effective against Creeper by no more than charging it's Photon Cannons rather than their default mode. The VGPSF is a shinning icon of the Vertu Empire, being tough enough to rival the endurance of entire battleships of primitive races. The only brand of weapon that can damage Vertu Fighters are those created by Vertu, or exceedingly upscaled primitive weapons that //somehow// landed a hit because by the fundamentals of kinetics, a big enough bullet will go through even the Neutronium((What is Neutronium? <fc #ff0000><fs large>SCIENCE LESSION TIME!</fs></fc> :WARNING: <color #ffaaaa>You have been warned.</color> |
| |
| * Is the main VAU. | * Is the main VAU. |
| * 75 HP. | * 75 HP. |
| * Will leave once <color #FFAA33>Mission Completed</color>((When all required objectives are fulfilled and you can Rift Jump to complete the mission.)) status is achieved. If Fighters are re-summoned after this status is achieved, they will stay to the end unless they encounter a valid retreat condition such as being too low on health. | * Will leave once <color #FFAA66>Mission Completed</color>((When all required objectives are fulfilled and you can Rift Jump to complete the mission.)) status is achieved. If Fighters are re-summoned after this status is achieved, they will stay to the end unless they encounter a valid retreat condition such as being too low on health. |
| |
| ---- | ---- |
| ===== -Role- ===== | ===== -Role- ===== |
| The Vertu Fighter within CW4 has a very simple but general role of providing air-ground firepower by vaporizing targeted Creeper. They have far superior range and efficiency compared to most combat towers but require a high impulse recharge that can be harmful to the Rift Lab's energy production abilities and cause sudden and extreme deficit while also being limited in number.\\ | The Vertu Fighter within CW4 has a very simple but general role of providing air-ground firepower by vaporizing targeted Creeper. They have far superior range and efficiency compared to most combat towers but require a high impulse recharge that can be harmful to the Rift Lab's energy production abilities and cause sudden and extreme deficit while also being limited in number.\\ |
| | \\ |
| The biggest advantage of all VAUs is how they obviously can fly over Creeper and target as they please. The Fighter works very well as a fast response unit and moderate-heavy fire support, further complimented by using energy as ammo as opposed to limited resources while still being easily accessible via the [[cw4:cmod:docs:fe4a67bc-f8b6-44b8-a0a9-54e89855edfb | Summoner]].\\ | The biggest advantage of all VAUs is how they obviously can fly over Creeper and target as they please. The Fighter works very well as a fast response unit and moderate-heavy fire support, further complimented by using energy as ammo as opposed to limited resources while still being easily accessible via the [[cw4:cmod:docs:fe4a67bc-f8b6-44b8-a0a9-54e89855edfb | Summoner]].\\ |
| | \\ |
| With their high speed, firepower, and efficiency, there is virtually no reason not to summon a few Vertu Fighters before investing into more expensive Liftic transactions in the [[cw4:cmod:docs:fe4a67bc-f8b6-44b8-a0a9-54e89855edfb | Summoner]], they are just that handy. It is also a practiced tactic by Vertu incursions to create two [[cw4:cmod:docs:fe4a67bc-f8b6-44b8-a0a9-54e89855edfb | Summoners]]. One is dedicated to summoning Fighters and only Fighters while the other is dedicated to summon every other VAU as seen fit at any point in time but only if there is enough available Liftic to sustain two [[cw4:cmod:docs:fe4a67bc-f8b6-44b8-a0a9-54e89855edfb | Summoners]].\\ | With their high speed, firepower, and efficiency, there is virtually no reason not to summon a few Vertu Fighters before investing into more expensive Liftic transactions in the [[cw4:cmod:docs:fe4a67bc-f8b6-44b8-a0a9-54e89855edfb | Summoner]], they are just that handy. It is also a practiced tactic by Vertu incursions to create two [[cw4:cmod:docs:fe4a67bc-f8b6-44b8-a0a9-54e89855edfb | Summoners]]. One is dedicated to summoning Fighters and only Fighters while the other is dedicated to summon every other VAU as seen fit at any point in time but only if there is enough available Liftic to sustain two [[cw4:cmod:docs:fe4a67bc-f8b6-44b8-a0a9-54e89855edfb | Summoners]].\\ |
| | ====Role (lore version):==== |
| In core design, the Vertu Fighter is.. well.. //a fighter.// So in the event (//somehow//) the Creeper evolves into a more militaristic methodology, the Fighters will be actual Fighters. This however is infidecimally impossible due to how the Vertu Empire is an anomaly in terms of technological age. Having overcome the great filter of technological stagnation and having no opposition to their ability to innovate and advance, and much like in Human Earth technology, with advancements in technology; more and better tools to conduct scientific study and discovery become available to enable breakthroughs in the categories of science to be achieved both more frequently and easily with the original limit being the great filter of technological stagnation from hyper advanced technology. Since Vertu has overcome this great filter, there was and is no stopping their innovation so it is infidecimally impossible for the Creeper to develop any kind of military presence to warrant the Fighters to act like the Fighters they are in their core when Vertu is so far ahead.((<color #aaffaa>LORE:</color> However, Vertu does express a part-time interest/curiosity to who created the Creeper. Also known as the Gray Goo by Vertu but as a blue liquid and biological edition. Many Vertu Fighters actually commit to service against the Creeper out of their own curiosity of this question and their curiosity to the Creeper in general. Sadly they are too few in number to make summoning Fighters even cheaper than 350 Liftic. This all still uses energy at the end of the day and the demand for Fighter services is so large, it is meaningless to not call it infinite.))\\ | In core design, the Vertu Fighter is.. well.. //a fighter.// So in the event (//somehow//) the Creeper evolves into a more militaristic methodology, the Fighters will be actual Fighters. This however is infidecimally impossible due to how the Vertu Empire is an anomaly in terms of technological age. Having overcome the great filter of technological stagnation and having no opposition to their ability to innovate and advance, and much like in Human Earth technology, with advancements in technology; more and better tools to conduct scientific study and discovery become available to enable breakthroughs in the categories of science to be achieved both more frequently and easily with the original limit being the great filter of technological stagnation from hyper advanced technology. Since Vertu has overcome this great filter, there was and is no stopping their innovation so it is infidecimally impossible for the Creeper to develop any kind of military presence to warrant the Fighters to act like the Fighters they are in their core when Vertu is so far ahead.((<color #aaffaa>LORE:</color> However, Vertu does express a part-time interest/curiosity to who created the Creeper. Also known as the Gray Goo by Vertu but as a blue liquid and biological edition. Many Vertu Fighters actually commit to service against the Creeper out of their own curiosity of this question and their curiosity to the Creeper in general. Sadly they are too few in number to make summoning Fighters even cheaper than 350 Liftic. This all still uses energy at the end of the day and the demand for Fighter services is so large, it is meaningless to not call it infinite.))\\ |
| <hidden More details to the above are provided here.>Obviously there are exceptions, but said "exceptions" are infidecimally entirely involved with only the Fighter's individuality, typically being; a Fighter will get board with it's low fire rate and the Creeper not actively engaging it, and swap firing modes into their original and preferred dog-fighting weapon mode. Usually the individual quickly learns how the ineffectiveness of this firing mode is more boring and sticks with the advised weapon mode. After some few missions in service, that individual fighter won't swap firing modes again. The true exception however; is that given the opportunity to not need to charge it's weapons to vaporize Creeper, some of these types of individuals that fit the description stated previously will take said opportunity without question and in the simulated event this happens, the other Fighters on the same mission will quickly join in. This is the only known possible situation where Fighters on a CW4 mission will behave like the Fighters they are at heart. It is Vertu policy to cycle Fighters out of service in CW missions and into more militaristic missions to help with their mentality from this foreign Fighter-behavior on CW missions and eventually be cycled back into service in CW missions after exercising their "natural" Fighter behavior(s) for long enough and with enough potency.</hidden>\\ | <hidden More details to the above lore are provided here.>Obviously there are exceptions, but said "exceptions" are infidecimally entirely involved with only the Fighter's individuality, typically being; a Fighter will get board with it's low fire rate and the Creeper not actively engaging it, and swap firing modes into their original and preferred dog-fighting weapon mode. Usually the individual quickly learns how the ineffectiveness of this firing mode is more boring and sticks with the advised weapon mode. After some few missions in service, that individual fighter won't swap firing modes again. The true exception however; is that given the opportunity to not need to charge it's weapons to vaporize Creeper, some of these types of individuals that fit the description stated previously will take said opportunity without question and in the simulated event this happens, the other Fighters on the same mission will quickly join in. This is the only known possible situation where Fighters on a CW4 mission will behave like the Fighters they are at heart. It is Vertu policy to cycle Fighters out of service in CW missions and into more militaristic missions to help with their mentality from this foreign Fighter-behavior on CW missions and eventually be cycled back into service in CW missions after exercising their "natural" Fighter behavior(s) for long enough and with enough potency.</hidden>\\ |
| |
| ===== -AI (Artificial Intelligence)- ===== | ===== -AI (Artificial Intelligence)- ===== |
| All VAUs except the Battlestation and Auto Station have proper AI with two separate parts which combine into said proper AI. | All VAUs except the [[cw4:cmod:docs:ac504307-18ee-4c6d-9a07-e7a070166594|V-Battlestation]] and [[cw4:cmod:docs:ae4805e8-0856-42d5-b374-2e7bceb4ec1c|Auto Station]] have proper AI with two separate parts which combine into said proper AI. |
| * The first AI is AutoRestock AI which is responsible for controlling the VAU when critically low on ammo and needs to go restock. It will even override the main AI by having priority. It is a very simple set of logic that tells the VAU to and how to go either to the Rift Lab or [[cw4:cmod:docs:09f51970-ce18-45a7-9e07-e4d33a0e7ade | RESTOCKv]] beacon if it's available and active. It will also react to the Desired Ammo widget that specifies how much ammo the VAU should wait to obtain when restocking. When the VAU's ammo reaches at or above the Desired Ammo, the AutoRestock AI will release it's control. If the Desired Ammo is at "~MAX", when the VAU obtains 5 ammo less than it's max ammo, a timer will count down based on the VAU's Charge Speed widget to simulate the next 5 packets on their way and how long it would take to receive all 5 remaining packets. Once the timer expires or full ammo is achieved at any moment, AutoRestock AI finishes and relinquishes it's control. This means that if the VAU is firing and using ammo while restocking, it won't be stuck restocking by waiting for newly sent ammo packets sent every time it fires before that original packet arrives and a new one needs to be sent to give it full ammo. | * The first AI is AutoRestock AI which is responsible for controlling the VAU when critically low on ammo and needs to go restock. It will even override the main AI by having priority. It is a very simple set of logic that tells the VAU to and how to go either to the Rift Lab or [[cw4:cmod:docs:09f51970-ce18-45a7-9e07-e4d33a0e7ade | RESTOCKv]] beacon if it's available and active. It will also react to the Desired Ammo widget that specifies how much ammo the VAU should wait to obtain when restocking. When the VAU's ammo reaches at or above the Desired Ammo, the AutoRestock AI will release it's control. If the Desired Ammo is at "~MAX", when the VAU obtains 5 ammo less than it's max ammo, a timer will count down based on the VAU's Charge Speed widget to simulate the next 5 packets on their way and how long it would take to receive all 5 remaining packets. Once the timer expires or full ammo is achieved at any moment, AutoRestock AI finishes and relinquishes it's control. This means that if the VAU is firing and using ammo while restocking, it won't be stuck restocking by waiting for newly sent ammo packets sent every time it fires before that original packet arrives and a new one needs to be sent to give it full ammo. |
| * The second AI is the "Full AI" which is more advanced sequences of logic that can actually be confidently called a form of AI rather than a logic sequence. This AI can do some forms of problem solving in the CW4 mission. This includes the reaction of being low on health and retreating to the Rift Lab, fully retreating (as in leaving the mission) when out of ammo and no ammo can be found within enough time, searching for targets, avoiding Creeper, entering formations (currently specifically for Fighters only), and eventually: prioritization logic and reaction to special buildings being under threat by Creeper and attempting to defend them (currently not yet implemented). | * The second AI is the "Full AI" which is more advanced sequences of logic that can actually be confidently called a form of AI rather than a logic sequence. This AI can do some forms of problem solving in the CW4 mission. This includes the reaction of being low on health and retreating to the Rift Lab, fully retreating (as in leaving the mission) when out of ammo and no ammo can be found within enough time, searching for targets, avoiding Creeper, entering formations (currently specifically for Fighters only), and eventually: prioritization logic and reaction to special buildings being under threat by Creeper and attempting to defend them (currently not yet implemented). |
| |
| ==== -Auto Restock AI- ==== | ==== -Auto Restock AI- ==== |
| Only the Battlestation and Auto Station don't have this kind of AI. The MBF also has some noticed potential issues with this AI so don't expect it to work too well on the MBF. It is an underdeveloped part of the MBF (due to lack of need to do something about it). | Only the [[cw4:cmod:docs:ac504307-18ee-4c6d-9a07-e7a070166594|V-Battlestation]] and [[cw4:cmod:docs:ae4805e8-0856-42d5-b374-2e7bceb4ec1c|Auto Station]] don't have this kind of AI. The [[cw4:cmod:docs:09dce69b-c3e4-4651-96fb-9186bf1a040c|MBF]] also has some noticed potential issues with this AI so don't expect it to work too well on the [[cw4:cmod:docs:09dce69b-c3e4-4651-96fb-9186bf1a040c|MBF]]. It is an underdeveloped part of the [[cw4:cmod:docs:09dce69b-c3e4-4651-96fb-9186bf1a040c|MBF]] (due to lack of need to do something about it). |
| |
| Whenever the VAU runs out of ammo, it will retreat to the Rift Lab to restock ammo. However, if a [[cw4:cmod:docs:09f51970-ce18-45a7-9e07-e4d33a0e7ade | RESTOCKv]] beacon is present and is online, it will go to it instead.\\ | Whenever the VAU runs out of ammo, it will retreat to the Rift Lab to restock ammo. However, if a [[cw4:cmod:docs:09f51970-ce18-45a7-9e07-e4d33a0e7ade | RESTOCKv]] beacon is present and is online, it will go to it instead.\\ |
| If a VAU goes to a location to restock and that location has a form of connection at or above 15 terrain height, no matter where the VAU decides to station in proximity to the location, it **will** be in connection range. This is a proven fact for Pylons and the Rift Lab. So be at ease with this certainty. | If a VAU goes to a location to restock and that location has a form of connection at or above 15 terrain height, no matter where the VAU decides to station in proximity to the location, it **will** be in connection range. This is a proven fact for Pylons and the Rift Lab. So be at ease with this certainty. |
| ==== -FULL AI Mode- ==== | ==== -FULL AI Mode- ==== |
| Only the Battlestation and Auto Station don't have this kind of AI. While a VAU has this AI enabled, it has full control over itself and will do it's own thing.\\ | Only the [[cw4:cmod:docs:ac504307-18ee-4c6d-9a07-e7a070166594|V-Battlestation]] and [[cw4:cmod:docs:ae4805e8-0856-42d5-b374-2e7bceb4ec1c|Auto Station]] don't have this kind of AI. While a VAU has this AI enabled, it has full control over itself and will do it's own thing.\\ |
| This includes: | This includes: |
| * Restocking ammo. | * Restocking ammo. |
| Each fighter is still in independent control of itself while in a formation. It is very much that the fighter itself is responsible for being in the formation. If it runs out of ammo or is too damaged, it will retreat as it sees fit at any time it pleases. | Each fighter is still in independent control of itself while in a formation. It is very much that the fighter itself is responsible for being in the formation. If it runs out of ammo or is too damaged, it will retreat as it sees fit at any time it pleases. |
| ===== -Using the Fighter's UI- ===== | ===== -Using the Fighter's UI- ===== |
| :TODO: Insert UI Image.\\ | {{ :cw4:cmod:docs:vgpsf_ui.jpg?nolink&100|}} |
| This may be the main reason you are here at this wiki page. And if that is true, fine. I will provide the details here but please understand that the UI only looks complicated because the Fighter uses all 7 UI widgets, the 6th and 7th are unimportant in an immediate sense. <color #ffffff>Note: The UI Widgets start at 0 and end at 7.</color> | This may be the main reason you are here at this wiki page. And if that is true, fine. I will provide the details here but please understand that the UI only looks complicated because the Fighter uses all 7 UI widgets, the 6th and 7th are unimportant in an immediate sense. <color #ffffff>Note: The UI Widgets start at 0 and end at 7.</color> |
| * <color #ffffff>0:</color><color #aaaaff>[]</color> | * <color #ffffff>0:</color><color #aaaaff>[FLIP]</color> **Target priority.** The targeting priority of the Fighter between Deepest and Closest. |
| * <color #ffffff>1:</color><color #aaaaff>[]</color> | * <color #ffffff>1:</color><color #aaaaff>[CHOICE]</color> **Hover Height.** What altitude the Fighter should fly up to when under manual control. |
| * <color #ffffff>2:</color><color #aaaaff>[]</color> | * <color #ffffff>2:</color><color #aaaaff>[CHOICE]</color> **Charge speed.** How fast energy is sent to the Fighter whenever connected to the network. Default refers to the vanilla speed that almost all vanilla units use which is 2 packets a second. "~MAX" is 30 packets a second. |
| * <color #ffffff>3:</color><color #aaaaff>[]</color> | * <color #ffffff>3:</color><color #aaaaff>[FLIP]</color> **Auto Restock.** A switch to turn Auto Restock behavior on and off. You will probably never touch it. |
| * <color #ffffff>4:</color><color #aaaaff>[]</color> | * <color #ffffff>4:</color><color #aaaaff>[CHOICE]</color> **Desired ammo.** How much ammo the Fighter needs to obtain before it is considered restocked. |
| * <color #ffffff>5:</color><color #aaaaff>[CHOICE]</color> The [[https://knucklecracker.com/wiki/doku.php?id=cw4:cmod:docs:6bff7473-183e-4731-b28a-c4905d87fb9f#full_ai_mode | Full AI]] controller. What is selected in this UI Widget determines the behavior of the [[https://knucklecracker.com/wiki/doku.php?id=cw4:cmod:docs:6bff7473-183e-4731-b28a-c4905d87fb9f#full_ai_mode | Full AI]] which will then take over control of the Fighter unless set to the special "Full AI" of "LEADER", the last type in the list of AI choices. | * <color #ffffff>5:</color><color #aaaaff>[CHOICE]</color> **AI Mode.** The [[https://knucklecracker.com/wiki/doku.php?id=cw4:cmod:docs:6bff7473-183e-4731-b28a-c4905d87fb9f#full_ai_mode | Full AI]] controller. What is selected in this UI Widget determines the behavior of the [[https://knucklecracker.com/wiki/doku.php?id=cw4:cmod:docs:6bff7473-183e-4731-b28a-c4905d87fb9f#full_ai_mode | Full AI]] which will then take over control of the Fighter unless set to the special "Full AI" of "LEADER", the last type in the list of AI choices. |
| * <color #ffffff>6:</color><color #aaaaff>[LABEL]</color> Informative text that says what formation the Fighter will enforce when in a type of LEADER AI mode. | * <color #ffffff>6:</color><color #aaaaff>[LABEL]</color> Informative text that says what formation the Fighter will enforce when in a type of LEADER AI mode. You need to scroll down the UI to see the text. |
| * <color #ffffff>7:</color><color #aaaaff>[LABEL]</color> Status text which has proven to not even be working and was long discontinued as legacy debug code that wasn't specifically just for debugging long ago, hence why it wasn't removed during that time. You would need to scroll down the UI to "see" this blank widget. There is an off chance text will successfully display there but I have not seen this myself. You can treat this UI Widget as nonexistent. | * <color #ffffff>7:</color><color #aaaaff>[LABEL]</color> Status text which has proven to not even be working and was long discontinued as legacy debug code that wasn't specifically just for debugging long ago, hence why it wasn't removed during that time. You would need to scroll down the UI to "see" this blank widget. There is an off chance text will successfully display there but I have not seen this myself. You can treat this UI Widget as nonexistent. |
| |
| | ---- |
| |
| ====== Download location and CPACK location: ====== | ====== Download location and CPACK information location: ====== |
| [[http://knucklecracker.com/forums/index.php?topic=39457.new#new | Download location (see latest reply)]]. | [[http://knucklecracker.com/forums/index.php?topic=39457.new#new | Download location]]\\ |
| [[cw4:cpack:docs:7f65b557-95b9-47d0-807a-5d05b1b426db|CPACK information location.]] | |
| |
| | <=[[cw4:cpack:docs:7f65b557-95b9-47d0-807a-5d05b1b426db| VAU CPACK]]\\ |
| <=[[cw4:info:start#custom_units| Index]] | <=[[cw4:info:start#custom_units| Index]] |
| | |
| | ---- |
| | |
