Loadfs and Unloadfs: Weird case sensibility management - Printable Version

+- SA-MP Forums Archive (https://sampforum.blast.hk)
+-- Forum: SA-MP (https://sampforum.blast.hk/forumdisplay.php?fid=3)
+--- Forum: Bug Reports (https://sampforum.blast.hk/forumdisplay.php?fid=20)
+--- Thread: Loadfs and Unloadfs: Weird case sensibility management (/showthread.php?tid=116696)

---

Loadfs and Unloadfs: Weird case sensibility management - Zamaroht - 29.12.2009

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.

---

Re: Loadfs and Unloadfs: Weird case sensibility management - ev0lution - 29.12.2009

I had this problem in 0.2X as well.

It's because loadfs doesn't care about case-sensitivity when loading a file, however in memory it's loaded as whatever you typed after "loadfs".

It's a bigger problem than what you showed, loadfs will load the script as many times as typed with different capitalisation.

For example:
loadfs filterscript
loadfs Filterscript
loadfs FIlterscript
loadfs FILterscript
loadfs FILTerscript

Now you have 5 scripts loaded, all the same script from filterscript.amx.
Depending on the script, it can cause the server/script to malfunction because of the duplicate items in each loaded script.



unloadfs will now be able to unload all of them, but no other case variations of them.

For example:
unloadfs filterscript
unloadfs Filterscript
unloadfs FIlterscript
unloadfs FILterscript
unloadfs FILTerscript

Those will all work, however any other case variations will not.


For a slightly better example, I quickly checked this on a SA-MP 0.3R4 Windows server with the "base.amx" filterscript that comes with the server.
I can assure you I only had "base.amx", all lowercase, in my filterscripts directory.

---