Editing The London Horticultural Show (historical)
From Fallen London Wiki (Staging)
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 46: | Line 46: | ||
On the Discord, it was revealed that the horticulture activity was essentially a facade, with most of the options and flowers not actually implemented, and that it might or might not return in future<ref>[https://discord.com/channels/606151996663267338/770266641762091079/1135938559879151696 Discord] "The horticulture wheel is gone but depending on the response to it we may bring it back as its own thing in the future." - Bruno (FBG), 14:14 UTC</ref>. The entire Horticulture Show was just there to allow the event to be advertised without spoiling the surprise inherent in a surprise attack<ref>[https://discord.com/channels/606151996663267338/770266641762091079/1135940264230392001 Discord] "The horticulture show really exists to preserve the shock and disorientation of the initial invasion – it's meant to sell that moment of "wait, what" while still allowing us to talk about the event in advance of it starting. Obviously you expect *something* to happen, but this year it's a sudden external threat so it wanted that bit of artifice." - Bruno (FBG), 14:21 UTC</ref>. Also revealed was the real event poster, shown above. | On the Discord, it was revealed that the horticulture activity was essentially a facade, with most of the options and flowers not actually implemented, and that it might or might not return in future<ref>[https://discord.com/channels/606151996663267338/770266641762091079/1135938559879151696 Discord] "The horticulture wheel is gone but depending on the response to it we may bring it back as its own thing in the future." - Bruno (FBG), 14:14 UTC</ref>. The entire Horticulture Show was just there to allow the event to be advertised without spoiling the surprise inherent in a surprise attack<ref>[https://discord.com/channels/606151996663267338/770266641762091079/1135940264230392001 Discord] "The horticulture show really exists to preserve the shock and disorientation of the initial invasion – it's meant to sell that moment of "wait, what" while still allowing us to talk about the event in advance of it starting. Obviously you expect *something* to happen, but this year it's a sudden external threat so it wanted that bit of artifice." - Bruno (FBG), 14:21 UTC</ref>. Also revealed was the real event poster, shown above. | ||
− | At 21:44, the Admiralty reached 10%, changing the reward for appealing to them from {{IL|Memory of Distant Shores}} to {{IL|Service to London}} and giving new text<ref>[https://discord.com/channels/606151996663267338/770266641762091079/1136051847501721621 Discord] "NEW TEXT" - THE SUN IS A GIRLBOSS, 21:44 UTC</ref>. A minute or so later, Jenny also crossed the 10% mark and switched to Service<ref>[https://discord.com/channels/606151996663267338/770266641762091079/1136052060383625226 Discord] "Go Jenny!!" - hlodvig, 21:45 | + | At 21:44, the Admiralty reached 10%, changing the reward for appealing to them from {{IL|Memory of Distant Shores}} to {{IL|Service to London}} and giving new text<ref>[https://discord.com/channels/606151996663267338/770266641762091079/1136051847501721621 Discord] "NEW TEXT" - THE SUN IS A GIRLBOSS, 21:44 UTC</ref>. A minute or so later, Jenny also crossed the 10% mark and switched to Service<ref>[https://discord.com/channels/606151996663267338/770266641762091079/1136052060383625226 Discord] "Go Jenny!!" - hlodvig, 21:45 UTC</ref>. |
Throughout this time, the game had a number of performance issues, with many people unable to login. This was due to the actual underlying database being at maximum capacity for input/output. | Throughout this time, the game had a number of performance issues, with many people unable to login. This was due to the actual underlying database being at maximum capacity for input/output. |