Phantom said:
PlayerMobile is already a child class, of the Mobile class, which was done awhile ago. The problem with the above idea is the fact, there are several issues with a conversion script because of some issues within the PlayerMobile.
Plus the fact even if this is done, if there is an issue in the child class, it still will cause problems. So really in the end its easier to deal with PlayerMobile then it is to deal with yet another child class.
LoL - PlayerMobile is a child class... obviously.
A conversion script would need to be provided, but it would only have to account for the standard PlayerMobile. Anyone who has edited the PlayerMobile will have to do it again in 2.0, so they can just tweak the conversion script instead. Or they can continue to use the PlayerMobile script. I have used a derived PlayerMobile for years and have never had a problem with distro scripts referring to PlayerMobile while mine refer to BritanniaMobile.
Lets see, if there is an issue with a script it will cause problems... again obviously. The idea here is that scripts actually be tested before they are submitted or put on a production shard.
And finally how is working with a 2865 line distro script easier than working with a short script script that contains only what you have added to it? I have multiple custom features added to my Players but my PlayerMobile has been the default distro script since beta 26 or so.
It is called PolyMorphism and is used throughout RunUO. It is not hard at all.