|
|
| Author |
Thread Statistics | Show CCP posts - 3 post(s) |
Meisterjager Jagermeister
981
   |
Posted - 2015.05.16 23:21:00 -
[1] - Quote
My sincerest apologies if this has been previously addressed (it's just dem 13 pages tho):
If all suits have proto tier slot layouts according to race/role, what is to stop a basic level user from fitting their suit as if it were a different suit?
For example: Let us say I have only invested enough skill points for one level of Gallente Assault which allows me the use of STD level dropsuits only. Presently this suit has a slot layout of 1/3. A proto level GallAss has a layout of 3/5. Under this system, despite having only one level, I would have the 3/5 layout with only PG/CPU to limit my fitting choices. What is there to stop me from using the "power core" cpu/pg allotment to fit all three high slots? The current system allows only one.
If the answer is nothing, then this system also makes dropsuit RACE a redundant asset at early levels. I can now fit my std GA Assault as if it were a std Cal Assault. So if this is true, then why have racial suits at all? Just have one generic role suit?
To maintain racial layouts, you could remove racial slot layouts from the dropsuit and instead tie it to each power grid module, but then you have the same situation we have currently, only trading the suit for a module as we would need a separate module for each tier. No benefits will be gained.
How does this system work without confusing Race/Role slot layouts of differing skill levels?
AKA - StarVenger- Horizons' Edge
|
Meisterjager Jagermeister
982
|
Posted - 2015.05.16 23:51:00 -
[2] - Quote
Dreis ShadowWeaver wrote: I mean, you could fit a Gal Assault like a Cal Assault now, but do you? I don't see how this would change anything. 
A layout of 3/5 contains within it the 3/1 layout of a STD CALASS.
An uninhibited pg/cpu allotment allows me to fit the Std GALASS 3/1 (out of the 3/5) the exactly same way I fit the Std CALASS 3/1, thus removing Racial Slot Layouts as a limiting aspect differentiating these two STD level dropsuits from each other.
AKA - StarVenger- Horizons' Edge
|
Meisterjager Jagermeister
984
|
Posted - 2015.05.17 00:21:00 -
[3] - Quote
Dreis ShadowWeaver wrote:Ok....However, it would only be like that for the Standard suits in the situation that you're describing.
Correct. But then we start down a slippery slope; since the entire point of this system is to remove redundant assets we can now fold those two standard suits into one, and if we continue this trend with any other suits that overlap we may as well re-examine the entire dropsuirt system as a whole, scrap the entire thing and start DUST development all over again *cough*cough*legion*cough*rougewedding*cough.
AKA - StarVenger- Horizons' Edge
|
Meisterjager Jagermeister
984
|
Posted - 2015.05.17 00:54:00 -
[4] - Quote
Avallo Kantor wrote:You misunderstand the tiericide; the pg / CPU allotment for each level is based around fitting ALL slots with that level of module.
Then I am not sure I am in favor of tiericide.
You can design for what you intend to happen but players will ALWAYS use it as THEY intend.
Give me a 3/5 layout and a STD level module with enough resources to fit all at basic and I'll leave 4 slots empty and fit as much ADV and PROTO as I can. APEX suits avoid this only because they have all slots with locked in pre fits; you cannot leave a slot empty.
You will understand when you see Std level resourced GalAss bouncing around with 3 fibs and 4 or 5 empty low slots or a Std level resourced AmrAss running triple stacked shield extenders and an armor plate in a low slot.
AKA - StarVenger- Horizons' Edge
|
|
|
| |
|