ID:1671586
 
Resolved
world/IsBanned() now takes a new argument indicating the connection type.
Applies to:DM Language
Status: Resolved (507.1255)

This issue has been resolved.
Currently, the only way to disconnect users that are using specific forms of connection is to do so once the user has actually joined the server.

Generally, you want to waste as little resources as possible on users who shouldn't be able to connect, which is where world/IsBanned() comes in handy. IsBanned is called before resources are even downloaded.

We can currently limit guests, telnet users, and guests via the web client by checking the key, but there's no real way to limit connection types.

It would make sense for a connection arg in the IsBanned function, which would have the same value as the future client's connection var.

There's currently no way for programmers to toggle support of the webclient at a low level, and people hosting via the beta may not be aware of the webclient toggle for DD.

This is a very good idea. I believe it may well be feasible, and if so I'll try to get it into 507.
Lummox JR resolved issue with message:
world/IsBanned() now takes a new argument indicating the connection type.
If we're using world.IsBanned() to limit connection types, it doesn't make sense for the denial message to be always preceded by "Banned by host."

Maybe it would even be more fitting to rename world.IsBanned() with a new proc, such as world.Enter().