VS:NF reminders · 6:43pm Jun 8th, 2013
Hey everyone,
With Chapter 10 finally having been released, I realize that there are few minor details about just stuff in general in the story that you may have forgotten due to the stupid long length of time it took for this update to happen or simply because I haven't mentioned it. Anyways, to spare you the need to go back and reread the story (which you're free to do so if you'd like), I decided that I'll just post some brief reminders of small things, as well as explain some things that otherwise would not be explained in the story. Here you go:
-Spy is an ARF trooper and has green decals. He's also a jerk.
-Gore's helmet has a crack in it, and he has blood red decals resembling a manticore.
-Viktor has a custom modified bowcaster.
-R8 is an R2 series astromech droid with a brown and silver color scheme.
-Other clones have landed on the surface.
-Poh Drüne, the Jedi Grievous killed in chapter 1, had an orange lightsaber which Grievous now has.
As far things I'd like to explain, I've only got two. Firstly: why a Heartstrings family picture was found in Appleloosa. Well, this is explained in my upcoming story Lyra: Lost and Found, so just know that this will be justified. Just a little later.
Secondly: the droids' odd way of speaking, and general lack of speaking. You've probably noticed a lot of “entity: something” thrown in whenever a droid speaks, so I thought I'd clarify. To me, the droids only have a set amount of known things in their vocabulary. And to me, a droid would not be able to learn what something unknown to them is except by having it programmed into them (unless they had some sort of really advanced adaptive learning software installed...being battle droids, that's automatically a no). But, at least in this rendition of the droids, they do have a way of coping with unknown terms, done by listing them as an entity that would then require being programmed into the droid at a more convenient date. So, Equestria, for example, is unknown to droids. Whenever mentioning Equestria, it would be identified as entity: Equestria until that term and all associated knowledge about it was to be hardwired in. For the most part, droids will have all Separatist vehicles, important members, locations, weaponry, and protocols programmed in.
As for why they're quiet: they can communicate via telecommunication; there's no need to talk. Grievous will talk to droids so that the particular droid he want to talk to is aware of that fact, and droids will talk to Grievous to indicate that what they have to say is for the general's ears only, but other than that, they telecommunicate. Screw what canon has to say about this.
Anyways, these are just a couple of things that I wanted to remind you of without having to force you to reread. Have a good day,
Legofan24
I said it before but all droids in Start Wars are just pathetic and useless. I can come up with ones ten times better then them (Making them is a whole other idea, but I'm sure that someone there could
)
Anyway, I'll read it when I get the chance
1132548
Aye... Well seeing and knowing that even the mass produced R2+ droids have an way more enhanced programming and AI, those toasters with weapons are nothing.. sure mass produsing them is sure cheap.. but really: why go the cheap way when you can get Droids ten time more effective but slightly 10% more expensive for real battle-Machines?!
These things don´t even have IR,MAD,Seismic-sensors...
And then the Veghicles: why man them with droids?!It would be waay more efficient to just make them "droids" too...
Because of all that, I think of your Droids as more true.
1135605 I totally agree with the 'make the vehicles droids' too. For the most part, that's the smart thing, but there would be certain advantages to having vehicles manned as they are. When the vehicle gets destroyed, there's still the chance that the pilot survives, which would allow the combined unit to continue fighting.
That...that's the only benefit I can see.
Star Wars droids have some issues with rational and practical design.
1135788
Hmmm.. yeah somewhat right.But the faact that both would be disabled with these puny little emps is laughable XD both units are destroyed, instead of just one, wich could´ve been protected against it with the given space for the Pilot.
I would prefer a BattleMech. Piloted by a human. A machine shouldn´t pilot a machine.. that´s somewhat if I would sit on the shoulders of a warrior and give orders
1135854 Yup, I'm with you there. Making machines pilot machines is a silly waste of resources and is highly inefficient. While I'm trying to make the battle droids seems more reasonable (with their communicate via radio as opposed to vocally, and all that), I sadly can't break canon here and have the AATs pilot themselves
.