Then how does the client know, on OSI servers, that if Siege Perilous or Mugen is chosen, to only allow one character and have the button disappear once one has been created?
How does the client know that when 5 (or in the case of a 7AE upgrade, 6) characters have been created, to remove that button and not allow any more to be created?
Even in RunUO, once 5 characters (I haven't tried 6, so I don't know if it works correctly) have been created, the button disappears. Why can't 1 character, which is a "supported" number of characters according to you, do the same?
If it's something server-side, in the programming for SP itself, can't it be scripted and/or modified in RunUO do the same thing? And if it's something programmed into the client, shouldn't there be a way to invoke it?
I'm not trying to be argumentative, I'm just trying to understand. I'm not asking the client to do anything it's not programmed to handle, such as is the case with 2, 3, or 4 characters allowed.