[Ellie]

Originally Posted by Ellie This is happening in L4D2 with the 1.6.6 version that was re-upped. Not only that, it seems to be loading multiple flash videos at once causing any player on the server to lag to the point their game just stops. Can people still use version 2.1.1 if they have it, or it won't work? BTW, where can I view an explanation of all that's mentioned in the MOTDGD preferences page?

I decided to give this plugin another go, but this time with L4D1. The video ads will play but as soon as it's over and a player closes the motd window, the game crashes every single time. Are there any other versions I can try?

Does anyone currently have this working with l4d2? If you do, can you post or pm me the version you are using?

[Happy DODs player]

Servers are located in France. Income was around 3$/day last month and dropped to around 0.6$/day this month.

Is your income getting higher again. ? h3Bus.

My n is stable also 3$ till 4 $ a day atm. Weekends maybe 4$ till 5$

[h3bus]

Yes income are improving this month. Still half not to the level it reached during august but it's better than nothing!

[Mike4Told]

I'm having problems with this plugin. Though my other servers work nicely. However, I am running it on a trade map. Which doesn't change maps. I have it set to open the MOTDGD Ads upon death. With the timer on as well; seen below:

// Whether eligible players are shown MOTDgd every X minutes during the game, 0 is disabled, minimum 20 minutes
// - 
// Default: "20"
sm_motdgd_review_minutes "20"

// Whether eligible players are shown MOTDgd after [review_minutes] have passed, 0 is on death, 1 is on round start (default)
// -
// Default: "1"
sm_motdgd_review_mode "0"

After the player's death the MOTDgd ad does not show, even after the timer has expired.

Any ideas?

[medic917]

ya it doesn't work for me either in tf2.

[Ixel]

Version 2.2.0 beta is now available for testing. I've ran it on my own server for some time and it seems fine, maybe certain functionality isn't fully tested but I'm pretty sure everything's good this time. Please provide feedback when you can!

[lionheart1066]

Anyone getting this with 2.2.0?

L 10/09/2014 - 01:14:21: [SM] Native "Steam_GetHTTPResponseBodyData" reported: HTTPRequestHandle invalid, not yet sent or invalid buffer size
L 10/09/2014 - 01:14:21: [SM] Displaying call stack trace for plugin "motdgd_adverts.smx":
L 10/09/2014 - 01:14:21: [SM]   [0]  Line 319, D:\SRCDS\Valve\CMDServer\addons\sourcemodclean\scripting\include\EasyHTTP.inc::EasyHTTP_SteamToolsComplete()

[Ixel]

Originally Posted by lionheart1066 Anyone getting this with 2.2.0? L 10/09/2014 - 01:14:21: [SM] Native "Steam_GetHTTPResponseBodyData" reported: HTTPRequestHandle invalid, not yet sent or invalid buffer size L 10/09/2014 - 01:14:21: [SM] Displaying call stack trace for plugin "motdgd_adverts.smx": L 10/09/2014 - 01:14:21: [SM] [0] Line 319, D:\SRCDS\Valve\CMDServer\addons\sourcemodclean\scripting\include\EasyHTTP.inc::EasyHTTP_SteamToolsComplete()

It appears to be an issue with EasyHTTP and SteamTools. I'm presently looking into it (testing with SteamTools instead, as I'm using cURL here) and will provide an update as soon as possible. This will only impact the in-game chat advertisements (if any are available in your server's region). The rest of the plugin will run as normal.

[lionheart1066]

Oh and there's this error as well

L 10/09/2014 - 02:54:29: [SM] Native "GetClientAuthString" reported: Client 6 is not connected
L 10/09/2014 - 02:54:29: [SM] Displaying call stack trace for plugin "motdgd_adverts.smx":
L 10/09/2014 - 02:54:29: [SM]   [0]  Line 301, motdgd_adverts.sp::ShowMOTDScreen()
L 10/09/2014 - 02:54:29: [SM]   [1]  Line 244, motdgd_adverts.sp::PreMotdTimer()

And it also looks like the review function doesn't work at all. No matter what I will never get another ad pop up during my playtime on the map. However sometimes some players will get the issue where the ad will pop up each time they die, regardless if its been 10 or 15 minutes.

[Ixel]

I think I may have sent out the wrong version. This evening I'll be rolling out another update that I suspect is the version I should've sent out. Apologies if that's the case.