![]() In short, saying that all the non-Commander units are drones raises a lot of Fridge Logic, especially for the UEF's units, which exhibit the "manned" appearances more clearly than the other sides. What's the point of designing a drone battlecruiser with rows of normal lights that look more like lit bridge windows? On the other hand, the Cyclone has intakes on either side of its fuselage, but it appears to have a cockpit where most manned aircraft have one.Īlso, look here at the UEF T3 Battlecruiser. The Phantom Ray has nothing that looks like a cockpit on its body, and in fact has an intake where the cockpit usually would be on a manned aicraft-this is typical of UAVs and UCAVs. Compare Boeing's Phantom Ray to the UEF's T1 Interceptor, the Cyclone. Modern unmanned combat vehicles don't have sensor pods shaped like cockpits. You could be right, but it doesn't make sense from a design standpoint. "Also, at the level of detail we get with the closeup, your 'cockpits, windows and bridges with bridge lights' could just be sensor pods, radios and normal lights.".Why would an entire Commander's army defect with him when he does, and how are they bringing personnel into combat to man constructed units when quantum teleportation gates only drop in one ACU at a time? Where's the chain of command? Also, at the level of detail we get with the closeup, your "cockpits, windows and bridges with bridge lights" could just be sensor pods, radios and normal lights. Well, I can't really provide a quote from the manual or anything like that, but the events in each game would make much less sense if the armies were actually manned.Is it explicitly stated somewhere that all the non-Commander units are just drones? Is it really true that all the units except the ACUs in Supreme Commander are piloted by AI? When I look at a lot of close-ups of units and buildings-especially on the UEF side-I see cockpits, windows, and bridges with bridge lights (in the case of naval units). ![]() PAGES WILL BE DELETED OTHERWISE IF THEY ARE MISSING BASIC MARKUP. DON'T MAKE PAGES MANUALLY UNLESS A TEMPLATE IS BROKEN, AND REPORT IT THAT IS THE CASE. THIS SHOULD BE WORKING NOW, REPORT ANY ISSUES TO Janna2000, SelfCloak or RRabbit42. The Trope workshop specific templates can then be removed and it will be regarded as a regular trope page after being moved to the Main namespace. All new trope pages will be made with the "Trope Workshop" found on the "Troper Tools" menu and worked on until they have at least three examples.Pages that don't do this will be subject to deletion, with or without explanation. All new pages should use the preloadable templates feature on the edit page to add the appropriate basic page markup. All images MUST now have proper attribution, those who neglect to assign at least the "fair use" licensing to an image may have it deleted.Failure to do so may result in deletion of contributions and blocks of users who refuse to learn to do so. Before making a single edit, Tropedia EXPECTS our site policy and manual of style to be followed.The AI section contains certain values that the unit's AI will use in certain situations. The Abilities section is used to give units buttons of corresponding abilities that can be used to activate abilities.ĪCU_Hunker BombBouncerCharge BombBouncerMegaBlast ConvertEnergy ConvertEnergyId DisruptorStation Electroshock EscapePod HalfBake HardenArtillery KnockbackWeapon Magnet MagnetPush Mobile_Hunker Overcharge Point_Defense_Hunker PowerDetonate Pullinsmash RadarOverdrive RogueNanites TriArmorHalfSpeed }, }, AI Below is an incomplete list of the fields and their purposes. The entire file is a call to UnitBlueprint with a large table. The following is documentation of the contents of a unit blueprint file.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |