Afraid so, it's a software limitation. They use a boolean field in the database to track the number of namechanges... so it can only be a 0 or a 1. Sorry.
Yup, the transaction isn't comitted to the database straight away, it only updates when you are next active, which may explain why in your case it may have appeared you may have had more namechanges, It's definately committed now though.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.