Go nuze!
| Account Details | |
|---|---|
| SteamID64 | 76561198074409147 |
| SteamID3 | [U:1:114143419] |
| SteamID32 | STEAM_0:1:57071709 |
| Country | Poland |
| Signed Up | January 1, 2016 |
| Last Posted | March 4, 2026 at 7:44 AM |
| Posts | 291 (0.1 per day) |
| Game Settings | |
|---|---|
| In-game Sensitivity | |
| Windows Sensitivity | |
| Raw Input | |
DPI |
|
Resolution |
|
Refresh Rate |
|
| Hardware Peripherals | |
|---|---|
| Mouse | |
| Keyboard | |
| Mousepad | |
| Headphones | |
| Monitor | |
Map pool update:
* removed cp_sunshine;
* added cp_cardinal_rc1a.
kaidusAny chance we could get a version of prolands with the old last cap speed? Doesn't have to be an official release, but it would be nice to try it out and see how much impact it makes to pushing last/stalemates. Would be very easy to test it as an unofficial version as well since it barely changes the map.
I honestly believe this change by valve is a primary reason why it became a problematic map after many years of ubiquitous enjoyment. The arguments against the old cap speed (backcaps/ninjas etc) are valid, but I really think the the trade-off is worth it.
You just want to make it easy for thalash to backcap don't you
TwiiKuuMenachemso hey if demos.tf is cool are there any plans to get some logs.tf action?
What Brimstone said is true.
I do plan on providing additional stats, whether it be by generating logs for logs.tf or by proposing and coding features for demos.tf.
I can foresee that players would rather have all their logs in one website (that would currently be logs.tf) but the integration would be painful and error-prone.
I think demos.tf has more potential to be a more fitting service for us *and the rest of the community* in the long run:
- STV demos will never require a third party plugin to run (meaning ESEA demos could be uploaded)
- Additional features can be applied to older demos (whereas new logs features can't be backported)
- Intensive stats will never require the gaming server to choke
- Demos.tf software is open source, any kind of statistic can be added
- Hypothetical: stats could be generated directly from a live STV feed (granted you plug it before the match starts)
- 2d/3d Heatmaps
- Automatically slice demos for fragmovie makers
I could come up with even more ideas, the only limiting factor is my free time
There are some downsides, obviously:
- Demo analysis (without packet filter) can be quite CPU expensive
- Demos take more space
- Both meaning that stats may take longer to be available
- It's possible that STV demos are missing crucial packets to provide information to clone stats from logs.tf
Is the file format tf2 demos use known? Can we actually slice demos and retrieve particular information out of them?
You can store the x and y params in a tuple as well, without using classes. But this approach sounds pretty painful in a long-term...
Have you had any experience with oop before?
If you need inspiration or coding style guidelines, browse GitHub for some python math-oriented projects. There should be a lot of solutions that may fit your project.
Apart from that - wrap the Vector in a class and implement __add__ method and hide the math logic in it.
now i have to ask for permission :c
Happens to me sometimes, more often during intense mge sessions.