legacy of loathing replica support

[docrostov]

i doubt this is an immediately pressing issue but here is a list of all the iotms that have libram support that may or may not need small ownership condition changes to account for replica availability depending on how mafia supports the path. i suspect most of these will just involve very simple changes, probably?

• grey goose
• crystal ball
• robortender
• terminal
• witchess
• chateau
• deck
• crimbo shrub
• dna lab
• florist friars
• obtuse angel
• bandersnatch

[spaghetti-squash]

This does raise a few questions as to implementation.

• Do we update the have and/or available functions of these?
• Do we provide an orReplica function that we can wrap a billion things in, that essentially says "if you're in LoL and have the replica, return the replica; otherwise, return the original"? How much special architecture will scripts need outside of updating the methods for these resources?
• I thought I had more questions and I'm sure I will in the future

[gausie]

All replicable items get a few accessor functions that account for LoL and we just make sure we use them internally? And expose them for others of course

…

On Fri, 19 May 2023, 20:55 neil, ***@***.***> wrote: This does raise a few questions as to implementation. - Do we update the have and/or available functions of these? - Do we provide an orReplica function that we can wrap a billion things in, that essentially says "if you're in LoL and have the replica, return the replica; otherwise, return the original"? How much special architecture will scripts need *outside* of updating the methods for these resources? - I thought I had more questions and I'm sure I will in the future — Reply to this email directly, view it on GitHub <#481 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABL4LRESWYHZJLNGRVNHOLXG7F4BANCNFSM6AAAAAAYECQMQY> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>