This fix corrected the issue that was reported over a year ago,
The fact that it is not a Harry Potter fix  for your particular situation, which is NOT the same as the originally reported problem
does NOT make the fix pointless.

Besides, since I no longer even use this plugin, I have no "skin in the game" to continue improving it.

razorfishsl

This fix corrected the issue that was reported over a year ago,
The fact that it is not a Harry Potter fix  for your particular situation, which is NOT the same as the originally reported problem
does NOT make the fix pointless.

Besides, since I no longer even use this plugin, I have no "skin in the game" to continue improving it.

No, this isn't a fix. Disabling a portion of the plugin in order to maintain core game mechanics is not a fix. Since you "no longer have skin in the game", why are you even commenting on this?

A fix is defined as fixing the issue in the code that prevents this issue from occuring, not just disabling a part of the plugin / code in order to gain back functionality. Its a design flaw that is bypassed by disabling the code that is flawed, not a fix. So, get you facts straight my dude.

Thankyou once again for reminding my why I  no longer publish fixes.

DJRedNight

No, this isn't a fix. Disabling a portion of the plugin in order to maintain core game mechanics is not a fix. Since you "no longer have skin in the game", why are you even commenting on this?

A fix is defined as fixing the issue in the code that prevents this issue from occuring, not just disabling a part of the plugin / code in order to gain back functionality. Its a design flaw that is bypassed by disabling the code that is flawed, not a fix. So, get you facts straight my dude.

Razor didn't create this plugin. It's broken and the creator is not responding. Instead of writing a paragraph about why Razor needs to do MORE work, why don't you fix the entire plugin for everyone @djrednight