White-Tiger,
1) It has to be rewritten to NOT be a protocol anymore, but classic plugin
2) If you strip all Xfire stuff and let only game detection and change status to work, it will be a different plugin. It has to have a new name and other stuff.
3) Plugin updater can do replace (let say we set rule to replace xfire.dll with e.g. gamedetector.dll), which will delete old plugin and install new one. IF we want to put only gamedetector plugin to all those who had XFire (which doesn't makes sense for me, because you can't tell whether he used it for Xfire or for Game detection), we can.
4) New plugin can be compatible with games settings from XFire (e.g. you can let user just rename the settings branch, or provide import of games settings at first run or something).
But it's definitely not needed, because do you know how many users who use VI uploading use XFire?
TWO. Just me and (probably) you. It's 1.5 % regarding all users with VI, but I guess the number is waaaay smaller. (We should prepare better stats btw :-) )
You can take game detection (which was only a tiny part of whole sources), but
it HAS to be different plugin with different name and with most things written from scratch.