[Zamaroht]

I actually find it a bit hard to explain this bug in words, so I'll use examples instead.

Let's suppose there is a properly compiled filterscript in the filterscripts directory named "FilterScript.amx" (notice the capital letters).

Now, suppose I write the following commands, either in console or ingame using /rcon:

Example 1:
loadfs FilterScript - Works
unloadfs FilterScript - Works

Example 2:
loadfs filterscript - Works
unloadfs filterscript - Works

Example 3:
loadfs FiLTErsCrIpt - Works
unloadfs FiLTErsCrIpt - Works

So far, it's noticable that there isn't any case sensitivity at all. The problem comes up in the following examples:

Example 4:
loadfs filterscript - Works
unloadfs FilterScript - Doesn't Work
unloadfs FiLTErsCrIpt - Doesn't Work
unloadfs filterscript - Works

Example 5:
loadfs FilterScript - Works
unloadfs filterscript - Doesn't Work
unloadfs FiLTErsCrIpt - Doesn't Work
unloadfs FilterScript - Works

That is, even although loadfs can be used either with the correct capitalisation or not, unloadfs has to be called with the exact same string, incluiding correct capitals, than the one used with loadfs, wheter or not it was loaded with the correct capitals.

This makes an irregularity, since loadfs is not case sensitive regarding the file name, but unloadfs is case sensitive regarding loadfs.

It's not a major bug (if it's considered a bug), but it can lead to confusion.