On my server I play mge_training_v7 with friends- and lately the person who dies will randomly spawn in the middle of the map instead of in the arena they are playing in. Killing yourself usually puts you back in the right arena, but sometimes you'll spawn in the blackness of the map more than once in a row.
I am pretty sure I tried putting a completely fresh install of non-beta MGE on the server, but I still get the glitch. Coincidentally (maybe?) I've also seen this glitch happen in the beta maps on other servers. Can anyone point out the error, be it whatever?
I tried searching the forums before writing this, so please know that before condescendingly replying. Thanks guys.
On my server I play mge_training_v7 with friends- and lately the person who dies will randomly spawn in the middle of the map instead of in the arena they are playing in. Killing yourself usually puts you back in the right arena, but sometimes you'll spawn in the blackness of the map more than once in a row.
I am pretty sure I tried putting a completely fresh install of non-beta MGE on the server, but I still get the glitch. Coincidentally (maybe?) I've also seen this glitch happen in the beta maps on other servers. Can anyone point out the error, be it whatever?
I tried searching the forums before writing this, so please know that before condescendingly replying. Thanks guys.
i just want to say that i have the same problem, on duel_ultimate and other mge maps
lange is aware of the problem but hasn't looked into it yet
i just want to say that i have the same problem, on duel_ultimate and other mge maps
lange is aware of the problem but hasn't looked into it yet
I saw this last week on the TrashedGamers mge server running v7, thought it was just the server acting weird
I saw this last week on the TrashedGamers mge server running v7, thought it was just the server acting weird
I'll see if I can get a sourcemod error log tonight and post it here. Thanks for the response Lange.
I'll see if I can get a sourcemod error log tonight and post it here. Thanks for the response Lange.
Lange: http://pastebin.com/iCV01MPz
thinkLange: http://pastebin.com/iCV01MPz
It appears that you are running SOAP on your server simultaneously, and it's just reporting an error because there aren't spawns for the SOAP plugin when you run MGE maps.
I managed to find this error today in my logs:
L 02/04/2013 - 16:52:54: [mgemod.smx] trace error. victim Valor(18)
L 02/04/2013 - 16:52:56: [mgemod.smx] trace error. victim Juanita Milllos Baby(5)
L 02/04/2013 - 16:52:57: [mgemod.smx] trace error. victim Valor(18)
Already talked with Lange this afternoon about it, and the error disappeared when I re-compiled the plugin against the latest SourceMod snapshot, but the bug is still present. No idea if it's something in SourceMod or the game itself as the "popular" MGE servers still run the original mandatory SM 1.5.0 hg3717/3718 snapshots while my servers run hg3761. Also, I noticed that people playing bball were seemingly unaffected (watched a pair of sollys for like 15 minutes and they were respawning normally from what I saw).
Hopefully we can resolve the problem soon, but until then, clueless people are probably going to blame my beta MGE V8 map or my servers, judging by the amount of "f!@k this broken server" BS I see in my HLStatsX chat logs. http://stats.trashedgamers.org/hlstats.php?mode=chat&game=tf2other&server_id=0&filter=fuck
[quote=think]Lange: http://pastebin.com/iCV01MPz[/quote]
It appears that you are running SOAP on your server simultaneously, and it's just reporting an error because there aren't spawns for the SOAP plugin when you run MGE maps.
I managed to find this error today in my logs:
L 02/04/2013 - 16:52:54: [mgemod.smx] trace error. victim Valor(18)
L 02/04/2013 - 16:52:56: [mgemod.smx] trace error. victim Juanita Milllos Baby(5)
L 02/04/2013 - 16:52:57: [mgemod.smx] trace error. victim Valor(18)
Already talked with Lange this afternoon about it, and the error disappeared when I re-compiled the plugin against the latest SourceMod snapshot, but the bug is still present. No idea if it's something in SourceMod or the game itself as the "popular" MGE servers still run the original mandatory SM 1.5.0 hg3717/3718 snapshots while my servers run hg3761. Also, I noticed that people playing bball were seemingly unaffected (watched a pair of sollys for like 15 minutes and they were respawning normally from what I saw).
Hopefully we can resolve the problem soon, but until then, clueless people are probably going to blame my beta MGE V8 map or my servers, judging by the amount of "f!@k this broken server" BS I see in my HLStatsX chat logs. http://stats.trashedgamers.org/hlstats.php?mode=chat&game=tf2other&server_id=0&filter=fuck
you say you've only seen it happen on the beta maps, could be possible that there's a faulty spawn point carried over from a different map? if you spawn outside of a arena, i'm sure it'd appear as black. this could produce the effect that the spawn happens randomly because MGE cycles through a list of spawn points, so if there's one or two faulty ones, they'd eventually come up.
if I had to guess i'd say because the maps are so similar (? haven't played the beta) Lange or whoever could have just copied over the old spawn config, unknowing that the map creator may have moved some arenas around.
no idea if any of this is correct, purely speculation after reading the thread.
you say you've only seen it happen on the beta maps, could be possible that there's a faulty spawn point carried over from a different map? if you spawn outside of a arena, i'm sure it'd appear as black. this could produce the effect that the spawn happens randomly because MGE cycles through a list of spawn points, so if there's one or two faulty ones, they'd eventually come up.
if I had to guess i'd say because the maps are so similar (? haven't played the beta) Lange or whoever could have just copied over the old spawn config, unknowing that the map creator may have moved some arenas around.
no idea if any of this is correct, purely speculation after reading the thread.
The bug always spawns the player at (0,0,0) and seems to affect once working MGE V7 servers as well (I don't know about RUGC or MGE IT though). I am the developer of the MGE V8 Betas and none of the original arenas were moved or deleted in order to retain compatibility with the original spawns (I want the map to replace V7 some day as I designed it to fix V7 bugs while adding more arenas for people to play on). :)
The bug always spawns the player at (0,0,0) and seems to affect once working MGE V7 servers as well (I don't know about RUGC or MGE IT though). I am the developer of the MGE V8 Betas and none of the original arenas were moved or deleted in order to retain compatibility with the original spawns (I want the map to replace V7 some day as I designed it to fix V7 bugs while adding more arenas for people to play on). :)
0 0 0 gets defaulted to when TeleportEntity is given invalid parameters. it's odd that it doesn't seem to happen on the normal map, though.
0 0 0 gets defaulted to when TeleportEntity is given invalid parameters. it's odd that it doesn't seem to happen on the normal map, though.
Jstn7477It appears that you are running SOAP on your server simultaneously, and it's just reporting an error because there aren't spawns for the SOAP plugin when you run MGE maps.
Hm I thought soap disabled when MGE was running. Wouldn't that theoretically solve it?
[quote=Jstn7477]It appears that you are running SOAP on your server simultaneously, and it's just reporting an error because there aren't spawns for the SOAP plugin when you run MGE maps.[/quote]
Hm I thought soap disabled when MGE was running. Wouldn't that theoretically solve it?
MGE-only servers have the same spawn issue, unrelated to SOAP. You're right about SOAP disabling itself on non-SOAP maps, and that's because the SOAP plugin sets itself into a fail state when no spawns for the given map are available, which is then logged in the SM error logs every time an unsupported map is loaded.
MGE-only servers have the same spawn issue, unrelated to SOAP. You're right about SOAP disabling itself on non-SOAP maps, and that's because the SOAP plugin sets itself into a fail state when no spawns for the given map are available, which is then logged in the SM error logs every time an unsupported map is loaded.
thinkJstn7477It appears that you are running SOAP on your server simultaneously, and it's just reporting an error because there aren't spawns for the SOAP plugin when you run MGE maps.
Hm I thought soap disabled when MGE was running. Wouldn't that theoretically solve it?
every server with SOAP should produce that error when on a map not in the soap spawn config, yeah. shouldn't be the problem afaik.
[quote=think][quote=Jstn7477]It appears that you are running SOAP on your server simultaneously, and it's just reporting an error because there aren't spawns for the SOAP plugin when you run MGE maps.[/quote]
Hm I thought soap disabled when MGE was running. Wouldn't that theoretically solve it?[/quote]
every server with SOAP should produce that error when on a map not in the soap spawn config, yeah. shouldn't be the problem afaik.
So is there anything we can do apart from waiting patiently for a fix?
So is there anything we can do apart from waiting patiently for a fix?
After spying on looking at some popular MGE servers using HLSW, it appears that they are running SourceMod 1.5.0 hg3717/3718. I downgraded the TrashedGamers MGE servers from hg3761 to hg3718 (still had the original package it in my downloads, thankfully) and the problem appears to be resolved from what I see (I only asked one set of people on my Beta server and only one guy responded).
MGE server operators, I recommend NOT UPGRADING SourceMod if you are currently running 1.5.0 hg3717/3718. If you did, here's the complete SourceMod Linux package for hg3718 that I still had (has been purged from the waterfall for some time).
https://dl.dropbox.com/u/53256537/sourcemod-1.5.0-hg3718-linux.tar
Hopefully this helps. I still have an hg3716 Windows build but I'll need to repack it if anyone needs it for Windows SRCDS.
After [s]spying on[/s] looking at some popular MGE servers using HLSW, it appears that they are running SourceMod 1.5.0 hg3717/3718. I downgraded the TrashedGamers MGE servers from hg3761 to hg3718 (still had the original package it in my downloads, thankfully) and the problem appears to be resolved from what I see (I only asked one set of people on my Beta server and only one guy responded).
MGE server operators, I recommend NOT UPGRADING SourceMod if you are currently running 1.5.0 hg3717/3718. If you did, here's the complete SourceMod Linux package for hg3718 that I still had (has been purged from the waterfall for some time).
https://dl.dropbox.com/u/53256537/sourcemod-1.5.0-hg3718-linux.tar
Hopefully this helps. I still have an hg3716 Windows build but I'll need to repack it if anyone needs it for Windows SRCDS.
Just
Jstn7477After spying on looking at some popular MGE servers using HLSW, it appears that they are running SourceMod 1.5.0 hg3717/3718. I downgraded the TrashedGamers MGE servers from hg3761 to hg3718 (still had the original package it in my downloads, thankfully) and the problem appears to be resolved from what I see (I only asked one set of people on my Beta server and only one guy responded).
MGE server operators, I recommend NOT UPGRADING SourceMod if you are currently running 1.5.0 hg3717/3718. If you did, here's the complete SourceMod Linux package for hg3718 that I still had (has been purged from the waterfall for some time).
https://dl.dropbox.com/u/53256537/sourcemod-1.5.0-hg3718-linux.tar
Hopefully this helps. I still have an hg3716 Windows build but I'll need to repack it if anyone needs it for Windows SRCDS.
I'm using windows and i would really appreciate it if you could repack it for me, thanks in advance
Just[quote=Jstn7477]After [s]spying on[/s] looking at some popular MGE servers using HLSW, it appears that they are running SourceMod 1.5.0 hg3717/3718. I downgraded the TrashedGamers MGE servers from hg3761 to hg3718 (still had the original package it in my downloads, thankfully) and the problem appears to be resolved from what I see (I only asked one set of people on my Beta server and only one guy responded).
MGE server operators, I recommend NOT UPGRADING SourceMod if you are currently running 1.5.0 hg3717/3718. If you did, here's the complete SourceMod Linux package for hg3718 that I still had (has been purged from the waterfall for some time).
https://dl.dropbox.com/u/53256537/sourcemod-1.5.0-hg3718-linux.tar
Hopefully this helps. I still have an hg3716 Windows build but I'll need to repack it if anyone needs it for Windows SRCDS.[/quote]
I'm using windows and i would really appreciate it if you could repack it for me, thanks in advance
MightyMeI'm using windows and i would really appreciate it if you could repack it for me, thanks in advance
It's missing a few configuration files that I always delete before upgrading my servers, but it's not like those ever change.
https://dl.dropbox.com/u/53256537/sourcemod-1.5.0-hg3716-windows.zip
I did test hg3771 last week (Alliedmodders added SDKHooks to the SourceMod package) but the problem was really bad. The newest build is hg3784 but I haven't bothered testing it.
[quote=MightyMe]I'm using windows and i would really appreciate it if you could repack it for me, thanks in advance[/quote]
It's missing a few configuration files that I always delete before upgrading my servers, but it's not like those ever change.
https://dl.dropbox.com/u/53256537/sourcemod-1.5.0-hg3716-windows.zip
I did test hg3771 last week (Alliedmodders added SDKHooks to the SourceMod package) but the problem was really bad. The newest build is hg3784 but I haven't bothered testing it.
For some reason, when I kill someone in mge as they spawn, it drops my frames, and it isn't just me because other people I know have the same issue.
^ this isn't even the point of this thread but I thought I could tell this.
For some reason, when I kill someone in mge as they spawn, it drops my frames, and it isn't just me because other people I know have the same issue.
^ this isn't even the point of this thread but I thought I could tell this.
raikuFor some reason, when I kill someone in mge as they spawn, it drops my frames, and it isn't just me because other people I know have the same issue.
^ this isn't even the point of this thread but I thought I could tell this.
Do you own an AMD Radeon HD graphics card (particularly one from the HD 7000 series, which has the most extensive power saving features ever)? If so, you need to download a tool called RadeonPro, add a profile for HL2.exe, click on it, go to the Overdrive tab, enable Overdrive and "Always use highest performance clocks while gaming." MGE as well as the regular game at some points wouldn't put enough load on my graphics card, so it was always changing to lower power states which resulted in my nice, smooth 120FPS VSYNC always becoming a nasty, stuttery 60FPS mess. Share this with your AMD Radeon using friends if it was indeed your issue. :)
[quote=raiku]For some reason, when I kill someone in mge as they spawn, it drops my frames, and it isn't just me because other people I know have the same issue.
^ this isn't even the point of this thread but I thought I could tell this.[/quote]
Do you own an AMD Radeon HD graphics card (particularly one from the HD 7000 series, which has the most extensive power saving features ever)? If so, you need to download a tool called RadeonPro, add a profile for HL2.exe, click on it, go to the Overdrive tab, enable Overdrive and "Always use highest performance clocks while gaming." MGE as well as the regular game at some points wouldn't put enough load on my graphics card, so it was always changing to lower power states which resulted in my nice, smooth 120FPS VSYNC always becoming a nasty, stuttery 60FPS mess. Share this with your AMD Radeon using friends if it was indeed your issue. :)
I've been away from TF2 for a while, but by what I can see there's that problem with the teleport event, not the respawn event. Every player that respawn at MGE do it on origin.. turns out that a few times it doesn't teleport the player to the corresponding arena. I'll try to seek help on the sourcemod forums and contact you if I find something useful.
This should be preferably fixed before the next major update on TF2.
I've been away from TF2 for a while, but by what I can see there's that problem with the teleport event, not the respawn event. Every player that respawn at MGE do it on origin.. turns out that a few times it doesn't teleport the player to the corresponding arena. I'll try to seek help on the sourcemod forums and contact you if I find something useful.
This should be preferably fixed before the next major update on TF2.
Jstn7477raikuFor some reason, when I kill someone in mge as they spawn, it drops my frames, and it isn't just me because other people I know have the same issue.
^ this isn't even the point of this thread but I thought I could tell this.
Do you own an AMD Radeon HD graphics card (particularly one from the HD 7000 series, which has the most extensive power saving features ever)? If so, you need to download a tool called RadeonPro, add a profile for HL2.exe, click on it, go to the Overdrive tab, enable Overdrive and "Always use highest performance clocks while gaming." MGE as well as the regular game at some points wouldn't put enough load on my graphics card, so it was always changing to lower power states which resulted in my nice, smooth 120FPS VSYNC always becoming a nasty, stuttery 60FPS mess. Share this with your AMD Radeon using friends if it was indeed your issue. :)
yes I do, I will try dis out now :)
[quote=Jstn7477][quote=raiku]For some reason, when I kill someone in mge as they spawn, it drops my frames, and it isn't just me because other people I know have the same issue.
^ this isn't even the point of this thread but I thought I could tell this.[/quote]
Do you own an AMD Radeon HD graphics card (particularly one from the HD 7000 series, which has the most extensive power saving features ever)? If so, you need to download a tool called RadeonPro, add a profile for HL2.exe, click on it, go to the Overdrive tab, enable Overdrive and "Always use highest performance clocks while gaming." MGE as well as the regular game at some points wouldn't put enough load on my graphics card, so it was always changing to lower power states which resulted in my nice, smooth 120FPS VSYNC always becoming a nasty, stuttery 60FPS mess. Share this with your AMD Radeon using friends if it was indeed your issue. :)[/quote]
yes I do, I will try dis out now :)
I had v7 and now i installed v8. Spawns still broken. Will latest sourcemod will fix it? Does anyone reported the bug there?
I had v7 and now i installed v8. Spawns still broken. Will latest sourcemod will fix it? Does anyone reported the bug there?
[quote=Jstn7477]http://stats.trashedgamers.org/hlstats.php?mode=chat&game=tf2other&server_id=0&filter=fuck[/quote]
"killing me while im takkin a shit, FUCK u man"
Jstn7477MightyMeI'm using windows and i would really appreciate it if you could repack it for me, thanks in advance
It's missing a few configuration files that I always delete before upgrading my servers, but it's not like those ever change.
https://dl.dropbox.com/u/53256537/sourcemod-1.5.0-hg3716-windows.zip
I did test hg3771 last week (Alliedmodders added SDKHooks to the SourceMod package) but the problem was really bad. The newest build is hg3784 but I haven't bothered testing it.
It's still happening to me after I downgraded the server. Nor really sure what's going on.
EDIT:
I keep getting this in console whenever it happens:
Ignoring unreasonable position (1755.262695,-15.696391,-16388.023438) from vphysics! (entity class C_PhysPropClientside)
[quote=Jstn7477][quote=MightyMe]I'm using windows and i would really appreciate it if you could repack it for me, thanks in advance[/quote]
It's missing a few configuration files that I always delete before upgrading my servers, but it's not like those ever change.
https://dl.dropbox.com/u/53256537/sourcemod-1.5.0-hg3716-windows.zip
I did test hg3771 last week (Alliedmodders added SDKHooks to the SourceMod package) but the problem was really bad. The newest build is hg3784 but I haven't bothered testing it.[/quote]
It's still happening to me after I downgraded the server. Nor really sure what's going on.
EDIT:
I keep getting this in console whenever it happens:
Ignoring unreasonable position (1755.262695,-15.696391,-16388.023438) from vphysics! (entity class C_PhysPropClientside)
slosprint It's still happening to me after I downgraded the server. Nor really sure what's going on.
EDIT:
I keep getting this in console whenever it happens:
Ignoring unreasonable position (1755.262695,-15.696391,-16388.023438) from vphysics! (entity class C_PhysPropClientside)
Linux or Windows server? Haven't messed with my servers for a few weeks so I don't know if a game update was a nail in the coffin or if it is a SourceMod problem that wasn't present in earlier Linux builds. CPrice is still working on the new MGE plugin but I do not believe it is close to being completed yet.
[quote=slosprint] It's still happening to me after I downgraded the server. Nor really sure what's going on.
EDIT:
I keep getting this in console whenever it happens:
Ignoring unreasonable position (1755.262695,-15.696391,-16388.023438) from vphysics! (entity class C_PhysPropClientside)
[/quote]
Linux or Windows server? Haven't messed with my servers for a few weeks so I don't know if a game update was a nail in the coffin or if it is a SourceMod problem that wasn't present in earlier Linux builds. CPrice is still working on the new MGE plugin but I do not believe it is close to being completed yet.
I'm still convinced that its a sourcemod problem and not a mge mod problem, since its happening on v7 too, it doesn't make much sense for a bug like this to randomly pop up a year after the code has been working completely fine. Also I've never seen this bug in my own server or any of the popular mge servers running older versions of sourcemod. If anyone has any leads as to what might be causing this or any info, feel free to add me on steam and msg me.
#21 that could come from the accuracy stats part of mge, which is being removed in the next version, which should fix any frame drops on player deaths.
#27 that "error" can come from server lag and other broken things valve put in the game, if you could double check and make absolutely sure that its ONLY happening when players get bad spawns that'd be great, otherwise you just might have not downgraded properly?
The only other question I have is, does this happen on bball arenas to? or only on non bball arenas?
I'm still convinced that its a sourcemod problem and not a mge mod problem, since its happening on v7 too, it doesn't make much sense for a bug like this to randomly pop up a year after the code has been working completely fine. Also I've never seen this bug in my own server or any of the popular mge servers running older versions of sourcemod. If anyone has any leads as to what might be causing this or any info, feel free to add me on steam and msg me.
#21 that could come from the accuracy stats part of mge, which is being removed in the next version, which should fix any frame drops on player deaths.
#27 that "error" can come from server lag and other broken things valve put in the game, if you could double check and make absolutely sure that its ONLY happening when players get bad spawns that'd be great, otherwise you just might have not downgraded properly?
The only other question I have is, does this happen on bball arenas to? or only on non bball arenas?
CpriceI'm still convinced that its a sourcemod problem and not a mge mod problem, since its happening on v7 too, it doesn't make much sense for a bug like this to randomly pop up a year after the code has been working completely fine. Also I've never seen this bug in my own server or any of the popular mge servers running older versions of sourcemod. If anyone has any leads as to what might be causing this or any info, feel free to add me on steam and msg me.
#21 that could come from the accuracy stats part of mge, which is being removed in the next version, which should fix any frame drops on player deaths.
#27 that "error" can come from server lag and other broken things valve put in the game, if you could double check and make absolutely sure that its ONLY happening when players get bad spawns that'd be great, otherwise you just might have not downgraded properly?
The only other question I have is, does this happen on bball arenas to? or only on non bball arenas?
I'm pretty sure bball had no issues when I tried a later build of SourceMod. I watched a pair of players use that arena for maybe 15 minutes without issue while everyone else was suiciding a million other times.
[quote=Cprice]I'm still convinced that its a sourcemod problem and not a mge mod problem, since its happening on v7 too, it doesn't make much sense for a bug like this to randomly pop up a year after the code has been working completely fine. Also I've never seen this bug in my own server or any of the popular mge servers running older versions of sourcemod. If anyone has any leads as to what might be causing this or any info, feel free to add me on steam and msg me.
#21 that could come from the accuracy stats part of mge, which is being removed in the next version, which should fix any frame drops on player deaths.
#27 that "error" can come from server lag and other broken things valve put in the game, if you could double check and make absolutely sure that its ONLY happening when players get bad spawns that'd be great, otherwise you just might have not downgraded properly?
The only other question I have is, does this happen on bball arenas to? or only on non bball arenas?[/quote]
I'm pretty sure bball had no issues when I tried a later build of SourceMod. I watched a pair of players use that arena for maybe 15 minutes without issue while everyone else was suiciding a million other times.
Jstn7477CpriceI'm still convinced that its a sourcemod problem and not a mge mod problem, since its happening on v7 too, it doesn't make much sense for a bug like this to randomly pop up a year after the code has been working completely fine. Also I've never seen this bug in my own server or any of the popular mge servers running older versions of sourcemod. If anyone has any leads as to what might be causing this or any info, feel free to add me on steam and msg me.
#21 that could come from the accuracy stats part of mge, which is being removed in the next version, which should fix any frame drops on player deaths.
#27 that "error" can come from server lag and other broken things valve put in the game, if you could double check and make absolutely sure that its ONLY happening when players get bad spawns that'd be great, otherwise you just might have not downgraded properly?
The only other question I have is, does this happen on bball arenas to? or only on non bball arenas?
I'm pretty sure bball had no issues when I tried a later build of SourceMod. I watched a pair of players use that arena for maybe 15 minutes without issue while everyone else was suiciding a million other times.
I don't mge very much but I can attest to that being accurate; I've never had this glitch with bball and it happens to me on average of 3 times a game every other arena.
[quote=Jstn7477][quote=Cprice]I'm still convinced that its a sourcemod problem and not a mge mod problem, since its happening on v7 too, it doesn't make much sense for a bug like this to randomly pop up a year after the code has been working completely fine. Also I've never seen this bug in my own server or any of the popular mge servers running older versions of sourcemod. If anyone has any leads as to what might be causing this or any info, feel free to add me on steam and msg me.
#21 that could come from the accuracy stats part of mge, which is being removed in the next version, which should fix any frame drops on player deaths.
#27 that "error" can come from server lag and other broken things valve put in the game, if you could double check and make absolutely sure that its ONLY happening when players get bad spawns that'd be great, otherwise you just might have not downgraded properly?
The only other question I have is, does this happen on bball arenas to? or only on non bball arenas?[/quote]
I'm pretty sure bball had no issues when I tried a later build of SourceMod. I watched a pair of players use that arena for maybe 15 minutes without issue while everyone else was suiciding a million other times.[/quote]
I don't mge very much but I can attest to that being accurate; I've never had this glitch with bball and it happens to me on average of 3 times a game every other arena.
Bug fixed. I have no idea how this didn't surface until just recently but I finally found the source of the problem and implemented a fix.
https://www.dropbox.com/s/k1lcxyz6zyy1mgu/mgemod.smx
Download that plugin file and replace your current mgemod.smx with that one. Let me know if anyone continues to get this issue after installing that version.
Bug fixed. I have no idea how this didn't surface until just recently but I finally found the source of the problem and implemented a fix.
https://www.dropbox.com/s/k1lcxyz6zyy1mgu/mgemod.smx
Download that plugin file and replace your current mgemod.smx with that one. Let me know if anyone continues to get this issue after installing that version.
CpriceBug fixed. I have no idea how this didn't surface until just recently but I finally found the source of the problem and implemented a fix.
https://www.dropbox.com/s/k1lcxyz6zyy1mgu/mgemod.smx
Download that plugin file and replace your current mgemod.smx with that one. Let me know if anyone continues to get this issue after installing that version.
Thanks, will try it on my servers.
[quote=Cprice]Bug fixed. I have no idea how this didn't surface until just recently but I finally found the source of the problem and implemented a fix.
https://www.dropbox.com/s/k1lcxyz6zyy1mgu/mgemod.smx
Download that plugin file and replace your current mgemod.smx with that one. Let me know if anyone continues to get this issue after installing that version.[/quote]
Thanks, will try it on my servers.