Nainstalovat Steam
přihlásit se
|
jazyk
简体中文 (Zjednodušená čínština)
繁體中文 (Tradiční čínština)
日本語 (Japonština)
한국어 (Korejština)
ไทย (Thajština)
български (Bulharština)
Dansk (Dánština)
Deutsch (Němčina)
English (Angličtina)
Español-España (Evropská španělština)
Español-Latinoamérica (Latin. španělština)
Ελληνικά (Řečtina)
Français (Francouzština)
Italiano (Italština)
Bahasa Indonesia (Indonéština)
Magyar (Maďarština)
Nederlands (Nizozemština)
Norsk (Norština)
Polski (Polština)
Português (Evropská portugalština)
Português-Brasil (Brazilská portugalština)
Română (Rumunština)
Русский (Ruština)
Suomi (Finština)
Svenska (Švédština)
Türkçe (Turečtina)
Tiếng Việt (Vietnamština)
Українська (Ukrajinština)
Nahlásit problém s překladem
http://pastebin.com/RFsxTaut (I think the dates are May 17th to May 24th)
//End of EDIT
This week's (May 24th to 31st) new runs data. Note that this is limited to the top-50 rankings for Enhanced Multiplayer.
http://pastebin.com/cvRkmzzw
I think I explained a little bit of the the method behind it above. But let me see if I can cover the bases better.
The table is composed of individual entries on the leaderboard (this would show up as a row in the ingame browser).
Rank is the rank the entry had when I took the screenshot.
PlayerName is the name that appeared with the entry, again at the time of the screenshot, and as read by the image parser (see disclaimer in OP).
CompTime is the completion time for that entry. It's the same time you'd see on the leaderboard row.
CharUsed is a series of letters that represent the characters that showed up in the row on the leaderboard. The OP has a list of what the individual letters mean.
LevelName is the name of the map the leaderboard entries appear under. Like when you use left-or-right to tab through the pages in the ingame leaderboard browser.
LeaderType is just Enhanced Multiplayer right now. If I get more thorough, you might see stuff like Classic MP or Enhanced 1P. This is what you get if you use [X] button to tab through leaderboard types for a single map in the ingame browser.
As for methodology, let me see if I can put it into simpler language, for potentially everyone's benefit.
Every week-ish, I take screenshots of the Monaco all-time leaderboards in game and file them away into the database. Then I run a database query (imagine taking a deck of cards and pulling out all the red ones, or all the spades) to pull out every 'entry' (imagine a single row of the leaderboards, but with some added info like the map name) that is the most recent. That is to say, for each map, for each leaderboard type, for each individual rank number, get the entry in the database that is the most up-to-date. It's like refreshing the ingame leaderboards as a player gets a new all time (the old ones are displaced and the new entry enters at say Rank #1).
To get this particular list, I consider each run as a unit. A 'run' is a combination of completion time, characters used, level name, and leaderboard type. So let's say you complete Banque Albert in Classic Mode using Mole, Locksmith, Lookout and Pickpocket in 1:50.30. The 'run' is distinct from the players on the run (because I can't keep track of people changing their name, like the steam leaderboards can) and from the rank (because a run's ranking changes as people create faster runs). For each run in the database (they have a separate table from entries), I check if the run's only occurrences are in the 'current entries' query I explained above. If the run also has entries in older data, it isn't considered new and is disqualified. Then, I take this list of new runs, and pull all the entries that include the run (the same as the rows would appear in the ingame leaderboards). This is what you get here.
So as I understand it now, this table shows the new speed runs that were added last week (which basically is your OP title, but was never extensively mentioned).
You consider a run to be a (decent) speed run if it's in the top 50 of a level and you compare each week with the previous week to show which entries are new. That way people can see the progress speed runners are making in a short overview.
Looks really good. Would be nice to hear some feedback from some of the speedrunners in the community to hear their opinion as well!
http://pastebin.com/8dasqtpC
The poor fellow who shows up as most of the "ERROR - Parser Failure"s this week is probably 0.o in most of them. Sorry 0.o, I don't think Tesseract-OCR likes you much.
I've added top 20 ranks for Enhanced 1P. 20 was an arbitrary choice. Maybe I'll expand that later. But bear in mind there are 48 levels. So every 10 ranks I add to the weekly reports is another 48 screenshots to both capture and run through the parser and database software. I'm already up to about 370 a week, not counting any other random stuff I grab (like some Classic or Zonaco for my own interest).
http://pastebin.com/Cf0rWfTV
I've started collecting top 20 1P data for all the game modes, but it will be another week or two until I get a second observation to compute new runs with.
I was going to post the Classic MP new runs a week ago, but the only new runs were the same team of four replaying levels. So congratulations to CORL!, Chromic Slicer, Vini and Vellaroque for their classic runs from a week ago-ish.
http://pastebin.com/aT0wx4H4
The "ERROR - Parser Failure"s are getting embarassing for me. I'll see about creating a better font file for tesseract to try to fix the issue. But it might just be that tesseract can't handle a name like 0.o (possibly no way to judge the font size with three completely differently sized characters?).
http://pastebin.com/LVazcLqy
It's interesting how many more Zonaco runs there are than classic runs lately. Then again, classic isn't too much different than Enhanced. So I guess it's sort of eclipsed.
It would either do nothing or try to lump in my classic score with the enhanced. Sometimes it showed that there were 0 all time classics when chekcing for all players.
Here's the Enhanced Mode new runs for June 14th to 21st:
http://pastebin.com/fTfgFtK4
http://pastebin.com/H4BgdtkH
http://pastebin.com/vptv7yA6
To address some of the concerns with names, I've started working on new font and dictionary files for the parser. The names should be a bit more accurate (but not for everyone, for some reason O's are occasionally becoming D's). Unfortunately for F_i_s_t_o and O.o, I still haven't found a solution for your names sometimes not being read at all. I have some ideas I'll have to try, but this week turned out as it did.
http://pastebin.com/BYcqeAnt
Not relevant for this posting, but as sort of an update. I've got a small fix in place for some of the unreadable names. 0.o works. I dunno if F_i_s_t_o will work 100% of the time yet (since that name did appear most of the time already, it will be hard for me to debug). I do still get a few unreadables, but progress! I've also reverted back to the old font files temporarily. The new ones work, but I think I still want to make some improvements (and I'd rather not do the back-end stuff like updating all the old, mispelled level names in the database multiple times). So patience as I sort that out (probably won't be ready for the next batch of Enhanced Mode runs on the weekend).
http://pastebin.com/TCpeEQ7T
Looks like quite the busy week! And no "ERROR" names this week. Getting on track!