Game Mechanics Subclasses

subclasses
our idea was to create subclasses classes that u unlock by doing quests or dungeons they can only be used by a certain class and you can only use it when u meet the requirements in each character when u do so u can switch to that subclass(u can switch back) it uses the same weapons but has different spells and stats maybe u could even customize your spells(idk if this is possible) so if you wanted to become theorick maybe you have to complete the ice barrows dungeon this would add a better reason to do dungeons like eldritch outlook where you get access to a whole new area im not gonna work out every class i leave that up to the ct but this would add so much more variety to the game some examples:
ranger:
focuses on speed and agility upgrades the escape spell and adds other spells which includes movement and fire speed
ice mage:
similar to theorick uses ice magic enhances ice snake and adds other slowness spells could be unlocked when completing ice barrows
hope you all like this idea i would love to get this implemented altho it might be hard to add such a big thing

 

I think this could be a great idea and will most likely keep the game fresher for longer. It would take a long time and plenty of work to produce though.

 

yea it would take long but if they do it would be rlly cool and thnx

 

I think this is already well achieved by major ids, they are more easily made and dont require drastic shifts in game mechanics. Even regular builds without major ids can have wildly different playstyles.

 

Please use punctuation. And don't leave stuff up for the ct, this is your suggestion, so give deeper ideas on what you want to see.

 

i think its the idea im suggesting not the way its gonna be implemented cus after all i dont know whats possible

and i think major ids dont do that much in comparison what i want, i want different spells and base stats so thats way different then major ids

 

Okay, so while the base idea of Subclasses that can change up spells a bit, this suggestion feels very barebones. Also first off, like Lousyre said,

Pls work on your grammar. The lack of capitalization and using "u" instead of "you" make it feel less like your using it out of quirkiness/flavor, and more so as if your making a joke thread and is hard to take seriously. Secondly, I feel like dungeons couldn't unlock Subclasses. Following the logic of unlocking Subclasses, how would beating a Corrupted fire guy by drowning him in lava make me learn how to a Berserker and do fiery Warrior spells? I feel like they could have exclusive quests to unlock them since that would make more sense to take a sort of "Trial of Mastery" to unlock new types of spells for your class. Also, please give more details. Expand on how Ice Snake is improved for Ice Mage, how does Ranger's Archer Spells get more movement/Speed, how long is the Speed? Try to put more Subclasses than just two for your example. Put at least one for each class, since you're making this a very tough sell for us readers with the lack of details and leaving it to the CT kinda makes this suggestion feel very incomplete. Lastly, Subclasses shouldn't just be Spells + Status Effect. Subclasses by concept are supposed to offer a new or expand the playstyle of a normal class to create differing ways of playing a class, like say Warrior branching off from DPS Berserker, or a Defensive Crusader. Just adding Status Effects for Subclasses isn't really that dynamic, and doesn't leave a memorable impression as compared to even some Major IDs in changing how the player plays and how they have to design their gear around their Class and Subclass.

 

Subclasses are classes that can be derived from a parent class by adding some functionality, such as new object variables or new methods. In terms of automaton theory, a subclass adds new states and new rows to the state transition table. However, most OO languages also allow us to derive subclasses from parent classes by overriding (modifying) existing functionality. By using inheritance mechanisms between parent class and subclass, it is only necessary to specify the new or modified functionality when implementing a class. The purpose of class hierarchies is to establish a mechanism for software reuse, not to establish an order relation between objects.