Client minimum for dynamic world sizes does not match actual value possibly accepted by server
Closed this issue · 0 comments
monoclex commented
The code for world sizes accepts worlds from 3 -> 50. The code for world sizes on the client only validates from 5 to 50. These two should be able to be kept in sync, perhaps by using the validation features of computed-types
and displaying the appropriate error when a size does not fall within range or something similar. Perhaps there is a way to display a custom error message, so that no code has to be duplicated and that all validation logic can be entirely computed-types related.