Quote:
Originally Posted by Tyhm
Piffle, I could care about internal security (the relative risk of people who already have access to RC), but I shan't. It's not the sort of thing that seems to merit having its own script to repair.
|
Then what are you caring about?
I requested protected variables. Kinda like making bank flags protected variables so staff members with any kind of script access (eg. level, weapon etc.) couldn't access the flags and change them from another object. Could also be like making a mud library into a DB with protected vars so weapons / items can't be changed without using the actual DB itself - thus logged. I don't see why we can't have it?
Quote:
Originally Posted by Tyhm
Maybe if we just had more control over public and private variables...
|
We currently have no control of such things - they don't exist for developers.
Quote:
Originally Posted by Tyhm
I don't know if I like the idea of classes being downloaded onto the client so they can see "Huh, whatever variable z01 is, that's the password...so I'll just say that, and it'll match it up...oh, I see, they have it scripted so I have to say the password backwards...well, I say that then."
|
No idea where that thought came from. In anycase, protected vars would be wasted clientside anyways. All important information should be held serverside.