Talk:Suggestion/@comment-25637142-20160724184715

In response to User:Fackifiknow's query yesterday. I've formulated a plan for branching rules culling in event. As usual, I'll start with the problems of the current system first.


 * Current system
 * Report thread contains fleet composition with full load-out, LoS and other stats. Some reports were more about suggested fleet load-out and map guide than simply reporting which ships were in the fleet and which route taken.
 * Formalization of branching rules is also done in the same report threads, and some scattered all over Event page's comments.
 * Rules posted in Branching rules section were mixed with Fleet composition reports and guide-like hints. Basically, Branching rules section became a down-sized mess of the report thread.

So for the new management system, I'm proposing a clear cut definition of the following concepts:
 * Fleet compositions report
 * For the purpose of branching rules determination.
 * Consists of ship class or ship name with the associated route and frequency of occurrence.
 * For example: 1CL, 4DD, 1LHA (A-D-C-E-F) 5 out of 5 / Isuzu, Inazuma, Yuudachi, Shigure, Akatsuki, Akitsumaru (A-D-C-E-F) 5 out of 5
 * Fleet build suggestion
 * For the purpose of guiding people through maps
 * Consists of ship class or ship name with the associated route and full equipment load out.
 * This is basically Template:EventComp
 * Branching rule proposal
 * Propose a branching rule based on fleet composition reports.
 * Formalized statements such as "1CL 3DD leads to A-D", "Akitsumaru leads to 100% C-E branching".

I propose abolishing the current fleet composition threads and use the old-school talk pages (http://community.wikia.com/wiki/Help:Talk_pages) instead. This way,
 * 1) We can separate different content (three concepts above) under different sections.
 * 2) Since everyone can edit talk page, the page can remain self-regulated and our staff can focus their efforts elsewhere.
 * 3) Archive old stuffs when the pages get too long.