ID:135543
 
I think a really nice feature for developers would be to add a built-in function called let's say, find_keys(). Pretty much, it'll find all keys that belongs to a client, or is associated with them. It'd really help for only allowing ONE character per pupil in games.
Goku72 wrote:
I think a really nice feature for developers would be to add a built-in function called let's say, find_keys(). Pretty much, it'll find all keys that belongs to a client, or is associated with them. It'd really help for only allowing ONE character per pupil in games.

Well, you could just check the players' ip addresses.
I have to strongly disagree here, as Jon said all you have to do is check the client's address.

There are two main reasons for disagreement here. First, just because two keys are on the same computer that does not mean they belong to the same person. My sister used to use my computer and she had a Byond key registered for a while, and I have some friends who all use the same computer (4 people use the computer, thus 4 different Byond keys all belonging to different people). I am sure plenty of other people share their computers similarly. Second, some of us like to keep our others unknown. I have a key that I use when I don't want to be bothered by everyone who knows my main key. I know of others who do this as well.
In response to Jon88
Well, problem with that is ip addresses change.
In response to Goku72
Oh, so you only want one key per computer ANY time? I thought you meant 2 keys at the same time. Well, I have to agree with Loduwijk here. It's kind of, well, not smart. It would lead to family members using the same key, and then things like "My BROTHER DIDX0R IT!!11!".

Not to mention, if made, it wouldn't be flawless. How do you know if a key is associated with another one? If I go to a friends house with BYOND and use his computer, my key becomes associated with his, doesn't it?

If you really want to do it, you could save something to the clients PC with some weird file name, random for each player. Add that filename to a list. When new players join, see if any of the filenames in the list exist [using fexist()] and if it does, kick/ban them. That works untill they realize it's the file not allowing them to play...so just tell them it's a savefile.
The problem I see with this is it gives people a tool to help get around the system. You could use it to ban people, but I might use it try and find a way to get around having my keys asociated. After I've got that figured out I don't have to worry about any bans I may get.