Quote:
Originally Posted by Ellie
Don't sweat it. I know you probably haven't worked on his plugin extensively in a while. Not to mention that the plugin has a ton of code (the is the "largest" plugin we use on our servers). The timer I'm referring to is one that is in the code that controls how frequently that disabled message appears, such as "CreateTimer(60.0, ect....");".
|
Yes, I have not done anything for the plugin since the last plugin update. I don't see any reason why I wouldn't get interested in developing the plugin, once I have an idea of what to develop. There is a timer that does the
plugin disabled message. It probably has a hardcoded time value. Changing that value and compiling the plugin you can change the frequency. If it's not a configurable value, I probably should set it as one.
Quote:
Originally Posted by Ellie
I figured out the issue we had with L4D2. It's very similar to what was posted on this post. Basically, if a server has this plugin running and it can't connect to the database, the server will crash with no errors at all, not even in the logs. You should mention this on the first post to save people looking for errors that won't be logged. Initially I thought maybe it was a conflict with another plugin. So I tried testing this with just the core SM plugins and nothing else installed plugin wise. Still crashes. So then I checked ALL the settings dealing with this plugin, and in our case it turned out the IP needed for remote database access was now different from the game server IP. It was not like this before when the plugin was previously working, since we used to have the same IP as the server as an access host for the database, which had to be removed as an access host even though the server IP did not change. I dunno wtf our GSP did that for. But once I found the alternate IP (which at first glance doesn't even look like an IP) I added it as an access host for the database and the servers can now start the maps.
|
I'll try to simulate the issue of not being able to connect the db and see if there is something I can do to make it easily solvable by the plugin users. Thanks for opening your case.
Quote:
Originally Posted by g Void
The commands such mysql_query, mysql_fetch_array and such are giving a warning (saying it won't be supported for long). It's no biggie, it is easy to change to, say mysqli_query, mysql_fetch_assoc etc. But it still gives off some inconsistencies. I just thought there was a up to date version of this already done.
|
The web site is not in the best shape. I do not have much experience in PHP, so it is likely to have problems. However, if you feel you can contribute to make things better and have the knowledge, please head over to GitHub (link at first post) and start there. The webstats have gone some further at Git, but the layout is unpolished. If someone with a little will and skills from web design could help me out a bit... I would be very happy!
__________________