Some excellent points as usual melwoc but i think we’re simply going to have to agree to disagree on various points you’ve raised.

I stand by the NOT having to inform players of the dangers for one thing. In my case because i’m using a payware product, it’s not up to me to to make the product secure, but the developer. It’s his responsibilty as a software programmer to ensure this is the case, hence the reason i pay the man. This argument is also solid regarding ANY payware item as we all click on the EULA agreement that comes with said software and keep our fingers crossed it does what it says on the tin. Should this not be the case, then we all have a valid case, so we can all call our respective lawyers and cry foul.

The point i think i’m also trying to make here is that we simply can’t forecast any form of hacker attack due to exploited code. You’ve made the point yourself that if someone is capable enough to exploit code then they will, no matter if it’s an FL related item or the Ministry of Defence mainframe. It therefore follows that even if we did give out warnings, they wouldn’t make a blind bit of difference as the dedicated hacker will simply get past any potential safeguards.

It’s the same with anything that is open to abuse, we take driving lessons so we can drive cars, still doesn’t stop us having accidents. By the same token, we use computers knowing that there are risks involved, common sense simply has to take over at some point, we can’t warn evryone about all associated dangers of using any product, otherwise we’d all starve to death for worrying about the dangers of opening a tin can and wouldn’t go outside for fear of something happening. It’s like putting a sign at the top of a ladder that says stop, we know not to go any further. The same with software you’re not happy using, if you’re concerned about using it, then don’t use it, it really is as simple as that.