Quote:
Originally Posted by GoTTi
nah not getting turned around on me, no way.
the idea is to have the uninstall information placed on the mods when moved to the graveyard. either removal of the plugin or whatever. staff can do it or dont, its the suggestion i submitted to this vb.org feedback forum. take it or not. im not gunna argue and debate it anymore, aint getting anywhere obviously. its not just my lost when it happens so whatever.
just close the thread already or delete it, useless.
|
You really seem to be missing the point here. Short of having a time machine to go back in time and download the modifications before they're deleted by the thread starters, how are the staff supposed to do that?
That's obviously excluding the time constraints, which, quite frankly, shouldn't be a staff duty anyway. I'd rather they were moderating the site, not spending hours writing instructions for someone else's modification.
You
should take this up with the coders who don't leave uninstallation instructions, not the staff. It's the coder's modification, the coder's decision to delete their mods (barring security issues, obviously) and the coder's failure to leave uninstall instructions.
Aside from providing this (free) resource, Jelsoft and the staff aren't responsible for other people's work and to be frank, that's the way it should be.
If you really want uninstall instructions or backed up modifications, you have both your server and your hard drive. There's no real reason why both should fail and there's also no excuse not to use every opportunity to backup everything, especially as you seem to have such a big problem with this. I have modifications spread across 2 hard drives and my server. There's no reason why you, or anyone else, can't do the same.