If I were to release a custom iw4m.dll modified from Apadayos clan tag mod, that allows users to set their name to whatever the value is in the third line of iw4m.ini , would that be wrong?

NTAuthority put this authentication system in order to prevent impersonation, so releasing a custom iw4m.dll file for changing our In-Game name is forbidden (normally).

 

Anyway, there are many people asking to change their name.

Maybe the best solution would be to purpose a way to change our name using an official dll.

I will now sell this .dll for $20 bucks a pop. But no seriously not a good idea.

These morons shall think before picking a retarded name and then complaining about it.

These morons shall think before picking a retarded name and then complaining about it.

I agree with this too much...

As said before this wouldn't be a good idea to release.

I also believe that this is a bad thing to do

Just wait until there's an official/manageable way to do it

alright, good to know.

you know, it's trivial to impersonate someone as it is, so I don't see why not. Better to have someone with fixed clan tags than someone (in the future) releasing a tool that allows any name.

you know, it's trivial to impersonate someone as it is, so I don't see why not. Better to have someone with fixed clan tags than someone (in the future) releasing a tool that allows any name.

Agreed. I dont get why the clantag was not enabled in the first place.

you know, it's trivial to impersonate someone as it is, so I don't see why not. Better to have someone with fixed clan tags than someone (in the future) releasing a tool that allows any name.

Agreed. I dont get why the clantag was not enabled in the first place.

because editing a .ini file is a horrible 'UI'

you know, it's trivial to impersonate someone as it is, so I don't see why not. Better to have someone with fixed clan tags than someone (in the future) releasing a tool that allows any name.

Agreed. I dont get why the clantag was not enabled in the first place.

because editing a .ini file is a horrible 'UI'

Hm, indeed. Didnt think about that.

you know, it's trivial to impersonate someone as it is, so I don't see why not. Better to have someone with fixed clan tags than someone (in the future) releasing a tool that allows any name.

Agreed. I dont get why the clantag was not enabled in the first place.

because editing a .ini file is a horrible 'UI'

what about something like the alteriw name setter?

you know, it's trivial to impersonate someone as it is, so I don't see why not. Better to have someone with fixed clan tags than someone (in the future) releasing a tool that allows any name.

Agreed. I dont get why the clantag was not enabled in the first place.

because editing a .ini file is a horrible 'UI'

what about something like the alteriw name setter?

Still, I think this is a bad idea.. it would be easy to impersonate staff

no, as in, it configures the dll. one textbox for clan tag, one for name. clan tag gets put into the third line, gets read by the modified dll, and is formatted with the login name, so there's no room for impersonation.

I think that in-game name change should be allowed. Some people use arev client just for the fact that they can easilly change the name on M1 client whenever they feel like or whenever their clan tag changes.

Impersonation could be punishable by a community rule that forbids it. It's not by their name that they identify towards our servers. So, there's not much of a problem if they change their in-game name.

Plus, those who really have an interest in impersonatig someone can preety much get a dll like ToolBox proposed.

Either that, or allowing them to have an option to change their in-game name on the forum's UCP, just like users change password (although that would be heavier on the DB). They could have their forum name and in-game aliases.

I think users should have a limited number of name changes via UCP. For example, 3. Each of their previous aliases should be saved as well.

I think users should have a limited number of name changes via UCP. For example, 3. Each of their previous aliases should be saved as well.

 

This, I support this.