Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EncumbranceVal and Value should not be ephemeral by default #1443

Merged
merged 6 commits into from
Feb 18, 2019

Conversation

Mag-nus
Copy link
Member

@Mag-nus Mag-nus commented Feb 14, 2019

EncumbranceVal is now ephemeral only for containers

Value is now ephemeral only for non-creature containers.

This allows items to persist their EncumbranceVal and Value changes to the database.

For containers, they will retain their original (default) value from the database, load that into the ephemeral dictionary and build from there. Those changes will then be lost and reset next time the object is loaded.

EncumbranceVal is now ephemeral only for containers

Value is now ephemeral only for non-creature containers.

This allows items to persist their EncumbranceVal and Value changes to the database.

For containers, they will retain their original (default) value from the database, load that into the ephemeral dictionary and build from there. Those changes will then be lost and reset next time the object is loaded.
ghost
ghost previously approved these changes Feb 14, 2019
@Mag-nus Mag-nus merged commit a9abbb5 into ACEmulator:master Feb 18, 2019
@Mag-nus Mag-nus deleted the EncumbranceValandValue branch February 18, 2019 00:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants