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

Areas / Maps with invalid or corrupt entries cause the mud to crash #166

Open
rezalas opened this issue Oct 1, 2022 · 1 comment
Open

Comments

@rezalas
Copy link
Owner

rezalas commented Oct 1, 2022

Ideally if an area has an error or a consistency problem the error would be identified and output in the log, and the area would be skipped. Currently that doesn't occur and instead the server crashes. This is a mix between a bug and an enhancement given that it technically works as intended, but the original intention was flawed.

@Psypher9
Copy link
Collaborator

So we need a way to identify the corruption?

Are there any known corrupted areas?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants