snowguy

EvilGrins · 2025-04-02T00:21:12+00:00

I recently posted to the 50+ UT groups I follow on Facebook to see if there's any other skinners out there... doesn't appear to be, but I did find some interested in learning.

Not that I have any immediate interest in starting another Skinning Contest, but I'm toying with the idea.

Although the general consensus is if I took part in it I'd win... so I may not enter anything of my own.

Though I may allow for edits of existing skins next time; like this one:

Head pieces from the DeadKatz skin sets, overall body from SkinCity's database, customized talk textures which seemed to work best.

Enjoy!
https://www.mediafire.com/file/etb0rpdohy30as5/SoldierSkins_WT.zip

Titan · 2025-03-24T09:25:09+00:00

I took a look at the code, and yes, to say the least, recalculating player stats is terrible. Can you please run the SQL? It will show you how many players statistics should be generated for.

SELECT count(*) as cnt FROM
(
SELECT 	
  p.id, 
	p.matchid, 
	p.pid, 
	p.gid,
	m.gamename
FROM uts_player p, 
		 uts_pinfo pi,
		 uts_match m
WHERE 	pi.id = p.pid 
	AND 	pi.banned <> 'Y' 
	AND	  m.id = p.matchid
-- ORDER BY p.matchid ASC, p.playerid ASC
)

PS: I don't understand why the original select contains an ORDER BY statement. It shouldn't really matter which player or match the ranking is based on. But perhaps there's a deeper meaning to it that I'm not currently seeing.

A comprehensive ranking calculation is then created for each result row. You can see this in the while loop in admin/recalcranking.php:

  while( ...) {
     ...
     
     include('import/import_ranking.php');
  }

WOW! I can well imagine this getting out of hand.

PS: The include within the while loop is terrible, by the way. I think this whole thing could be solved today with the PHP option of snippets, no, it's called traits.

Suggestion: You could probably speed up the ranking by restricting the ranking to "active" players. For example, by only considering matches from the last 90, 180, or 365 days. It would then look something like this:

SELECT 	
  p.id, 
	p.matchid, 
	p.pid, 
	p.gid,
	m.gamename
FROM uts_player p, 
		 uts_pinfo pi,
		 uts_match m
WHERE 	pi.id = p.pid 
	AND 	pi.banned <> 'Y' 
	AND	  m.id = p.matchid
	AND   m.time < _______         /*   <=== NEW!  */
ORDER BY p.matchid ASC, p.playerid ASC

You'll have to take a look at what the "time" column looks like in the database (it's defined as varchar(14), so you don't specify time values!!).

Other aspects that caught my attention:
The colleagues who wrote the tool are familiar with UT and statistics, as you can see. But they have no idea about databases.

In admin/check.php, most CREATE TABLE scripts are coded with "CREATE TABLE uts...". Only one table has the suffix "CREATE TABLE IF NOT EXIST uts....", which would be the safer option.
Every column in every table is defined with "NOT NULL." Why? Presumably because of the subsequent HTML output?!
Numeric data types are usually initialized with an incorrect default (... DEFAULT '0')
More or less everything in the database is processed using single-record processing. Set-based operations, especially for INSERTS, UPDATES, etc., would be much more efficient.

[Okay, that's high-level criticism. The guys did a great job ]

Otherwise: I hope your admin key is secure. The site is easily accessible. Could you guess the key using a dictionary?

I haven't checked whether it's an Apache or something else server, but maybe you (@snowguy) are securing the admin pages with an http login (htpasswd)?

Titan · 2025-03-20T10:41:54+00:00

Maybe it's further up in the text and I just missed it, sorry.

To avoid multiple loading, you could set a primary key for the target table that is derived from one of the natural attributes (e.g., the date the map was started). If this isn't feasible with a primary key, a unique key (UK) can also help. It might be possible to resolve the UK, which includes multiple columns, but this would make the inserts longer.

Alternatively, you can also pursue the following solution strategy: You don't load the data immediately into the actual target table, but rather into a staging table. You can then perform the inserts row by row using a cursor. If the UK matches (see above), an existing record is rejected, and the remaining ones are entered into the target table.

If you are interested in the rejected data, you can simply write the data to an error table in the event of an error using this procedure.

Depending on how results are calculated (the ranks mentioned above), there are also workarounds: either you calculate only a subset of the ranking in a suitable loop (e.g., only player names beginning with "A," then "B," etc.).

Alternatively, you have to look at the query to determine the ranking. Nested full table scans are expensive. Here, you could speed up the query by using indexes on the appropriate columns.

If all else fails, you can consider rewriting the ranking calculation (query rewrite) or storing intermediate results in a temporary table. If the database starts swapping data with large amounts of data, the query quickly becomes imperformant.

Covid_A_Swab · 2025-03-08T19:59:05+00:00

i was bored and started editing Comboking because its such a dark map ( I sometimes have difficult with dark maps) and i like to make it summer style because offcourse its getting summer!! not sure if this could become a map, i made a secret tunnel pipe under the flag that exits to the lower middle.
only 1 side because im not sure about it yet.

Just an experiment what do you think?

ctf-combo-king-day4.7z

2MB

bustacell · 3 Mar

ESUOH · 28 Feb

UT Players Settings_Setups by Crawford - year 2020

Name cm/360° DPI Mouse Hz Win sens In-game sens Acceleration Mouse Input Renderer UT version

BNG 40 caden 90 400 1000 Crawford 26 800 1000 Cromaniac 52 800 1000 D!ÄtêR^ 28 900 1000 Damien 38 800 1000 Dewsick 26 800 1000 Finalz 28 1600 1000 Gizmo 17 800 1000 Hatchet 22 800 1000 iMpacT^ 35 400 1000 iMpure 45 500 1000 JeRoMe^ 72 jyb 65 400 500 keizeR 77 400 1000 K-os^ / lockpick 60 400 500 Loque 56 550 1000 MaDTeTa 37 800 1000 noobx 17 1600 1000 p4j1 25 800 1000 rain 33 600 1000 Ramdrop 60 1700 500 riven 60 800 1000 rummy 40 800 1000 Serenity / solidsnake 60 800 500 Staci 29 uenz^ 24 800 1000 unrealshots 25 800 1000 vega 41 800 1000 Viperzz^ 10 2100 1000 1600 1000 6/11 0,36 no Raw Input D3D9 469
6/11 0,56 no DirectInput D3D9 469
6/11 0,9 no Raw Input D3D9 469
6/11 0,83 no Raw Input D3D9 469
6/11 0,66 no DirectInput D3D9 436
6/11 0,7 no DirectInput D3D8 436
6/11 0,71 no Raw Input D3D9 469
6/11 0,43 no Raw Input OpenGL 469
6/11 0,35 yes Cursor D3D9 469
6/11 0,82 no Raw Input D3D9 469
9/11 0,42 no DirectInput D3D8 436
6/11 0,84 no DirectInput D3D9 469
1200 1000 6/11 0,2 no Raw Input D3D9 436
6/11 0,68 yes Raw Input D3D9 469
6/11 0,5 yes DirectInput D3D9 469
400 1000 6/11 0,39 no Raw Input D3D9 436
6/11 0,78 no DirectInput D3D11 436
6/11 0,66 no Raw Input D3D9 469
6/11 0,65 no Raw Input D3D9 469
6/11 0,65 no Raw Input D3D9 469
6/11 0,5 no Raw Input D3D9 469
6/11 2,12 no Raw Input D3D9 469
6/11 0,26 no DirectInput D3D9 436
6/11 0,4 no DirectInput D3D9 469
6/11 0,65 no Raw Input D3D9 469
900 1000 6/11 0,94 no Raw Input D3D9 436
6/11 0,4 no Raw Input D3D9 469
800 1000 6/11 1 no Raw Input D3D9 469
6/11 0,8 no Raw Input D3D9 469
6/11 1,5 no Raw Input D3D9 469
6-11 0,43 no Raw Input D3D9 469
6-11 0,2 no Raw Input D3D9 469

player                   Mouse	                              Mousepad	                 Resolution	Fov

BNG Razer Viper Ultimate Gigabyte Aorus AMP500 1920x1080 85
caden CoolerMaster MM710 HyperX Fury S 1600x900 80
Crawford Logitech G502 Hero HyperX S Fury XL 1920x1080 85
Cromaniac Logitech G Pro Wireless HyperX Fury S XL 1920x1080 88
D!ÄtêR^ G-Wolves Skoll SteelSeries QcK+ 1920x1080 90
Damian Logitech G400 SteelSeries QcK+ 1920x1080 90
Dewsick Razer Basilisk v1 Razer Goliathus Control 1920x1080 93
Finalz Zowie EC2-A Zowie G-SR 1920x1080 90
Gizmo Logitech G900 Razer Goliathus Control 2560x1440 84
Hatchet Logitech G502 Corsair MM200 Extended Cloth 1920x1080 90
Impact Logitech G502 Logitech G440 1920x1080 90
iMpure Logitech MX518 Logitech G840 1440x1080 87
JeRoMe Roccat Kone EMP Roccat Taito 1920x1080 110
jyb Logitech G5 Artisan Zero Soft 1920x1080 90
keizeR Logitech G Pro Wireless SteelSeries QcK Heavy 1920x1080 87
K-os Zowie EC2A Zowie G-SR 1920x1080 80
lockpick Logitech G203 HP Omen 1920x1080 87
Loque Razer Viper Razer Goliathus Speed 1920x1080 80
MaDTeTa Glorious Model O Razer Goliathus Control 1680x1050 85
noobx Razer Viper Mini Nedis Glass 1920x1080 90
P4j1 Glorious Model O CoolerMaster MP510 3840x2160 85
rain Logitech G502 Hero SteelSeries QcK XXL 1920x1080 90
Ramdrop Razer Deathadder Razer Goliathus Control 1920x1080 95
riven Logitech G403 HyperX Fury S 1920x1080 85
rummy Logitech G403 SteelSeries QcK Heavy 2560x1440 87
Serenity Logitech G502 Razer Goliathus Control 1920x1080 87,5
Solidsnake Logitech G305 SteelSeries QcK XXL 1728x1080 80
Staci Razer Lancehead Razer Goliathus Speed 1920x1080 85
uenz Logitech G Pro Wireless Razer Goliathus Control 1920x1080 90
unrealshots Logitech G703 Hero Cooler Master MP510 1920x1080 85
vega Logitech G Pro Wireless Gigabyte Aorus 1920x1080 85
Viperzz Logitech G502 Proteus Spectrum Logitech G440 1920x1080 90

bustacell · 25 Feb

bustacell · 16 Feb

bustacell · 9 Feb

Ann0ying · 8 Feb

I'm a PHP Developer, but I've no idea if this can help on your case.
you can convert to UTF16LE with:

$str = mb_convert_encoding($str, "utf-8", "UTF-16LE");

Ooper · 8 Feb

What I used in nodejs to deal with the encoding stuff https://www.npmjs.com/package/encoding-japanese, don't know if there is something similar for php.

Ooper · 2 Feb

Rankings are pretty meaningless with the way the combo server is, if you only play normal ctf maps you will be nowhere, play joust, andaction, woot, you will get a lot more ranking points.

I'm guessing ranking is only calculated for the players in the current imported log, you could just empty the rankings table and then just have rankings for more recent matches without losing years of data or waiting hours for the recalculate rankings(rankings would just be current active players more or less, if older players come back their rankings would return as well).

edit

looking at the recalculating code it's not very efficient, but it is 20ish year old code so some stuff may have not existed back then.

Jacey · 2 Feb

snowguy Is that what those of you who care about stats would want?

Why not delete it all together, who cares about stats anyway? Saves you the trouble and time fixing it....

destro · 2 Feb

I'm not going to speak for everyone but I generally look to see my accuracy of my last few games. So getting the 2025 stats would be great.

bustacell · 1 Feb

EvilGrins · 1 Feb

There's a typo in the .int file for the skin's name, would've been easy enough to fix but I think there's another skin with the same intended name so I left it as is.

3 faces, African skin tones as provided by Baardman, and subtle team colors.

Didn't team color the armor above the waist but opted instead for the shirt just under the armor.

Enjoy!
https://www.mediafire.com/file/9ulqn1kdka7p1uh/SoldierSkins_BlackKnights.zip

Ooper · 28 Jan

Not tested it(have to install old php), should save having to delete one by one, luckily utstats doesn't cache totals so there is no need to recalculate those totals. I've not touched PHP in years will have a play around later to see if it works or not and it not just be pseudo code.

SELECT id,time,COUNT(*) as total_matches FROM uts_match GROUP BY time HAVING total_matches > 1;

use the dates returned from the query above

SELECT id FROM uts_match WHERE time IN (...)

use the match ids returned from the query above in the ones below

DELETE FROM uts_events WHERE matchid IN (...);
DELETE FROM uts_killsmatrix WHERE matchid IN (...);
DELETE FROM uts_match WHERE id IN (...);
DELETE FROM uts_player WHERE matchid IN (...);
DELETE FROM uts_weaponstats WHERE matchid IN (...);
DELETE FROM uts_chartdata WHERE mid IN (...);

Use the admin recalculate rankings to fix the rankings```

MORTIS · 27 Jan

New small "1on1" map which should provide massive chaos when played with more players.

Straight forward layout where 3 separate paths lead to the flagbases

Basic beta tested needed although I think the map is pretty solid as it is. But maybe I missed something..

ctf-1on1-tumultb1.zip

2MB

Ooper · 26 Jan

More recent update: https://github.com/OldUnreal/UnrealTournamentPatches/releases/tag/v469e-rc7

Player · 17 Jan

Removing the joystick keybinds didn't make a difference for me. However, a simple restart of the computer fixed it. Strange. If it comes back I will let you know. Running Windows 10, UT v469 (i don't know if it's d)

snowguy

EvilGrins

Titan

Titan

Covid_A_Swab

bustacell

ESUOH

Name cm/360° DPI Mouse Hz Win sens In-game sens Acceleration Mouse Input Renderer UT version

bustacell

bustacell

bustacell

AAnn0ying

Ooper

Ooper

Jacey

Ddestro

bustacell

EvilGrins

Ooper

MORTIS

Ooper

PPlayer