KanColle Wiki
m (→‎Report guidelines: Change pre to nowiki and code combo)
Tag: sourceedit
No edit summary
Tag: sourceedit
Line 118: Line 118:
   
 
===Hard===
 
===Hard===
  +
  +
==Sandbox area==
  +
<div style="width:95%; border:2px solid darkred;font-size:20px; background:pink; text-align:left; margin:15px auto 20px;padding:5px;">
  +
;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.
  +
</div>
  +
  +
===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. [http://fujihita.azurewebsites.net/Poidb2NodeInfo.html 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 [http://db.kcwiki.moe//wiki/enemy/51.html this link] to test the parser.
  +
  +
In any cases, [[User:がか|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 [[User:Nanamin|Nanamin]] to update [[Template:EventComp]] to include plane proficiency, equipment upgrades and the new 33 LoS formula. [[User:Crazy_teitoku|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 [[User:Admiral Mikado|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, [[User:ckwng|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.
  +
  +
-- [[User:Fujihita|Fujihita]] ([[User talk:Fujihita|talk]]) 18:44, July 25, 2016 (UTC)

Revision as of 18:44, 25 July 2016

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

Spring 2016 E6 Map

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) ?/?

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))

Rewards

Easy

Medium

Hard

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)