I've observed what seems to be kind of a bug in extDB2.
I've configured the whitelist kicking and created an appropriate database structure. According to the logs, the query is being executed and returns the correct result (True when whitelisted, False when not).
However, when the server is starting, the player isn't kicked up until the point where he reconnects, negating the whole point of a whitelist. So when connecting before extDB has logged in (which happens very late), the server is essentially not whitelisted at all.
Furthermore, when entering garbage as the whitelist query, the query fails but still doesn't kick the player even when the corresponding setting "kick on query fail" is set to "true".
I've observed what seems to be kind of a bug in extDB2.
I've configured the whitelist kicking and created an appropriate database structure. According to the logs, the query is being executed and returns the correct result (True when whitelisted, False when not).
However, when the server is starting, the player isn't kicked up until the point where he reconnects, negating the whole point of a whitelist. So when connecting before extDB has logged in (which happens very late), the server is essentially not whitelisted at all.
Furthermore, when entering garbage as the whitelist query, the query fails but still doesn't kick the player even when the corresponding setting "kick on query fail" is set to "true".