Droid Engineer Archive
Thread: MODULE EFFICENCY CAP by DROID TYPE could save DEs
Hi
From the things we heard from the Devs and the Things i see as a DE i would like to make a suggestion of how to make a base concept for Droid Construction which should be rather easy to implement and helps to balance Droids without big work for our 25% Dev we DEs have. This is constructive and may be a help to lower his work on our profession and impelementing a solution in a realistic timeframe.
This would implement the suggested Battle Modules and Reaction Modules Thunderheart has presented to us! We could determine what Droids are efficent in Battle and who are less!
Here it comes: For each Droid Type we need "Module efficeny caps". When a Droid is constructed its Type will define how much Efficency from the implemented Modules are left at the end of construction. Right now we can build Droids with up to 110% Medical Efficency. In theorie we could up this to infinity with Clusters but at the End a CAP cuts it to 110% max for MSE and also for fighting probots.
Now why dont you do this also for diffrent Droid Types.
Example: Medical Modules Efficency
Surgical Droid Max CAP=110% Medical (Master of Medical needs)
R2 Max CAP=60% Medcial (Jack of all trades)
MSE Max CAP=20% medical (They suck but own with Data Storage capacity, Memory on wheels)
Probot CAP=0% medical (No Probots dont do healings!)
So people would use Surgical Droids for Medical needs mostly creating a realistic Starwars atmosphere.
Each Droid Type needs these kind of Caps and limitations on efficency. Like a MSE is KING OF DATA STORAGE and a Binary is KING OF ITEM STORAGE etc
This would be rather easy to implement and would widen the demand for diffrent Droid Types. Right now we only see R2s Probots and Surgicals. The rest is unwanted atm
With this CAP System diffrent upcoming Battle Droids would have there Pros and Cons. And not beeing just a 3D Module which cause couly vary so much from cooking machine to Battle Droid.
Please post your Ideas and Comments, maybe im wrong here but i think its an rather easy and basic step to sort things out which are IMBALANCED for DEs right now...