FANDOM


  • This thread have been opened since the last two events in order to obtain information pertaining the event bosses, due to the fact that their information are no longer accessible from the master data from Summer 2015 Event onwards. This thread still fulfils that purpose for any potential new enemies introduced in the upcoming event.

    For this season however, we will be enforcing our preference for API calls over screenshot pictures due to the issues with the latter as stated by Hayashi H:

    • Inappropriate cropping by people who don't know what they're doing, leaving important info like enemy formation type out.
    • Inability to distinguish between identical looking but functionally different ships, like Standard Carrier Wo-Class Kai Flagship BannerAbyssal Hell Dive Bomber Kai 557 EquipmentAbyssal Revenge Torpedo Bomber Kai 558 Equipment and Standard Carrier Wo-Class Kai Flagship Banner, especially if not in the flagship position, or PT Imp Packs variant I and II.
    • Taking a ton of space on Mediawiki to hold on all the images, while API calls are text-only.

    For this reason, this thread will be more focused on instructing the players how to record the API calls, such as kcsapi/api_req_sortie/battle.

    Some links to get you started on how to obtain API information in order to help wiki out:

    (more to be added)

      Loading editor
    • Additionally, here's the information pertaining the enemy boss voice lines, It has 8 digit numbers.

      http://203.104.209.55/kcs/sound/kc9998/{3 digits, map number}{3 digits, api_id number}{1 digit,type}{1 digit,damaged}.mp3

      For example: map number 32_4, api id = 644

      • pref+"10" is introduction line (undamaged)
      • pref+"21" is attacking line (damaged)
      • pref+"40" is sunk line
        Loading editor
    • I made a quick adaptation of Hayashi's template over at the sitrep thread, which added a bit of syntax highlighting. If you think it's satisfactory enough you can turn it into a template:

      {| border="0" class="wikitable mw-collapsible mw-collapsed article-table" style="width:500px;"
      |-
      ! width=100px | <span style="color:#F00">Map, Node and Difficulty</span> <!--type the map, node and difficulty below-->
      ! <!--type info here-->
      |-
      | colspan=2 | <!--Paste the contents of Battle below this line.--><div style="font-family:monospace;word-wrap:break-word!important;width:500px;box-sizing:border-box;"><syntaxhighlight lang="javascript" enclose="none">
         /* data goes here */
      </syntaxhighlight></div><!--Paste the contents of Battle above this line-->
      |}
      

      which turns into:

      Map, Node and Difficulty E-1-J, Normal
      svdata={"api_result":1,"api_result_msg":"\u6210\u529f","api_data":{"api_dock_id":1,"api_ship_ke":[-1,554,575,575,501,501,-1],"api_ship_lv":[-1,1,1,1,1,1,-1],"api_nowhps":[-1,34,37,25,24,24,36,53,35,35,20,20,-1],"api_maxhps":[-1,50,37,36,32,32,36,53,35,35,20,20,-1],"api_midnight_flag":0,"api_eSlot":[[504,542,543,-1,-1],[502,545,542,-1,-1],[502,545,542,-1,-1],[501,-1,-1,-1,-1],[501,-1,-1,-1,-1],[-1,-1,-1,-1,-1]],"api_eKyouka":[[0,0,0,0],[0,0,0,0],[0,0,0,0],[0,0,0,0],[0,0,0,0],[0,0,0,0]],"api_fParam":[[70,98,59,69],[54,89,59,57],[59,99,59,59],[59,89,48,59],[70,87,52,54],[59,88,78,50]],"api_eParam":[[42,72,27,36],[38,60,30,22],[38,60,30,22],[5,15,6,5],[5,15,6,5],[0,0,0,0]],"api_search":[5,5],"api_formation":[1,1,2],"api_stage_flag":[1,0,0],"api_kouku":{"api_plane_from":[[-1],[-1]],"api_stage1":{"api_f_count":0,"api_f_lostcount":0,"api_e_count":0,"api_e_lostcount":0,"api_disp_seiku":1,"api_touch_plane":[-1,-1]},"api_stage2":null,"api_stage3":null},"api_support_flag":0,"api_support_info":null,"api_opening_flag":0,"api_opening_atack":null,"api_hourai_flag":[1,0,0,1],"api_hougeki1":{"api_at_list":[-1,1,7,5,10,4,11,6,3,9,2],"api_at_type":[-1,0,0,0,0,0,0,0,0,0,0],"api_df_list":[-1,[11],[6],[8],[3],[9],[2],[10],[11],[4],[9]],"api_si_list":[-1,[6],[504],[63],[501],[-1],[501],[122],[91],[502],[3]],"api_cl_list":[-1,[0],[0],[1],[0],[1],[0],[1],[1],[1],[1]],"api_damage":[-1,[0.1],[0],[46],[0],[31.1],[0],[51],[50],[2],[25]]},"api_hougeki2":null,"api_hougeki3":null,"api_raigeki":{"api_frai":[-1,1,1,1,1,1,1],"api_erai":[-1,2,0,0,0,0,0],"api_fdam":[-1,0,0,0,0,0,0],"api_edam":[-1,229,0,0,0,0,0],"api_fydam":[-1,49,37,47,53,43,0],"api_eydam":[-1,0,0,0,0,0,0],"api_fcl":[-1,1,1,1,1,1,0],"api_ecl":[-1,0,0,0,0,0,0]}}}

      I'm also working on a little guide on copying output from api_req_sortie/battle calls using browsers and viewers; hopefully I'll have it complete before the event proper.

        Loading editor
    • Wasn't there a plan to implement something on KC3 Kai to give the player an option to enable sharing of the API data they come across during the last event? I forget the specifics already, but it would help streamline the process for people that aren't as savvy or too lazy to deal with the API information.

        Loading editor
    • KC3K has export replay option. The exported replay maps have sortie api data but we'll need people to state which nodes they went through.

        Loading editor
    • GuardianTK wrote: Wasn't there a plan to implement something on KC3 Kai to give the player an option to enable sharing of the API data they come across during the last event? I forget the specifics already, but it would help streamline the process for people that aren't as savvy or too lazy to deal with the API information.
      There used to be a website for that similar to kancolledb, Poi-statistics and myFleetGirls, but it's already defunct now.
        Loading editor
    • Technically I can read the nodes and difficulty for the replay API information alone, provided Kadokawa doesn't stuff up the convention of A = 1, B = 2 ... etc.

        Loading editor
    • would this tab suffice? so users can just screenshot theirs and you guys figure them out by ID

      Ss (2016-02-08 at 08.09.49)

      Also, I have included the stats and equip list on library page, so users can also just screenshot this

      Ss (2016-02-08 at 08.11.28)

        Loading editor
    • Dragonjet wrote: would this tab suffice? so users can just screenshot theirs and you guys figure them out by ID

      Ss (2016-02-08 at 08.09.49)

      Also, I have included the stats and equip list on library page, so users can also just screenshot this

      Ss (2016-02-08 at 08.11.28)

      Should be able to work fine, though you might wanna test multiple entries.


      Oh, and I'll be absent until 11th February, as I'll have to pay a visit to my grand-uncles tomorrow. No escaping obligatory visits it seems.

        Loading editor
    • That looks great. I'm having Wednesday off but if it comes during the evening I'll be able to help for only a bit as I have meeting early morning on Thursday.

        Loading editor
    • @Dragonjet That still has the issue of cluttering up MediaWiki with images though relative to a raw text form, and it's only useable if someone uses a viewer, though it's probably easier to teach.

      Using raw API text crosses all viewer boundaries, but it will require teaching people to know where to get the API calls.

        Loading editor
    • Hayashi H wrote:
      @Dragonjet That still has the issue of cluttering up MediaWiki with images though relative to a raw text form, and it's only useable if someone uses a viewer, though it's probably easier to teach.

      Using raw API text crosses all viewer boundaries, but it will require teaching people to know where to get the API calls.

      We can always just use the https trick to post images straight from image hosting websites instead of uploading it. But it doesn't seem like DJ has finished the enemy encounters tab. Since it doesnt seem like we agreed on any explicit form of submission, I guess I'll post APIs using Hayashi's and Mart's code. Also upload the replays into imgur and share that if you want to see it. 

        Loading editor
    • This is how they store maps now

      http://203.104.209.102/kcs/resources/swf/map/gmlbign_zjwmq.swf 33_01
      http://203.104.209.102/kcs/resources/swf/map/fgyvwqymk_ekn.swf 33_02
      http://203.104.209.102/kcs/resources/swf/map/fwy_wlrdttcoc.swf 33_03
      

      the placement for _ is ... I dunno.

        Loading editor
    • oh, great... seems like we're in quite a predicament for data mining now.

        Loading editor
    • "Naval Intelligence Command HQ"

      Why not Office of Naval Intelligence? =P

        Loading editor
    • Either way, the api_mst_shipgraph should tell which kanmusu has new voices

      SonyaUliana wrote: "Naval Intelligence Command HQ"

      Why not Office of Naval Intelligence? =P

      Because this sounds way cooler.
        Loading editor
    • Ar-cen-ciel wrote:
      Either way, the api_mst_shipgraph should tell which kanmusu has new voices

      SonyaUliana wrote: "Naval Intelligence Command HQ"

      Why not Office of Naval Intelligence? =P

      Because this sounds way cooler.

      But nothing is cooler than having a department name that you can shorten to "ONI".

        Loading editor
    • SonyaUliana wrote:

      Ar-cen-ciel wrote:
      Either way, the api_mst_shipgraph should tell which kanmusu has new voices

      SonyaUliana wrote: "Naval Intelligence Command HQ"

      Why not Office of Naval Intelligence? =P

      Because this sounds way cooler.

      But nothing is cooler than having a department name that you can shorten to "ONI".

      Oh okay, then the name accepted as an official name. End of discussion.
        Loading editor
    • @SonyaUliana please, this isn't the ideal place to talk about the proper naming conventions of some forum thread. We're expecting people to provide feedback on the new Abyssal vessels information that is working on the backend within the KC game.

      Worst is that you began this discussion since almost a day ago without providing something that isn't about abbreviation, etc to information we wiki desperately need:

      Name JP Name Battle Card HP API_Id
      Airfield Princess 飛行場姫 Airfield Princess Banner 500 556
      Airfield Princess/II 飛行場姫 Airfield Princess II BannerHell plane 2 500 631
      Airfield Princess/III 飛行場姫 Airfield Princess II BannerHell plane 2Abyssal Revenge Torpedo Bomber Kai 558 Equipment 500 632
      Airfield Princess/IV 飛行場姫 Airfield Princess II BannerAbyssal Hell Dive Bomber Kai 557 EquipmentAbyssal Revenge Torpedo Bomber Kai 558 Equipment 500 633?
      Airfield Princess/V 飛行場姫 Airfield Princess BannerAbyssal Liberation Land-based Dive Bomber 561 Equipment 500 650
      Airfield Princess/VI 飛行場姫 Airfield Princess BannerAbyssal Liberation Land-based Dive Bomber Ace 562 EquipmentAbyssal Liberation Land-based Dive Bomber 561 Equipment 500 651
      Airfield Princess/VII 飛行場姫 Airfield Princess BannerAbyssal Liberation Land-based Dive Bomber Ace 562 EquipmentAbyssal Liberation Land-based Dive Bomber Ace 562 Equipment 500 652?
      Supply Depot Princess 集積地棲姫 Supply Depot Princess Banner 600 653
      Supply Depot Princess/Damaged 集積地棲姫 Supply Depot Princess - Damaged Banner 380 656
      Supply Depot Princess/II 集積地棲姫 Supply Depot Princess BannerAbyssal Liberation Land-based Dive Bomber Ace 562 EquipmentAbyssal Liberation Land-based Dive Bomber 561 Equipment 600 654
      Supply Depot Princess/Damaged II 集積地棲姫 Supply Depot Princess - Damaged BannerAbyssal Liberation Land-based Dive Bomber Ace 562 EquipmentAbyssal Liberation Land-based Dive Bomber 561 Equipment 430 657
      Supply Depot Princess/III 集積地棲姫 Supply Depot Princess BannerAbyssal Liberation Land-based Dive Bomber Ace 562 EquipmentAbyssal Liberation Land-based Dive Bomber Ace 562 Equipment 600 655
      Supply Depot Princess/Damaged III 集積地棲姫 Supply Depot Princess - Damaged BannerAbyssal Liberation Land-based Dive Bomber Ace 562 EquipmentAbyssal Liberation Land-based Dive Bomber Ace 562 Equipment 480 658
      Heavy Cruiser Princess 重巡棲姫 Heavy Cruiser Princess Banner 350 659
      Heavy Cruiser Princess/IV 重巡棲姫 Heavy Cruiser Princess IV Banner 370 662
      Heavy Cruiser Princess/II 重巡棲姫 Heavy Cruiser Princess Banner 350 660
      Heavy Cruiser Princess/V 重巡棲姫 Heavy Cruiser Princess IV Banner 380 663
      Heavy Cruiser Princess/III 重巡棲姫 Heavy Cruiser Princess Banner 350 661
      Heavy Cruiser Princess/VI 重巡棲姫 Heavy Cruiser Princess IV Banner 390 664

      We're also missing out the enemy equipments' spaces as well:

        Loading editor
    • Uhmm, where do i report for their stat and equipment ?

        Loading editor
    • On this page please.

        Loading editor
    • Ah okay, i'm farming E-2 so gonna take sometime to get all the info.

      Oh and BTW, can someone show me how to make those expand/collapse tab


      Airfield Hime V ID#650

      "api_ship_ke":[-1,650,-1,-1,-1,-1,-1],

      "api_maxhps":[-1,32,56,31,50,33,30,500,-1,-1,-1,-1,-1],

      "api_eSlot":[[561,561,561,561,-1],[-1,-1,-1,-1,-1],[-1,-1,-1,-1,-1],[-1,-1,-1,-1,-1],[-1,-1,-1,-1,-1],[-1,-1,-1,-1,-1]],

      "api_eParam":[[50,0,120,140],[0,0,0,0],[0,0,0,0],[0,0,0,0],[0,0,0,0],[0,0,0,0]],

      "api_plane_from":[[-1],[7]],

      "api_stage1":{"api_f_count":0,

      "api_f_lostcount":0,"api_e_count":36,"api_e_lostcount":0,"api_disp_seiku":4,"api_touch_plane":[-1,-1]},

      "api_stage2":{"api_f_count":0,"api_f_lostcount":0,"api_e_count":36,"api_e_lostcount":31,"api_air_fire":{"api_idx":4,"api_kind":8,"api_use_items":[122,106]}},

      36 planes total

      Airfield hime basic VI - ID#651

      "api_ship_ke":[-1,651,-1,-1,-1,-1,-1],

      "api_maxhps":[-1,32,31,33,56,47,50,500,-1,-1,-1,-1,-1],

      "api_eSlot":[[562,561,561,561,-1],[-1,-1,-1,-1,-1],[-1,-1,-1,-1,-1],[-1,-1,-1,-1,-1],[-1,-1,-1,-1,-1],[-1,-1,-1,-1,-1]],

      "api_eParam":[[60,0,120,140],[0,0,0,0],[0,0,0,0],[0,0,0,0],[0,0,0,0],[0,0,0,0]],

      "api_kouku":{"api_plane_from":[[-1],[7]],

      "api_stage1":{"api_f_count":0,"api_f_lostcount":0,"api_e_count":48,"api_e_lostcount":0,"api_disp_seiku":4,"api_touch_plane":[-1,-1]},

      "api_stage2":{"api_f_count":0,"api_f_lostcount":0,"api_e_count":48,"api_e_lostcount":48,"api_air_fire":{"api_idx":2,"api_kind":5,"api_use_items":[122,122,106]}},

      48 planes total

      Supply depot hime basic ID#653

      "api_ship_ke":[-1,653,513,513,637,637,637],

      "api_maxhps":[-1,32,56,31,50,33,30,600,70,70,9,9,9],

      "api_eSlot":[[561,561,561,561,-1],[-1,-1,-1,-1,-1],[-1,-1,-1,-1,-1],[515,-1,-1,-1,-1],[515,-1,-1,-1,-1],[515,-1,-1,-1,-1]],

      "api_eParam":[[70,88,60,100],[0,0,0,10],[0,0,0,10],[9,88,12,19],[9,88,12,19],[9,88,12,19]],

      "api_kouku":{"api_plane_from":[[-1],[7]],

      "api_stage1":{"api_f_count":0,"api_f_lostcount":0,"api_e_count":36,"api_e_lostcount":0,"api_disp_seiku":4,"api_touch_plane":[-1,-1]},

      "api_stage2":{"api_f_count":0,"api_f_lostcount":0,"api_e_count":36,"api_e_lostcount":28,"api_air_fire":{"api_idx":4,"api_kind":8,"api_use_items":[122,106]}},

      36 planes

      Supply depot hime damaged ID#656

      "api_ship_ke":[-1,656,513,513,638,637,637],

      "api_maxhps":[-1,32,31,33,47,56,50,380,70,70,9,9,9],

      "api_eSlot":[[562,561,561,561,-1],[-1,-1,-1,-1,-1],[-1,-1,-1,-1,-1],[515,515,-1,-1,-1],[515,-1,-1,-1,-1],[515,-1,-1,-1,-1]],

      "api_eParam":[[130,88,70,130],[0,0,0,10],[0,0,0,10],[9,98,18,29],[9,88,12,19],[9,88,12,19]],

      "api_kouku":{"api_plane_from":[[6],[7]],

      "api_stage1":{"api_f_count":5,"api_f_lostcount":2,"api_e_count":48,"api_e_lostcount":1,"api_disp_seiku":4,"api_touch_plane":[-1,-1]},

      "api_stage2":{"api_f_count":3,"api_f_lostcount":0,"api_e_count":47,"api_e_lostcount":40,"api_air_fire":{"api_idx":2,"api_kind":5,"api_use_items":[122,122,106]}},

      48 planes

      Supply Depot Hime basic II _ ID#654

      "api_ship_ke":[-1,654,526,513,513,638,638],

      "api_maxhps":[-1,32,31,33,47,56,50,600,80,70,70,9,9],

      "api_eSlot":[[562,561,561,561,-1],[501,503,503,-1,-1],[-1,-1,-1,-1,-1],[-1,-1,-1,-1,-1],[515,515,-1,-1,-1],[515,515,-1,-1,-1]],

      "api_eParam":[[90,98,70,130],[15,0,0,35],[0,0,0,10],[0,0,0,10],[9,98,18,29],[9,98,18,29]],

      "api_kouku":{"api_plane_from":[[-1],[7]],

      "api_stage1":{"api_f_count":0,"api_f_lostcount":0,"api_e_count":48,"api_e_lostcount":0,"api_disp_seiku":4,"api_touch_plane":[-1,-1]},

      "api_stage2":{"api_f_count":0,"api_f_lostcount":0,"api_e_count":48,"api_e_lostcount":31},

      48 planes

      Supply depot hime damage II _ ID#657

      "api_ship_ke":[-1,657,526,526,639,638,638],

      "api_maxhps":[-1,32,31,33,47,56,50,430,80,80,15,9,9],

      "api_eSlot":[[562,562,561,561,-1],[501,503,503,-1,-1],[501,503,503,-1,-1],[515,515,-1,-1,-1],[515,515,-1,-1,-1],[515,515,-1,-1,-1]],

      "api_eParam":[[160,98,80,160],[15,0,0,35],[15,0,0,35],[15,98,18,29],[9,98,18,29],[9,98,18,29]],

      "api_plane_from":[[-1],[7]],

      "api_stage1":{"api_f_count":0,"api_f_lostcount":0,"api_e_count":72,"api_e_lostcount":2,"api_disp_seiku":4,"api_touch_plane":[-1,-1]},

      "api_stage2":{"api_f_count":0,"api_f_lostcount":0,"api_e_count":70,"api_e_lostcount":32,"api_air_fire":{"api_idx":2,"api_kind":5,"api_use_items":[122,122,106]}},

      72 planes

        Loading editor
    • Requesting help at Seasonal/Valentines_2016 to upload all the voice lines we could find.

      KuroPercher wrote:
      Oh and BTW, can someone show me how to make those expand/collapse tab

      Well, since you asked...
      {| class="mw-collapsible mw-collapsed wikitable"
      ! style="text-align:center; width: 500px; background-color:#eee;" |so much text wow
      |-
      |
      }}
      
        Loading editor
    • がか wrote: This is how they store maps now

      http://203.104.209.102/kcs/resources/swf/map/gmlbign_zjwmq.swf 33_01
      http://203.104.209.102/kcs/resources/swf/map/fgyvwqymk_ekn.swf 33_02
      http://203.104.209.102/kcs/resources/swf/map/fwy_wlrdttcoc.swf 33_03
      

      the placement for _ is ... I dunno.

      how to rip those maps?

        Loading editor
    • How to get links or how to extract SWF? You can google about SWF, for links you first look into the master file (api_start2, read linked guides in the main post), worlds with their names and IDs are in api_data.api_mst_maparea (currently six worlds and one event world), maps with names, IDs (api_id, api_maparea_id, api_no) and some extra info are in api_data.api_mst_mapinfo, so previously map's SWF link was http://<server>/kcs/resources/swf/map/<api_maparea_id>-0<api_no>.swf, but now you lookup api_id in api_mst_shipgraph (so E-1 is actually Amagi and E-2 is Katsuragi :|) for api_filename, and use http://<server>/kcs/resources/swf/map/<api_filename>.swf with underscore inserted somewhere in api_filename (try until you get 200).

        Loading editor
    • Sorry for all the edit spam, kind of hard to do it right.

      Anyway i edit to make it easier to read (i think).

        Loading editor
    •   Loading editor
    • Requesting help to confirm/include squadron slot sizes. From the Battle API calls available to me I can only see total number of aircraft and the types of squadrons equipped...

      But not information on what the slot sizes for each of them are.

      This affects air power values for all six forms of Headphone Princess, and all three new forms of Airfield Princess.

        Loading editor
    • New way of getting voice lines (in JS):

      var voiceLineKeys = [
        608614, 611089, 612644, 615991, 624682, 632529, 636124, 637891, 641202, 643709,
        653360, 658681, 663154, 670271, 676218, 685707, 688376, 697117, 703266, 704567,
        711864, 714839, 721252, 729643, 739348, 741591, 743682, 747913, 751020, 760519,
        764724, 770737, 774130, 780531, 787516, 791199, 800646, 803933, 809114, 816701,
        826054, 828189, 833136, 838541, 843764, 853221, 858988, 868253, 876444, 880371,
        883432, 886237, 889510, 896841
      ];
      
      function getVoiceLineFileName(ship_api_id, voice_line_id) {
        return 100000 + 17 * (ship_api_id + 7) * (voiceLineKeys[voice_line_id] - voiceLineKeys[voice_line_id - 1]) % 99173;
      }
      
        Loading editor
    • がか wrote: New way of getting voice lines (in JS):

      var voiceLineKeys = [
        608614, 611089, 612644, 615991, 624682, 632529, 636124, 637891, 641202, 643709,
        653360, 658681, 663154, 670271, 676218, 685707, 688376, 697117, 703266, 704567,
        711864, 714839, 721252, 729643, 739348, 741591, 743682, 747913, 751020, 760519,
        764724, 770737, 774130, 780531, 787516, 791199, 800646, 803933, 809114, 816701,
        826054, 828189, 833136, 838541, 843764, 853221, 858988, 868253, 876444, 880371,
        883432, 886237, 889510, 896841
      ];
      
      function getVoiceLineFileName(ship_api_id, voice_line_id) {
        return 100000 + 17 * (ship_api_id + 7) * (voiceLineKeys[voice_line_id] - voiceLineKeys[voice_line_id - 1]) % 99173;
      }
      
      Seems like they're gonna took us quite a while to crack.
        Loading editor
    • It's already, e.g. for Hayasui api_id = 460, Secretary line id = 2, so getVoiceLineFileName(460, 2) = 147693 is her Secretary line (<server>/kcs/sound/kc<api_filename>/147693.mp3). For any automated way of retrieving voice lines nothing really changed (once this function is known).

        Loading editor
    • がか wrote: It's already, e.g. for Hayasui api_id = 460, Secretary line id = 2, so getVoiceLineFileName(460, 2) = 147693 is her Secretary line (<server>/kcs/sound/kc<api_filename>/147693.mp3). For any automated way of retrieving voice lines nothing really changed (once this function is known).

      How do I swap voice line filenames?

      I-8, Atago and Kinugasa audio files seems to be the other way around, can you check?

        Loading editor
    • I will just swap them for now (and do the usual scan for any missing lines later).

        Loading editor
    • がか wrote: New way of getting voice lines (in JS): [...]


      Thanks for the hard work, Gaka. Someone pinched a deobfuscated Core.swf for you? :D

        Loading editor
    • It wasn't obfuscated, at least not SoundUtil, where this function is defined, it's decoded tho, but it can be countered by using http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/flash/net/FileReference.html#save() in mainD2.swf (I used RABCDAsm).

        Loading editor
    • A FANDOM user
        Loading editor
Give Kudos to this message
You've given this message Kudos!
See who gave Kudos to this message
Community content is available under CC-BY-SA unless otherwise noted.