- Welcome to the Kancolle Wiki!
- If you have any questions regarding site content, account registration, etc., please visit the KanColle Wiki Discord
Difference between revisions of "Game Updates/2024/March 3rd"
Jump to navigation
Jump to search
(Created page with "{{UpdateBar|PrevDate= February 27th|PrevYear= 2024|NextDate= March 3rd|NextYear= 2024}} ===Commence! Operation Tatsumaki! Update=== {| style="bor...") |
Jigaraphale (talk | contribs) m |
||
Line 1: | Line 1: | ||
− | {{UpdateBar|PrevDate= February | + | {{UpdateBar|PrevDate= February 29th|PrevYear= 2024|NextDate= |NextYear= }} |
− | |||
===[[Early Spring 2024 Event|Commence! Operation Tatsumaki!]] Update=== | ===[[Early Spring 2024 Event|Commence! Operation Tatsumaki!]] Update=== | ||
Line 20: | Line 19: | ||
* Furniture shop updated. | * Furniture shop updated. | ||
+ | |||
+ | ;🐞Bug: | ||
+ | * On implementation, the new E-4 tags were wrongfully applied on E-3 fleets. | ||
+ | ** This issue has been fixed with a rollback. | ||
==Dev Tweets== | ==Dev Tweets== | ||
Line 31: | Line 34: | ||
[https://twitter.com/KanColle_STAFF/status/1764111900571488699] | [https://twitter.com/KanColle_STAFF/status/1764111900571488699] | ||
[https://twitter.com/KanColle_STAFF/status/1764114214690705731] | [https://twitter.com/KanColle_STAFF/status/1764114214690705731] | ||
+ | [https://twitter.com/KanColle_STAFF/status/1764123735848841380] | ||
+ | [https://twitter.com/KanColle_STAFF/status/1764133465803686271] | ||
+ | [https://twitter.com/KanColle_STAFF/status/1764134866520801759] | ||
+ | [https://twitter.com/KanColle_STAFF/status/1764139791048917427] |
Revision as of 09:15, 3 March 2024
Previous | Current | Next |
---|---|---|
2024 February 29th | 2024 March 3rd | TBA |
Commence! Operation Tatsumaki! Update
Early Spring 2024 Event: Commence! Operation Tatsumaki! |
---|
- Early Spring 2024 Event 2nd Stage Operations have started!
I-41 SSV - E-4 Reward
- Furniture shop updated.
- 🐞Bug
- On implementation, the new E-4 tags were wrongfully applied on E-3 fleets.
- This issue has been fixed with a rollback.