Forts Tools

Read your ranked match log

Forts keeps a running record of your ranked matches on your own machine. Upload it and this turns it into a table: every match, the map, who won, what your score did, and how much damage each side dealt.

Maximum file size 32 MB.

Keep or publish (optional, off by default)

The file and its result are stored with the game version, the upload time and the file's name, so forts-tools can study them. You get a private link to download or delete them. Up to 96 MB per file, 50 a day.

Look up a player

Enter a Steam ID or a player name to open that player's ranked matches.

What it shows you

The game writes it as log2.dat for ranked matches or log3.dat for other online matches, in its own folder under the Steam install — steamapps/common/Forts/users/<your account>/ — beside your replays folder.

API reference

· Changed in v2

Decode a Forts telemetry log to JSON. Server-to-server; the browser-facing surface is the form above.

Changed in v2: POST /api/telemetry forts-telemetry/2

POST /api/telemetry now answers a ranked log of any size, in pages. Its schema is forts-telemetry/2; it was forts-telemetry/1.

What changedIn v1 a log with more matches than one answer holds was refused with 422. In v2 it is answered in full, over several pages. New fields: page, pages, next_url, samples.matches[].continued.
What a v1 client must doAccept forts-telemetry/2. While page is less than pages, fetch next_url with GET; stop when page equals pages (next_url is then null). Join the pages as below. A client that reads only the first answer gets only page 1 of a long log.
UnchangedA log of 300 or fewer matches (with ?samples=1, also 6,000 or fewer series points) is answered exactly as in v1 apart from the tag: one page, page: 1, pages: 1, next_url: null.
Further pages/api/telemetry/<job>/<page>, by GET: pages 2 to pages, the same shape as page 1. Nothing is uploaded or decoded again.
Page size300 matches; with ?samples=1, also at most 6,000 series points.
Result lifetime10 min from the first answer, the same as downloads[].url. After that a page answers 410; upload the log again.
Joining the pagesmatches: pages 1 to pages in order, concatenated. samples.matches: the same, except that an entry marked continued: true goes on in the first entry of the next page; append that entry's rows to it. summary, releases, matches_total, rejections, downloads are the same on every page.
Page statuses200: the page. 404: no such page number. 410: the result has expired. 429: the rate limit, shared with the upload, is spent.
EndpointPOST https://forts-tools.com/api/telemetry
Request bodymultipart/form-data
Response bodyapplication/json
AuthenticationNone. No key, no origin allow-list.
Browser accessNo CORS headers are sent. fetch() from a page is blocked by the browser before the body is readable. Call this endpoint server-side.

Parameters

NameInTypeRequiredNotes
logfilemultipart bodyfilerequiredThe game's telemetry log — the same file the form above takes. Ranked and network logs are both accepted; kind says which one was read.
samplesquery stringstringoptionalInclude the per-match time series. On: 1, true, yes, on. Off (default): 0, false, no, off. Any other value: 400. The series is one point every few seconds of play; over a full season it is larger than the rest of the response.

Example request

curl -X POST -F "logfile=@your-log.dat" \
     https://forts-tools.com/api/telemetry

Response

Field names, type names and token values are fixed. They are not translated.

Every field has one type or null. null means the file did not record the value: never words standing in for a value, never 0 for a figure that was never written. An empty array means the file records none, not that the value is missing.

schema is forts-telemetry/2. It changes only on a breaking change; a new field never changes it. Any other value is outside this contract.

FieldTypeDescription
okbooleantrue on success, false on failure.
schemastringContract version. Currently forts-telemetry/2.
releasesstring[]Game releases the file recorded, sorted and deduplicated. Empty when it recorded none.
summaryobjectWhole-file figures. Fields below.
matchesobject[]This page's matches, oldest first. Pages 1 to pages in order give every resolved match. Fields below.
matches_totalintegerMatches resolved in the file: the length of matches summed over every page.
pageintegerThis page's number, from 1.
pagesintegerHow many pages the answer has. 1 when everything fits in one.
next_urlstring | nullPath of the next page on this host, /api/telemetry/<job>/<page>, to fetch with GET; null on the last page. Pages stay fetchable as long as downloads.
rejectionsobject[]Lines the reader could not resolve, grouped by message. Fields below.
samples_requestedbooleanWhether ?samples=1 asked for the series.
samplesobjectThe per-match time series. Fields below. Present but empty unless requested.
downloadsobject[]Files generated from the upload. The full decoded text is here, not in the body. Fields below.
expires_in_secintegerSeconds the downloads URLs and the pages stay fetchable.
summary
kindstring"ranked" or "network".
formatstringWhich framing the log file uses: "v1" for the plain format, "v2" for the self-framed one the game writes from 1.39.
lines_totalintegerLines in the decoded file.
lines_understoodintegerLines the reader resolved.
understood_pctintegerlines_understood as a percentage of lines_total, rounded.
readable_pctnumberShare of the file that decoded to text, as a percentage.
samples_totalintegerSample points across all matches.
matches_with_seriesintegerMatches that carry a sample series.
unresolvedintegerMatch blocks the reader could not close.
countersobjectEvent tallies. Keys: launches, forfeits, technical, lobbies, timeouts, uploads. An empty object means nothing was counted.
low_confidencebooleanThe reading is incomplete: readable_pct below threshold, or part of the file did not decode to text.
first_seenstring | nullEarliest date in the file, YYYY-MM-DD.
last_seenstring | nullLatest date in the file, YYYY-MM-DD.
season_firstinteger | nullLowest season number in the file.
season_lastinteger | nullHighest season number in the file.
winsinteger | nullWins in the season-to-date record, as of the most recent match in the file. The counter resets each season, so this is not a career total and does not add up to matches_total.
lossesinteger | nullLosses in the same season-to-date record, on the same terms as wins.
score_firstinteger | nullFirst leaderboard score in the file.
score_lastinteger | nullLast leaderboard score in the file.
score_bestinteger | nullHighest leaderboard score in the file.
matches[]
datestringMatch date, YYYY-MM-DD.
timestringMatch start time, HH:MM:SS.
seasonintegerRanked season number.
samplesintegerSample points recorded for this match. 0 means none.
notesstring[]Flags for this match. Values: won_by_forfeit, lost_by_forfeit, you_forfeited, technical_issue, match_voided, steam_connection_failed, opponent_disconnected, server_connection_lost, winner_disputed, pre_game_winner, score_disagrees, not_launched. [] means none.
map_namestring | nullMap the match was played on.
releasestring | nullGame release the file recorded for this match.
sidestring | nullThe uploader's team as the file writes it: "Team 1" or "Team 2". Not the "left", "right" tokens used by the replay endpoint.
resultstring | null"won" or "lost", from the uploader's side.
score_afterinteger | nullLeaderboard score after the match.
changestring | nullRating change, signed, e.g. "+14": the score change less the point a day the score adds by itself.
opponent_scoreinteger | nullOpponent's leaderboard score.
recordstring | nullSeason-to-date win/loss record after this match, e.g. "44W 9L". Resets each season.
damage_dealtstring | nullDamage dealt, two decimals.
damage_takenstring | nullDamage taken, two decimals.
durationstring | nullLength of play, mm:ss. Taken from the samples, so it excludes lobby and loading.
ping_msinteger | nullMatchmaking ping, in milliseconds.
stake_winstring | nullPoints that a win would have gained, signed.
stake_losestring | nullPoints that a loss would have cost, signed.
rejections[]
messagestringThe line as the file wrote it, cleaned. This is the uploader's own text and is not rewritten.
countintegerHow many lines carried it.
samples
columnsstring[]Column names for every row, in order: seconds, damage_dealt, damage_taken.
matchesobject[]One object per match that carries a series. Fields below.
samples.matches[]
datestringMatch date. Pairs with the matches row of the same date and time.
timestringMatch start time.
map_namestring | nullMap the match was played on.
rowsarray[]One array per sample point.
continuedbooleantrue when this match's rows continue in the first entry of the next page.
downloads[]
idstringArtifact id, as it appears in url.
namestringFile name. Always English, whatever this page's language is.
bytesintegerFile size in bytes.
urlstringPath to fetch, relative to the site root.

Figures typed string keep the sign and the decimal places the file's own line carried. They are text, not numbers: parse before doing arithmetic.

Each row holds the values named in samples.columns, in that order: seconds as an integer, then two damage figures as numbers rounded to two decimals, or null. A figure the file never wrote is null, never 0.

Limits

LimitValueNotes
File size256 B – 32 MB
File parts1Sent as logfile. If more than one is sent, the last is read.
Matches per page300Page size, not a cap. Every log is answered in full: a log with more matches comes back over several pages, decoded once. pages says how many; fetch next_url with GET until it is null. Every page repeats the same summary.
Sample points per page6,000Page size for the series, not a cap. A match whose points do not fit continues on the next page, its entry marked continued: true. A response is never silently shortened.
Requests per minute, per caller6Shared with the upload form on this page. Over it: 429.
Download and page link lifetime10 min

Errors

Every failure returns {"ok": false, "error": "…"} with one of the status codes below. error is a human-readable message in the language negotiated from Accept-Language. Branch on the status code, not on the message text.

StatusMeaning
200Success.
400Missing file part, file below the minimum size, unreadable file, or an invalid parameter value.
405Method other than POST.
413Body above the maximum size.
422File read but not usable: nothing decodable, or too large to decode.
429Rate limit exceeded. Back off; do not retry immediately.
500Internal error.
503Busy, timed out, or the endpoint is disabled.