Talk:Sandbox/Event/E-6 formatted

This page is intended for fleet composition reports and branching rules discussion. DO NOT post equipment load-out or exchange map clearing tips here.

Report guidelines

Fleet compositions report

SINGLE FLEET

Report the fleet composition under the appropriate route header. If it's a new route, feel free to create a new route header using this form. ;{Route} Append under the route header the fleet composition using this form *-- ~~~~ ** {Names of ship girls in fleet} If fleet composition has a chance to go another route, report to both routes with frequency of occurrence using this form: *-- ~~~~ ** {Names of ship girls in fleet} ({Route 1}) {frequency} ({Route 2}) {frequency} When unsure of frequency, use ?/? EXAMPLE A-D-C-E-F -- Fujihita (talk) 12:46, July 25, 2016 (UTC) Isuzu, Inazuma, Yuudachi, Shigure, Akatsuki, Akitsumaru -- Fujihita (talk) 12:46, July 25, 2016 (UTC) Abukuma, Samidare, Yayoi, Shigure, Yukikaze, Akitsumaru -- Fujihita (talk) 12:46, July 25, 2016 (UTC) Abukuma, Fubuki, Yuudachi, Ayanami, Yukikaze, Akitsumaru (A-D-C-E-F) 4/7 (A-B-E-F) 3/7 -- Fujihita (talk) 12:46, July 25, 2016 (UTC) Naka, Hamakaze, Yuudachi, Inazuma, Yukikaze, Akitsumaru (A-D-C-E-F) ?/? (A-B-E-F) ?/? A-B-E-F -- Fujihita (talk) 12:46, July 25, 2016 (UTC) Abukuma, Fubuki, Yuudachi, Ayanami, Yukikaze, Akitsumaru (A-D-C-E-F) 4/7 (A-B-E-F) 3/7 -- Fujihita (talk) 12:46, July 25, 2016 (UTC) Naka, Hamakaze, Yuudachi, Inazuma, Yukikaze, Akitsumaru (A-D-C-E-F) ?/? (A-B-E-F) ?/?

COMBINED FLEET

Similarly, append under the appropriate route(s) using the form *-- ~~~~ ** {Names of ship girls in fleet 1} ** {Names of ship girls in fleet 2} ({Route 1}) {frequency} ({Route 2}) {frequency} EXAMPLE A-B-E-F -- Fujihita (talk) 12:46, July 25, 2016 (UTC) Isuzu, Inazuma, Yuudachi, Shigure, Akatsuki, Akitsumaru Chiyoda, Chitose, Mogami, Mikuma, Yayoi, Mutsuki -- Fujihita (talk) 12:46, July 25, 2016 (UTC) Isuzu, Inazuma, Yuudachi, Shigure, Akatsuki, Akitsumaru Chiyoda, Chitose, Mogami, Mikuma, Yayoi, Mutsuki (A-D-C-E-F) 4/7 (A-B-E-F) 3/7 A-D-C-E-F -- Fujihita (talk) 12:46, July 25, 2016 (UTC) Isuzu, Inazuma, Yuudachi, Shigure, Akatsuki, Akitsumaru Chiyoda, Chitose, Mogami, Mikuma, Yayoi, Mutsuki (A-D-C-E-F) 4/7 (A-B-E-F) 3/7

Branching rules proposal

BRANCHING RULES PROPOSAL

Use formalized statements to propose branching rules. Always attempt to narrow down the conditions as much as possible. The proposals should be structured as follow: *{Broad proposal} **{Narrow proposal 1} **{Narrow proposal 2} Once a statement has been verified, our staff will mark it as Verified and bring it to top level as well as add it to main event article. All broader conditions will be removed. This process is repeated until the narrowest set of rules is determined. Example "1CL, 4DD, 1LHA guarantees A-D-C-E-F" "1CL 3DD leads to A-D" "Akitsumaru leads to 100% C-E branching". "Shigure guarantees A-D" (Verified) (Fujihita (talk) 12:08, July 25, 2016 (UTC))

Report area

Fleet composition report

A-D-C-E-F

• -- Fujihita (talk) 17:02, July 25, 2016 (UTC)
  • Isuzu, Inazuma, Yuudachi, Shigure, Akatsuki, Akitsumaru
• -- Fujihita (talk) 17:02, July 25, 2016 (UTC)
  • Isuzu, Inazuma, Yuudachi, Shigure, Akatsuki, Akitsumaru
  • Chiyoda, Chitose, Mogami, Mikuma, Yayoi, Mutsuki (A-D-C-E-F) ?/? (A-B-C-D-E-F) ?/?
• -- McDerp (talk) 20:26, July 25, 2016 (UTC)
  • Ooyodo, Kagerou, Shiranui, Kuroshio, Oyashio, Akizuki
• -- McDerp (talk) 20:28, July 25, 2016 (UTC)
  • Ooyodo, Samidare, Umikaze, Kawakaze, Suzukaze, Akizuki
  • Yuubari, Shiratsuyu, Shigure, Murasame, Poi, Harusame

Branching rules proposal

• 1CL 4DD Akitsumaru leads to A-D-C-E-F
  • I think this is "1CL 3DD Akitsumaru 1XX" goes ADCEF (Fujihita (talk))
  • I tested it with 1CL 3DD without Akitsumaru, it goes ADCGHF so Akitsumaru = C-E (Fujihita (talk))
  • Further testing, it seems "1CL 3DD" is required to go A-D (Fujihita (talk))
    • Tested. 1CL 3DD works (Fujihita (talk))
    • Second that. I tried 1CL 2DD, off route (Fujihita (talk))

Sandbox area

This section is for discussion on the layout of this page and the guideline. It also serves as a playground for editors to get used to talk pages. It will not be included in the released version.

Here's a briefing of what our admins are doing in preparation of event

Automate enemy patterns

A few months back, we developed a number of tools to automate enemy patterns. This, for example, is a JS parser I developed to translate PoiDB's enemy patterns report into our template. However, when we checked the api two days ago, some api links (like the one listed on the above page) are dead.

You can use this link to test the parser.

In any cases, Gaka is looking for alternatives (besides Poidb). If all fail, we can simply set up enemy report threads as always since there haven't been any problems with those.

Update EventComp template and KC3K fleet exporter

I also asked Nanamin to update Template:EventComp to include plane proficiency, equipment upgrades and the new 33 LoS formula. Crazy Teitoku is in contact with KC3K team in order to bring back fleet exporter before next event (if all things go well, that is).

Event contribution guidelines

I asked Mikado to work on a guide on how to contribute to event wiki but he's not available until mid August. Therefore, I'm taking over his task. I plan to separate the messy stuffs from event pages, and put them in talk pages and community guide hub for sorting.

Improve page performance

In the meanwhile, ckwng is addressing performance issues with Lua modules and JS templates that have been causing internal error issues we've seen in the past week.

-- Fujihita (talk) 18:44, July 25, 2016 (UTC)

I like boobs Fackifiknow (talk) 19:25, July 25, 2016 (UTC)

Can that add topic button be moved or is there a keyboard shortcut? 

this is so fucking weird.... Fackifiknow (talk) 19:27, July 25, 2016 (UTC)

Well, click edit section and edit like the usual thing. Don't forget indentation to make it easier to look at. In any cases, this seems worse off than Comments for casual conversations. It's only better when it comes to data collection since we can move and group reports easily. -- Fujihita (talk) 19:34, July 25, 2016 (UTC)

stuff

Not being able to see the page or other comments while "commenting" hurts... as does the way these "comments" show up on Latest activity.

Automated patterns is sweet and I hope that works out.

... right so edit summary does that.

and when you dont tilde a few times?

dont mind me...

-- anon'd 67.246.170.39 19:55, July 25, 2016 (UTC)

I'd get used to it if I had to...

I wonder how many other people would be able to pickup and use Talk without it turning into a gigantic run on sentence written by dozens of people. Fackifiknow (talk) 20:04, July 25, 2016 (UTC)

This talk page doesn't support comment by default so we're doing this in talk page's way. The key point is to use indentation and to archive old discussions frequently.

There's a good thing about these talk pages though. They can be self-regulated. You don't need mod power to edit other people's comments (but do know that there's a public edit history, a Report Misbehavior thread and banhammer awaits the mischievous souls)

We'll still rely on comments for the most part though. This is just for data organization.

-- Fujihita (talk) 20:19, July 25, 2016 (UTC)

Fuji remember to kill that one Template. :v

-- McDerp (talk) 20:31, July 25, 2016 (UTC)

Getting ninja edited while slowposting.....

I can't say I hate it... but more people need to chime in on this for sure. 

   Fackifiknow (talk)

Event comp drills (minigame)

I propose the following minigame, which can be considered as an event drill.

So, we'll split the participants into two teams:

• The first team will compile a set of branching rules and share among themselves (and a neutral referee/GM). This team will then generate event comp reports based on the rules submit the reports to this page using the format outlined by the guidelines above.
• The second team will attempt to guess the branching rules based on the first team's fleet comp reports. Please do carry out the discussions in the manner outlined by the guidelines above.
• The game ends when the second team decides there's no other rules to discover or when the time (agreed upon by everyone) runs out.

There will be three difficulties for this game:

• Easy: there are plenty of reports and there's no false report.
• Medium: there are insufficient reports (second team must demand first team to provide a test with a certain ship or fleet comp in order to correctly determine all rules)
• Hard: there shall be false reports (dum dum dum!).

So...INTEREST CHECK! Who wants to play in round 1 (3 days, Easy difficulty)

-- Fujihita (talk) 20:53, July 25, 2016 (UTC)