Closed Commandcracker closed 2 days ago
The only reason we use serde_inline_default
is to have default values for config fields we can't parse. I tested your changes and removed a random config value. It gave me an error Couldn't parse config at "configuration.toml". Reason: missing field
hardcore. This is is proberbly caused by an Config update, Just delete the old Config and start Pumpkin again
The only reason we use
serde_inline_default
is to have default values for config fields we can't parse. I tested your changes and removed a random config value. It gave me an errorCouldn't parse config at "configuration.toml". Reason: missing field
hardcore. This is is proberbly caused by an Config update, Just delete the old Config and start Pumpkin again
Now it should work
Just tested again. Works fine now and looks much better. Thanks @Commandcracker :D
Description
Most changes are because serde_inline_default is no longer needed, see here
Testing
ran diff on booth configs to see if anything changed.
Checklist
Things need to be done before this Pull Request can be merged.
cargo fmt
cargo clippy