Line 3: |
Line 3: |
| The following list is what I think are good ideas to implement in KC in order to improve the game, while keeping its basic aesthetic, and keeping in mind that it is still a free-to-play game that needs to make money. I absolutely do not want to transform this game into a generic and forgettable Gacha, I just want to imagine how an up-to-date Kancolle can be, with many features that I believe are missing in this 11+ years old game. I also consider that no 3rd party software should be used because if the game is "good enough" or even "perfect", it simply does not need such things (even so I will still use them myself). | | The following list is what I think are good ideas to implement in KC in order to improve the game, while keeping its basic aesthetic, and keeping in mind that it is still a free-to-play game that needs to make money. I absolutely do not want to transform this game into a generic and forgettable Gacha, I just want to imagine how an up-to-date Kancolle can be, with many features that I believe are missing in this 11+ years old game. I also consider that no 3rd party software should be used because if the game is "good enough" or even "perfect", it simply does not need such things (even so I will still use them myself). |
| | | |
− | <div align="center" style="margin:20px"><span style="border:1px red solid;padding:20px"><span style="border:1px red solid;padding:10px">'''{{color|red|Remove the stupid idea to have the Strike Force fleet in the 3rd fleet, the single worst design element in the entire game.}}'''</span></span></div> | + | <div align="center" style="margin:20px"><span style="border:1px red solid;padding:20px"><span style="border:1px red solid;padding:10px">'''{{color|red|Remove the stupid idea to have the Striking Force fleet in the 3rd fleet, the single worst design element in the entire game.}}'''</span></span></div> |
| | | |
| <tabber> | | <tabber> |
Line 18: |
Line 18: |
| **Maybe also give 5-10 slots with a hard quest for each KC anniversary, depending on the recently added ships. | | **Maybe also give 5-10 slots with a hard quest for each KC anniversary, depending on the recently added ships. |
| | | |
− | *{{color|red|All ships required in quests '''must be''' obtainable at any moment}}, so you are not blocked at some point, praying for the next event (for [[Gotland]], [[Fletcher]], [[Johnston]], [[Samuel B. Roberts]], [[Gambier Bay]], [[Shinshuu Maru]], and [[USN]] SS). | + | *{{color|red|All ships required in quests '''must be''' obtainable at any moment}}, so you are not blocked at some point, praying for the next event ([[Gotland]], [[Fletcher]], [[Johnston]], [[Samuel B. Roberts]], [[Gambier Bay]], [[Shinshuu Maru]], [[Hatsuzuki]], [[Richelieu]], [[USN]] SS, ...). |
| **Making them "normal" drop is the best way to fix it, | | **Making them "normal" drop is the best way to fix it, |
| **Another way to fix it, is to modify those quests, so they can accept the unavailable ship, as well as some other alternative. | | **Another way to fix it, is to modify those quests, so they can accept the unavailable ship, as well as some other alternative. |
Line 97: |
Line 97: |
| | | |
| |-|Event= | | |-|Event= |
− | *'''{{color|red|Remove the stupid idea to have the Strike Force fleet in the 3rd fleet, this adds NOTHING to the game but frustration and big mistakes.}} | + | *'''{{color|red|Remove the stupid idea to have the Striking Force fleet in the 3rd fleet, this adds NOTHING to the game but frustration and big mistakes.}} |
| **For now, it is objectively and factually terrible game design and proof of lazy/spaghetti coding. | | **For now, it is objectively and factually terrible game design and proof of lazy/spaghetti coding. |
− | **Making all fleets (aka n°1) "expedition capable" would be the best/easiest way to fix this flaw. | + | **Making all fleets (aka n°1) "expedition capable" can be a way to fix this flaw, but having the SF in the main fleet is unequivocally better. |
| **Historical elements are very much welcomed, unless they are detrimental to the game. | | **Historical elements are very much welcomed, unless they are detrimental to the game. |
| | | |
− | *'''{{color|red|Rework "tag routing" !}} | + | *'''{{color|red|Rework "tagging" !}} |
− | **In its recent implementations, it was possible to lock himself totally, making the event impossible to clear in '''ANY difficulty. | + | **In its some implementations, it was possible to lock himself totally, making the event impossible to clear in '''ANY difficulty. |
− | **If locks are not supposed to be an issue in lower difficulties, then a way to bypass this "tag routing" must be easily possible in those cases. seems fixed since mid 2022) | + | **If locks are not supposed to be an issue in lower difficulties, then a way to bypass "tag routing" must be easily possible in those cases. seems fixed since mid 2022) |
| + | **Locks should not be applied immediately upon sortie, in order to let us cancel any mistake sortie before it is too late. |
| + | ***The Summer 2023 E-5 implementation was almost perfect in this regard, and should be the only way around. |
| | | |
| *Historical bonus general nerf. | | *Historical bonus general nerf. |
| **It must be a simple bonus fact, not a game-breaking thing that is a "must-have" each time. | | **It must be a simple bonus fact, not a game-breaking thing that is a "must-have" each time. |
| + | **European/summer bonuses are even crazier and must be simplified. |
| | | |
| *Remove the possibility to drop nothing on an S rank on absolutely every "boss". | | *Remove the possibility to drop nothing on an S rank on absolutely every "boss". |
| + | **So far, sub-bosses are treated as regular nodes, not event counting for quests. |
| | | |
| *Friendly fleets "from the start", but using them add a drawback, like less/worst drops for instance. | | *Friendly fleets "from the start", but using them add a drawback, like less/worst drops for instance. |