SnuggleSnail wrote:Daily reminder that once upon a time flower menus were client side. This shit was an active decision.
My first impulse was to bully you for living in Australia, but the issue basically affects everyone not living in Europe, and if issue is caused entirely by an arbitrary decision by the devs, then this should be called out with minimal cacophony.
Analogy: you sit at restaurant table. Client side flowermenu means you have the menu on the table and just call the waiter whenever. Server side flowermenu, you have to always ask the waiter for a new on-demand menu.
Assuming I understood this correctly.
Got me thinking of the difference between a client/Server side flower menu. I'm assuming client side flower menu requires client to know at all times which flower menu options are available. Maybe this was the concern/reason for making them server side? Ideally there would be some indication on objects that they can be clicked anyway (like Natural Wonders and Bee Hives, for example.) If you have some exceptions to this where it is absolutely necessary that only by specifically pinign the server you get the correct menu, maybe add it through some additional layer that can only apply to those things?