By “Client Override” i mean a folder within the client that is not affected by any update, and that client accesses first.
Such a thing would be within in the client folder (so client > client override).
So for example, i add into it GFX > Sprites > Sprite635.sprite, in which sprite635 is the old hydreigon sprite. So then when i see a hydreigon, the sprite shown will be the “old” (the one in the override file) and not the “current” (the one in the actual unmodified client). This is what i mean by accessed first - so things within in are used instead of the stuff in the client folder.
Everytime an update package comes along, files are updated, added (in the case of stuff being taken out) and/or removed in some cases. Updates also mean client modifications, as such as the above, can be overwritten when we dont want them to be. Such a folder should not be affected by an update, allowing modifications to remain after updates without having to remodify stuff all over again which can get tedious.
This will allow client modifications (mods as most commonly abreviated) to be easily implemented by a player to their own (or others) clients.
Meaning some accessability issues (e.g in respect to some of the gfx being hard on the eyes to people with eye problems amongst more issues that apply to a minority of people) can be sorted easily - via mods.
As well, the ability to change the client to peoples desires/preferences (that hydreigon sprite example is a preference) will be more easily done and supported.
As a note, this would not mean copying the whole pmu client folder into it, the idea is to work only for a given path (GFX > Sprites > Sprite635.sprite would only override the Sprite635.sprite file for example, all other sprites/gfx etc would not be affected.)
(Sorry if it isn’t all that clear, i found it hard to explain it.)