My goal: I want to make the Shifter SubClass incompatible with Paladins and Chanters.

 

Therefore i used the Character Tables and copied the Class ID`s into the field "IncompatibleWithIDs":[].

 

The problems i am facing with this approach are:

1. ClassID´s for some reason do not work so the class is still shown during character creation.

2. SubClassID´s remove the specific buttons but i can still click on so the Paladin or Chanter is created without a SubClass.

 

Is there any way to remove the Class- and SubClass-Combos for real? How?

 

Thanks for your help!!

The problem here, from a coding perspective, is that you can't control which class the player chooses first during character creation. So, there are probably not hard coded functions to limit a class based upon another class.

 

I do think implementing this restriction is possible, but it will probably involve a fair amount of work. I'm also not exactly sure how you'd go about that work yet either.

 

If, ultimately, certain class options cannot be restricted, then another approach is to gimp that restricted class so that there's not motivation to select it.

You are right @Armakoir. After several fails i also think that its best to gimp certain combos like power level penalties or similar. Should be much easier!

Paladins have restricted priest's deity selection, but it's hard coded, maybe is this a setting can be exposed?

I'm curious why you'd want to disable an optional thing in the game

We never implemented this idea @Mr Wockip but in the early stages of our Shifter Mod combos with Paladin or Chanter felt OP. A lot has happened since then! :D