<=[[cw4:info:start#custom_units| Index]]\\ <=[[cw4:custom| Custom CPACKs & Units]]\\ <=[[cw4:cpack:docs:0af46b44-90a2-404d-8909-749beb5df3e3| CPACK - VPAC Creeper Expansion]]\\ <=[[cw4:cpack:vpac_wiki_page| VPAC Wiki Page]]\\ [[http://knucklecracker.com/forums/index.php?topic=41251.0|VPAC CPACKs download location.]]\\ ====== [VPAC Creeper Expansion] Flow Controller ====== {{ :cw4:cmod:docs:flow_controller.jpg?nolink&400|}} The Flow Controller is the only VWC system that can directly manipulate the flow of Creep, **BUT NOT ANTI-CREEP!**((This is a major difference between normal PAC and VPAC!))\\ The Flow Controller uses a simple array of Force Emitters to accelerate the Creep median into a specific direction. This can work even with the controller not submerged by accelerating the air particles to create a wind current which can move shallow Creep. If this is being used in space, well then nanites are used with a swapped version of the Flow Controller which looks identical for sake of consistency.\\ Fun fact: The Flow Controller is merely an adoption of a preexisting system into the VWC project. ===== Overview ===== * Uses 2 power. * 'Pushes' Creeper in a specific direction. This enhances the flow of the Creeper too. On mesh, which increases Creeper flow on terrain, a Flow Controller is able to direct the Creeper so quickly, it does not build up into a mountain of Creep. If you are having flow problems, you can use Flow Controllers to enhance the flow of Creep throughout the map if the [[cw4:cmod:docs:9374ef02-1ef9-43ff-b379-9a92aa79baa9|Egg Fabricator]] is not preferred in favor of consistent flow. * CAN BE STUNNED. * CAN BE NULLIFIED. * IMPERVIOUS TO NORMAL DAMAGE. * :WARNING: Prior to //around// VPAC v2.8.0.0, you must set a **new** flow direction for the Flow Controller after experiencing any kind of power deficit while unpaused as it would become idle. ===== Optimized use ===== The Flow Controller's ability to enhance the flow of Creeper has a downside. Since Creeper is moving to the frontlines faster, more Creeper can be killed at said front lines, mainly by Depth-seeking weapons. This will cause the total Creeper to drop considerably if the Flow Controller is misused, especially with mesh. Having [[cw4:cmod:docs:d476c68d-631d-450c-8e7f-81e5e9da8dda|Emitter Bases]] to produce Creeper in front of a Flow Controller is the ideal method to exploit the enhanced Creeper flow. If mesh is to be considered, the mesh should be local to those same Emitters only and not the main mesh network you may of constructed. This ensures the Flow Controller does not redirect effectively all your Creeper to the point it eventually tickles into the enemy front lines due to the enhanced flow. It needs to redirect waves and built-up Creep, not just flow direction, otherwise the Flow Controller will have no "Pushing Power" into enemy defenses once the initial wave of Creeper is pushed back (which is very likely as the defenses should be at full strength prior to the assault, leaving nothing to follow up, allowing the enemy to rebuild). This is so much of a problem, it may be wise to avoid using Mesh around a Flow Controller when pushing into enemy defenses.\\ Remember, the Flow Controller is not weaker in push force in VPAC than in PAC. The only difference is that it can't push Anti-Creeper in VPAC. By far one of the strongest combos ever is a Flow Controller pushing into 2 [[cw4:cmod:docs:d476c68d-631d-450c-8e7f-81e5e9da8dda|Emitter Bases]] with a [[cw4:cmod:docs:4576bde4-8fe7-4c6f-bdd2-68f6782a652e|Crimsonator]] in front of the flow direction beside the Emitters. This combo was so strong, it is the sole reason the Flow Controller has increased Power Use compared to PAC. It is still powerful but requires investment (in this example, it would be 5.5 power) but never forget, the combo itself wasn't nerfed, it was just made harder to execute conveniently.