Ravyne That method is the second method I mentioned. I suppose writing it that way is easiest in that it always works the same as server client, or the one. Though will double up on memory and resources that could be shared. Like models and there animations
ApochPiQ I do like that the only problem is animation needs to be available both for client and server. The server may need it for collision detection stuff.
I suppose the completely separate client & server model might be the simplest method and where prediction is needed just inherit for the server. Even if there is some duplication.
Thank you both for the quick reply. I will try your suggestions when I get a chance as I think I am starting to understand it.
The actually structure of the item is much more complicated actually. It's more like this(some stuff i omitted). I will try apply from what you have said. No need to reply unless you think there is imminent disaster I may run into lo. I know there is XMLAttribute but i figure i don't need to expose that as I can use "getAttribute(string searchName);"