UX improvement: Hunt change dialog raises obscure error

When modifying a hunt in the "Hunt change dialog" and leaving the client limit empty it raises the following obscure error "Unable to parse field v_-client_limit: invalid literal for long() with base 10: ''

Can you change the dialog to catch this situation and provide the user with clear feedback that the client limit should be a numeric value and that 0 represents "no limit".