-
Notifications
You must be signed in to change notification settings - Fork 7
Home
かがみ edited this page Sep 29, 2017
·
24 revisions
Don't be evil.
Server is running on http://poi.0u0.moe/ now.
You can get latest data dumped from the linked below:
https://poi.0u0.moe/dump/FILE
where FILE are one of the following:
- aaci.csv.gz
- quests.csv.gz
- createitemrecords.gz
- createshiprecords.gz
- dropshiprecords.gz
- passeventrecords.gz
- reciperecords.gz
- selectrankrecords.gz
All APIs are following the same format:
- URL:
http://[SERVER_NAME]/api/report/v2/[API_NAME]
- Method:
POST
- Body:
data=[JSON_PAYLOAD]
where SERVER_NAME
are currently poi.0u0.moe
. For now there are 3 possible API_NAME
available, namely create_ship
, create_item
, drop_ship
. JSON_PAYLOAD
is the JSON encoded / serialized data you are supposed to send, its content varies depending on API_NAME
, see following sections for detail.
URL: http://[SERVER_NAME]/api/report/v2/create_ship
Field | Type | Explanation |
---|---|---|
items |
[Number] |
Items for construction, from api_item1 to api_item5 in KanColle game api |
kdockId |
Number |
Dock ID, examples: [0, 3], note the index is 0-based, if you get it from KanColle API's api_kdock_id field, you need to minus 1 from it. |
secretary |
Number |
Secretaryship's ship_id |
shipId |
Number |
Result ship id |
highspeed |
Number |
use highspeed. [0, 1, 10] |
teitokuLv |
Number |
Game player's level |
largeFlag |
Boolean |
Set to true if it was LSC(大型舰建造) |
origin |
String |
(Optional) It's the name of your report plugin, requests' User-Agent will be used if not present |
URL: http://[SERVER_NAME]/api/report/v2/create_item
Field | Type | Explanation |
---|---|---|
items |
[Number] |
(Same as construction) |
secretary |
Number |
(Same as construction) |
itemId |
Number |
api_slot_item.api_slotitem_id on success. If development failed, api_fdata will be a comma separated list, get the second element from it (e.g. if api_fdata = "2,33" , you should fill this field with 33 ) |
teitokuLv |
Number |
(Same as construction) |
successful |
Boolean |
(Successful or unsuccessful.) |
origin |
String |
(Same as construction) |
URL: http://[SERVER_NAME]/api/report/v2/drop_ship
Field | Type | Explanation |
---|---|---|
shipId |
Number |
The ship_id got, -1 for nothing got |
mapId |
Number |
(Current map, 5-5 is 55, 1-6 is 16...) |
quest |
String |
(api_quest_name from KanColle API, the name of current map) |
cellId |
Number |
api_no from KanColle API, the name of enemy's fleet |
enemy |
String |
(api_enemy_info.api_deck_name from KanColle API, the name of enemy's fleet deck) |
rank |
String |
One of: ('S', 'A', 'B', 'C', 'D', 'E') |
isBoss |
Boolean |
Set to true if it is a boss node (api_color_no == 5) |
teitokuLv |
Number |
(Same as construction) |
mapLv |
Number |
Event specific indicating difficulties chosen (甲乙丙). api_eventmap.api_selected_rank if this is an event map, 0 otherwise. |
enemyShips |
[Number] |
api_ship_ke.slice(1, 7), 0 is always -1 therefore useless |
enemyFormation |
Number |
api_formation[1] |
origin |
String |
(Same as construction) |
URL: http://[SERVER_NAME]/api/report/v2/remodel_recipe
Field | Type | Explanation |
---|---|---|
recipeId |
Number |
recipe id, note that 101, 201, 301 will not be reported |
itemId |
Number |
item to improve |
stage |
Number |
improve stage, [0,6) = 0, [6, 10) = 1, 10 = 2 |
day |
Number |
day of week UTC+9 Tokyo/Japan |
secretary |
Number |
ship id of second slot, determined by api_req_kousyou/remodel_slot 's api_voice_ship_id
|
fuel |
Number |
0 if no fuel consumed |
ammo |
Number |
similar to above |
steel |
Number |
similar to above |
bauxite |
Number |
similar to above |
reqItemId |
Number |
item id for consumed items, will be -1 if no item consumed |
reqItemCount |
Number |
0 if no item consumed |
buildkit |
Number |
cannot be 0 |
remodelkit |
Number |
cannot be 0 |
certainBuildkit |
Number |
cannot be 0 |
certainRemodelkit |
Number |
cannot be 0 |
upgradeToItemId |
Number |
id for new item upgraded, only possible at stage 3, -1 if no information |
upgradeToItemLevel |
Number |
level for new item upgraded, -1 if no information |
key |
String |
key yp identify recipe, r${recipeId}-i${itemId}-s${stage}-d${day}-s${secretary}
|
origin |
String |
(Same as construction) |
Several KanColle tools/plugins have implemented supports for this, you can refer to them when in question: