Security News
Input Validation Vulnerabilities Dominate MITRE's 2024 CWE Top 25 List
MITRE's 2024 CWE Top 25 highlights critical software vulnerabilities like XSS, SQL Injection, and CSRF, reflecting shifts due to a refined ranking methodology.
github.hscsec.cn/markus-wa/cs-demo-minifier
This tool and library aims to provide a way of converting CS:GO demos into a more easily digestible format while decreasing the data size (up to 99.7%) and retaining all important information. It is based on the demo parser demoinfocs-golang.
The project is still under development and the data formats may change in backwards-incompatible ways without notice.
Use gitter to ask questions and discuss ideas about this project.
There are also some other rooms available around the topic of CS:GO demos.
See the releases page for pre-compiled executables for Linux, MacOS & Windows.
# Library
go get -u github.com/markus-wa/cs-demo-minifier
# Command line tool
go get -u github.com/markus-wa/cs-demo-minifier/cmd/csminify
The following command takes one snapshot of a demo every two seconds (-freq 0.5
) and saves the resulting replay in the MessagePack
format to demo.mp
.
csminify -demo /path/to/demo.dem -format msgpack -freq 0.5 -out demo.mp
$ csminify -help
Usage of csminify:
-demo path
Demo file path (default stdin)
-format string
Format into which the demo should me minified [json, msgpack, protobuf] (default "json")
-freq float
Snapshot frequency - per second (default 0.5)
-out path
Output file path (default stdout)
Format | Command Line (-format ) Flag | Structure | Minimal Example | Full Example |
---|---|---|---|---|
JSON | json | schema.json | minimal.json | see releases page |
MessagePack | msgpack , mp | schema.json | minimal.mp | see releases page |
Protocol Buffers | protobuf , proto , pb | replay.proto | minimal.pb | see releases page |
The minimal examples contain an extract of a demo with each event being included at least once. Events and attributes are also are documented in events.md.
More formats can be added programmatically by implementing the ReplayMarshaller
interface.
If you would like to see additional formats supported please open a feature request (issue) or a pull request if you already have an implementation ready.
jq
As the CLI supports Unix pipes, you can combine it with other tools such as jq
.
In this section you can find a few examples.
$ csminfy < demo.dem | jq -r '.header.map'
de_cache
$ csminify < test/cs-demos/default.dem | jq -r '[ .ticks[] as $parent |
$parent.events[] | select(.name=="kill") as $kill |
$kill.attrs[] | select(.key=="victim") as $victim |
$kill.attrs[] | select(.key=="killer") as $killer |
$kill.attrs[] | select(.key=="weapon") as $weapon |
{
tick: $parent.nr,
kill: { victim: $victim.numVal, killer: $killer.numVal, weapon: $weapon.numVal }
}] | .[0:3]'
[
{
"tick": 43,
"kill": {
"victim": 9,
"killer": 2,
"weapon": 303
}
},
{
"tick": 1029,
"kill": {
"victim": 7,
"killer": 4,
"weapon": 9
}
},
{
"tick": 1057,
"kill": {
"victim": 11,
"killer": 4,
"weapon": 9
}
}
]
$ du -sk demo.dem
67696 demo.dem
# original demo is 67 MB
$ csminfy < demo.dem | gzip > demo.json.gz
$ du -sk demo.json.gz
160 demo.json.gz
# gzipped JSON is 160 KB
# -> reduced size by ~99.7%
This is an example on how to minify a demo to JSON and decode it to a replay.Replay
again.
package main
import (
"bytes"
"encoding/json"
"log"
"os"
csminify "github.com/markus-wa/cs-demo-minifier"
rep "github.com/markus-wa/cs-demo-minifier/replay"
)
func main() {
// Open the demo file
f, err := os.Open("/path/to/demo.dem")
defer f.Close()
if err != nil {
log.Fatal(err)
}
// Minify the replay to a byte buffer - or any other io.Writer (JSON)
// Take 0.5 snapshots per second (=one every two seconds)
freq := 0.5
buf := new(bytes.Buffer)
err = csminify.MinifyTo(f, freq, marshalJSON, buf)
if err != nil {
log.Fatal(err)
}
// Decoding it again is just as easy
var r rep.Replay
err = json.NewDecoder(buf).Decode(&r)
if err != nil {
log.Fatal(err)
}
}
// JSON marshaller
func marshalJSON(r rep.Replay, w io.Writer) error {
return json.NewEncoder(w).Encode(r)
}
MessagePack marshalling works pretty much the same way as JSON.
For Protobuf use protobuf.Unmarshal()
(in the sub-package).
To run tests Git LFS is required.
git submodule init
git submodule update
pushd test/cs-demos && git lfs pull -I '*' && popd
go test ./...
.golden
filesThere are golden
files that are used to make sure no unintended changes are introduced.
This will cause tests to fail when adding new data to the output.
To update these files when you inteded to make such a change (such as adding new events etc.) you will need to run the following command
go test -updateGolden
Should you need to re-generate the protobuf generated code in the protobuf
package, you will need the following tools:
The latest protobuf generator (protoc
) from your package manager or https://github.com/google/protobuf/releases
And protoc-gen-gogofaster
from gogoprotobuf to generate code for go.
go get -u github.com/gogo/protobuf/protoc-gen-gogofaster
Make sure both are inside your PATH
variable.
After installing these use go generate ./protobuf
to generate the protobuf code.
This project is licensed under the MIT license.
FAQs
Unknown package
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
MITRE's 2024 CWE Top 25 highlights critical software vulnerabilities like XSS, SQL Injection, and CSRF, reflecting shifts due to a refined ranking methodology.
Security News
In this segment of the Risky Business podcast, Feross Aboukhadijeh and Patrick Gray discuss the challenges of tracking malware discovered in open source softare.
Research
Security News
A threat actor's playbook for exploiting the npm ecosystem was exposed on the dark web, detailing how to build a blockchain-powered botnet.