Proposed Kancolle Pool

NWF_Renim said:

All these groups were created based on a connection, historical, stage, class, color, and etc, so why is the grouping itself important, when an alternative connection tag would cover the concept of why they're linked and placed together in the image. Even team 9 at its core is stage boss connection.

The thing is, we should use one tag to cover it all. But anyway, I don't have any problems with _connection (may it be class, historical, group, stage, playable, role, type, etc), might as well we use these instead of clique.

So the possibles are:

stage_connection for touhou to replace pool #2353.
class_connection for different classes (ship-class, job-class, etc).
team_connection for team_9 (also applicable for military divisions and squadrons)
historical_connection for characters that were connected by a real life historical event.

Lunatic6 said:
So the possibles are:

stage_connection for touhou to replace pool #2353.
class_connection for different classes (ship-class, job-class, etc).
team_connection for team_9 (also applicable for military divisions and squadrons)
historical_connection for characters that were connected by a real life historical event.

+1 for stage_connection.

I don't care much either way for the rest, except team_connection for team 9. Team 9 members are part of a team because they are often portrayed as sharing some character traits (weak, silly, childish, etc.) and not just because they're a team, so something like trait_connection (though we currently use it slightly differently) is closer to what they and things like pool #1053 are about.

Fred1515 said:

Team 9 members are part of a team because they are often portrayed as sharing some character traits (weak, silly, childish, etc.) and not just because they're a team, so something like trait_connection (though we currently use it slightly differently) is closer to what they and things like pool #1053 are about.

then use age_connection for pool #1053, but what if there is an age altering tag (older or younger) should this still be applicable?

The class and historical would be about the same things so just how about history connection. It can then cover the meta gameplay logic of stage connection that wouldn't fit under trait connection. Alternatively, it could be about in-series traits.

Something like:
history connection = similar backgrouds/associations

I just added stage_connection in every posts within pool #2353, I also created a wiki (mostly base on the pool's description) on how to use the tag. That's one less problem to worry about, I hope did the right thing.

Lunatic6 said:

then use age_connection for pool #1053, but what if there is an age altering tag (older or younger) should this still be applicable?

One thing though. Are you seriously bringing that up?

monhan said:

One thing though. Are you seriously bringing that up?

That was just an idea for pool #1053, my main priority was still to create a unified tag for the destroyer-classes and now can be extend for every ship-classes (which suppose to be a pool but the situation has changed).