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
Currently SBInfo is not serialized, but information about it is used to serialize BaseVendor. We should strive keep serialization standardized by rewriting BaseVendor serialization.
SBInfo is copied for every vendor even though 99%+ use a static list. This means as a vendor is spawned, changes maps, barkeep title is changed, etc, the list is recreated which has ramifications for serialization.
Let's architect a way to maintain the serialization of SBInfo that have doubled on a vendor, but avoids additional allocations for SBInfo per vendor where possible. It looks like the double factor is the only thing serialized for vendors.
The text was updated successfully, but these errors were encountered:
Let's architect a way to maintain the serialization of SBInfo that have doubled on a vendor, but avoids additional allocations for SBInfo per vendor where possible. It looks like the double factor is the only thing serialized for vendors.
The text was updated successfully, but these errors were encountered: