Praise Ehekatl he's back. It has been far too long.
I think there's a pun here I'm not getting... Maybe. In any case, Saara is cute.
It's a reference to the day when Sara K2 was added. Somehow when you Kai 2 Saratoga, the image of a Floating Fortress appear instead of the tight sprite. This was quickly corrected, but some people managed to catch screenshots of the bug. Even at least one person managed to "marry" the Floating Fortress.
It's a reference to the day when Sara K2 was added. Somehow when you Kai 2 Saratoga, the image of a Floating Fortress appear instead of the tight sprite. This was quickly corrected, but some people managed to catch screenshots of the bug. Even at least one person managed to "marry" the Floating Fortress.
It has to do with caching. Images in the game are basically just labelled by a number. To give an example, images #001-500 might all be shipgirls (including different art for kai-ni and such), and then images #501-700 are the abyssals. As new shipgirls or kai-ni artwork is added, they run out of numbers to assign before they go into the abyssal artwork numbers, and since they want to keep them as distinct blocks, they just renumber the abyssals, shoving them up another hundred numbers so that shipgirls have another hundred numbers to work with. (So #001-600 would now be shipgirls and #601-800 are abyssals.)
When Saratoga's Kai-Ni was added, her new art had the number 'slot' that was previously occupied by the floating fortress artwork. (It would be something like #402 in the previous example numbers.) On the server side, if the player's client were to request image #402 to display because they had Saratoga Kai-ni, then it would send the proper image of Saratoga Kai-ni to your browser.
The client browser, however, usually just caches images to prevent the need to download the same data over and over. This means that, without purging the cache or otherwise forcing a refresh of the assets, when the game requests image #402, and it checks and sees that it has an image #402 in its cache, it displays that, because it wasn't told that old #402 (floating fortress art) was now obsolete.
Because of this, so long as players prevented the clearing of their cache (by, for example, never logging out or closing their browser), they could keep Saroating Fortresscchi in their roster and even marry "her".
Also, there was a similar problem with Gangut at first appearing as a Ru-class.
Everyone here is saying the artist is back. But is he TRULY back? I just checked his Pixiv account and he still hasn't updated it. So why is this image posted here and not there?
Everyone here is saying the artist is back. But is he TRULY back? I just checked his Pixiv account and he still hasn't updated it. So why is this image posted here and not there?
Leave a comment