You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Painting saving is extremely opaque, and it's currently very easy for somebody to do it incorrectly, have their frame get blown up before round end, have the round admin restarted instead of shuttle called, etc... all of which result in their art being lost forever.
Proposed solutions (choose one or multiple):
Make it save immediately upon being framed
Make it save in non-roundstart frames instead of just the library ones (easy)
Add some kind of dialogue saying "Your painting will be saved!" or "Your painting will not be saved in this frame -- find a different one!" (easier)
Put painting saving directly into the painting window, instead of via framing (hardest, least diagetic)
Add instructions on the painting dialogue on exactly how saving a painting works (easiest, least helpful)
Note that at the moment, the way paintings are saved does serve a useful purpose -- it can limit spam of the same painting to the database over and over. But I trust our players not to abuse the system, the existing method is Bad, and we can always remove paintings from the database afterwards.
Personally, I'm leaning towards 2, 3, and 5.
The text was updated successfully, but these errors were encountered:
Painting saving is extremely opaque, and it's currently very easy for somebody to do it incorrectly, have their frame get blown up before round end, have the round admin restarted instead of shuttle called, etc... all of which result in their art being lost forever.
Proposed solutions (choose one or multiple):
Note that at the moment, the way paintings are saved does serve a useful purpose -- it can limit spam of the same painting to the database over and over. But I trust our players not to abuse the system, the existing method is Bad, and we can always remove paintings from the database afterwards.
Personally, I'm leaning towards 2, 3, and 5.
The text was updated successfully, but these errors were encountered: