Clan: (What is the name of your clan?)

Kekkei Genkai: (What special ability does your clan have? This section is just for the name, the description is below.)

Elements: (What elements does your clan require?)

Specialization: (What specializations does your clan require?)

Location: (Where is your clan located?)

Clan History: (What is your clan's history?)

Kekkei Genkai Description: (What does your clan's ability do? Remember, details are the key to a fast approval)

Drawbacks: (What is your clan bad at?)

Members: (Members of the clan can be updated here)

Kekkei Genkai Jutsu: (What jutsu is unique to your clan? There can be a max of four - with a limit of 1 S / SS rank jutsu, and 1 Scaling Jutsu.)

Nice work on the clan so far

KKG:
So I'm assuming that the core and it's attachments count as one weapon for the purposes of buying the weapon, could you expand on your code sample so that each individual attachment and the core has it's own app code, so that all of the components of the weapon are separate but still in one group. This is so it is clearly listed what exactly each attachment is (and what damage it does, ect) so that it is much easier to make judgement calls on what exactly these components can transform into.

I would like it mentioned that only the core or one of the attachments are able to have a special ability, so that a bunch of abilities are not crammed into one weapon.

For the modifications, state that the modification needs to list which component it is bound to.

For puppetry, the mechanisms are controlled remotely via chakra strings. So state that modifications need to list how they are triggered (flick a switch, ect.) when chakra strings are not active.

Drawbacks:

solid


Jutsu:

Sui Generis Arsenal: Modification

As mentioned above, I would like the modifications bound to one of the components, so there would not neccesarily be a stray modification (as that would be a component). However you can change the wording around so that you may reassemble the modifications to be bound to different components with the words 'if applicable', because if the mod is inbuilt into the component then you wouldn't be able to swap it around without it's component piece.

Sui Generis Arsenal: Synthesis

Awesome jutsu, but remove the SS (if you want to cheat, add an extra chakra cost onto the s rank to achieve the same effect but shh don't tell anyone)

Sui Generis Arsenal: Nonpareil

I can't allow more than A rank here. Also give an explanation and example on how the defensive properties work when the jutsu goes up a rank, e.g. what happens when the jutsu blocks an offensive of it's rank (half used) and then goes up a rank, how much can it block then?

Fukai wrote:KKG:
So I'm assuming that the core and it's attachments count as one weapon for the purposes of buying the weapon, could you expand on your code sample so that each individual attachment and the core has it's own app code, so that all of the components of the weapon are separate but still in one group. This is so it is clearly listed what exactly each attachment is (and what damage it does, ect) so that it is much easier to make judgement calls on what exactly these components can transform into.

I'm not sure if I may have portrayed it wrongly, but the Sui Generis Arsenal is supposed to be applied for as a puppet. The only difference is that the Sui Generis Arsenal, instead of having humanoid or animalistic limbs and appendages, has an entire weapon (either whole or broken down into its parts) as its 'Description'.

Assuming that's what you picked up on as well, would I just add the Weapon/Armor/Item template to that portion as well?

Fukai wrote:I would like it mentioned that only the core or one of the attachments are able to have a special ability, so that a bunch of abilities are not crammed into one weapon.

Understood. Will edit after.

Fukai wrote:For the modifications, state that the modification needs to list which component it is bound to.

This is something that I'd like to ask in more detail. What do you mean that they need to be listed which component they are bound to? I had thought that modifications were assigned to each limb(core/attachment) at the start of a thread.

Fukai wrote:For puppetry, the mechanisms are controlled remotely via chakra strings. So state that modifications need to list how they are triggered (flick a switch, ect.) when chakra strings are not active.

Drawbacks:

solid


Jutsu:

Sui Generis Arsenal: Modification

As mentioned above, I would like the modifications bound to one of the components, so there would not neccesarily be a stray modification (as that would be a component). However you can change the wording around so that you may reassemble the modifications to be bound to different components with the words 'if applicable', because if the mod is inbuilt into the component then you wouldn't be able to swap it around without it's component piece.

Sui Generis Arsenal: Synthesis

Awesome jutsu, but remove the SS (if you want to cheat, add an extra chakra cost onto the s rank to achieve the same effect but shh don't tell anyone)

Sui Generis Arsenal: Nonpareil

I can't allow more than A rank here. Also give an explanation and example on how the defensive properties work when the jutsu goes up a rank, e.g. what happens when the jutsu blocks an offensive of it's rank (half used) and then goes up a rank, how much can it block then?

I will address these later after my primary concerns/questions are sated. 

Thank you!

However you do it, I would just like a full description of each individual component and it's measurements and functions.

"This is something that I'd like to ask in more detail. What do you mean that they need to be listed which component they are bound to? I had thought that modifications were assigned to each limb(core/attachment) at the start of a thread. "
Well, modifications are like the abilities that the puppet has. If they are things that can be separated and assigned, then really they are components themselves (this is a grey line with a puppet weapon that should probably be cleared up in an explanation).