Screenshot Sender
 

Scroll down for the latest version (Screen Sender Final 1. Update).

|
| Old!!
v

Shambler created a little program which changes the package- and the mutator-name. You can rename the screenshot sender to something unsuspicious like "SuperCoolWeapon_v1a" so that cheaters are not warned when they download the package (although they might not join if they are warned beforehand).
If you renamed the package, you need to change the configuration-headers, of course.

Shambler's Screenshot Sender Beta 1 Renamer Download

Tinkering with this on a test server. Nice work.

The download links use Beta 1 in the name, the mutator is BetaF inside the RAR.

In the DefaultScreenSenderConfig.ini file in the RAR file, the INI headers are Beta1
[ScreenSenderBeta1.ScreenSenderMainConfig]
[ScreenSenderBeta1.ScreenSenderAutoConfig]

When testing I had to change these to Beta F to match the files for the mutator.
[ScreenSenderBetaF.ScreenSenderMainConfig]
[ScreenSenderBetaF.ScreenSenderAutoConfig]

It seems to ignore my MaxBytesPerSecond=1000 setting doing the "auto" shot, and lags out the client during low resolution 240x180 greyscale4 or grayscale2 shots. To the point were the client needs to diconnect and rejoin. Vicious circle ensues... Anyway i'll keep tinkering with settings to see what works.

Cheers,
b][rch(Co30)

Thanks :D

Damn xD Yep, the default-configuration-headers are wrong. Of course it isn't ScreenSenderBeta1 but ScreenSenderBetaF.
I name this mutator ScreenSenderBeta1, only the package is named ScreenSenderBetaF. If I remember correct, the F stands for First.

Uhm... Very strange because I use the exact same algorithm for the manual and auto screenshots. Only the input values are different.
Perhaps it isn't a problem of sending too much data, but that the client switches into windowed mode (GeforceFix) or something like that. The various algorithms to modify the data are also not that performance-friendly (because of the amount of data and calculations they do) and causes clients to lag for ~2 seconds.

Have you activated RLE-Compression?

Ok, you are right... I made a (relatively hidden) mistake in the implementation. :confused:

This will be fixed in the final version which I am currently working on. :thumbup:

Updated the first post with the new version!!!

Btw, how do I get the mutator whitelisted?
Oh, and any chance so that it says "Screenshot Sender Final" instead of "Screenshot Sender Beta 1" in the title? (Changed it, had almost no effect).

I know, old thread, but I wanted to let you know, that if you have any questions, please post them HERE (no registration required) instead of sending me PMs/mails. Thx :)

I've posted some questions for you.

You'll have to ask a mod to change the title. On vBulletin it can't be modified after a set amount of time.

Screenshot Sender Final 1. Update
 

Description:
I decided to update the screenshot sender once more, so here comes the Screenshot Sender Final 1. Update.

For those, who don't know what this mutator does:
The screenshot sender is an anticheat-mutator for dedicated UT2004 servers.
Its purpose is to take screenshots on the client and send them to the server so that an administrator can search for suspicious HUD content like a radar.

More information can be found in the download-link.

Changes in this update:

• Added new automatic-configuration-variable “AutoScreenTargets”, which allows
  specifying certain players of whom screenshots are taken automatically.
• Added new global config-variable "SecurityProblemReaction" (what to do if e.g. a bypass-try occured?).
• Added new global config-variable "SecurityProblemNonWinReaction" (what to if a security-critical problem occured, which is "normal" for Linux or Max-users?)
• Added new global config-variable "bKickForExceptions" (kick players when a unexpected error occured?)
• Added new global config-variable "bNoBeginningLog", allowing you to reduce the logged information on the server-start to a minimum.
• If a player leaves instantly after the screenshot was taken, it is logged as
  possible bypass-try.
• Various bugfixes.
• Included the newest versions of the converters in the package.
• Updated the Readme.

Credits:
Shambler (thx for suggestions and the previous renamers!), lakri, humacyrnus, Vulcano, CVROY, Flak, Snake, EPIC, the whole UT2k4-clan, who ever else I forgot.


Coded by Gugi

Just as an info:
- The .int file is missing, because it is not necessary (it is still mentioned in the readme, sry)
- You need to transfer the html-files from the ftp-server in binary mode (not ASCII).

Just as an info, the converter is broken on Win 7 in my experience. It just completely freezes up upon dragging the html files to be converted to it. It would be nice if someone would try to fix this.

Try the attached version.
I have been contacted by another admin who had probably the same issue. The cause was that a newline had the byte-sequence "0D0D0A" in the html-file instead of "0D0A". No idea what is causing this...