Slig wrote:No particular reason. without server login, eventually server ip, and perhaps map uid and gamemode, i have nothing to look at and eventually test...
That is irrelevant.
The problem is that you unilaterally
changed something in the Dedimania interface without informing plugin authors. XAseco's Dedi plugin works with this list of access URLs:
Code: Select all
For normal operations (retrieving/sending records, player joins/leaves, etc) one of the first five URLs is randomly picked, but for the initial connect, the last URL is used. That's how we agreed earlier this year that I should build the plugin.
So now that you block that last URL from any requests other than the help page
, the error message in the first post is produced during XAseco/Dedimania startup. The same problem may occur in other controllers' plugins that used mine as the starting point.
I don't know what the right solution could be. Personally I prefer not being forced to issue a new XAseco release because you changed the interface.
But I also understand the reason that made you implement that change. Perhaps you can completely block any controller that uses that last URL for normal operations, leaving it only for the initial connects and the help page like before. That forces the author(s) of the abusing controller(s) to fix the stuff on their
end, instead of putting the burden on authors that adhered to the original spec.