| Account Details | |
|---|---|
| SteamID64 | 76561197960343048 |
| SteamID3 | [U:1:77320] |
| SteamID32 | STEAM_0:0:38660 |
| Country | Denmark |
| Signed Up | November 1, 2013 |
| Last Posted | February 22, 2022 at 7:37 AM |
| Posts | 53 (0 per day) |
| Game Settings | |
|---|---|
| In-game Sensitivity | |
| Windows Sensitivity | |
| Raw Input | |
DPI |
|
Resolution |
|
Refresh Rate |
|
| Hardware Peripherals | |
|---|---|
| Mouse | |
| Keyboard | |
| Mousepad | |
| Headphones | |
| Monitor | |
maidoshey i have logstf.smx uploaded on /home/tf2user/tf2/tf/addons/sourcemod/plugins
and have tftrue and soapmod installed but it doesnt upload logs :S
If you are using TFTrue, you don't need to use logstf.smx ... Just remove that.
TFTrue will upload the logs for you. You just need to put your logs.tf api key in your server.cfg:
tftrue_logs_apikey xxxxI released an update of the supstats2 plugin now that should fix the errors above.
Now we just need to wait for server admins to update it. It will happen automatically if they have the Updater plugin.
That is something I need to fix in the LogsTF plugin.
The reason the accuracy is so high is because when you shoot with a Gun Mettle weapon, it is not counted as a "missed shot". Thus you basically get 100% accuracy.
StatikI don't know if it's logs.tf or the curl extension but the uploads fail to often, i'd say 50% of the times and i've read curl has lots of bugs.
I have been using it for a long time without problems. Can you be more specific about the error? It logs upload errors to the SourceMod error logs, so you should be able to find them there.
StatikIs there a public repository of your plugins where a can make pull requests? I would love to see your plugin working with SteamTools instead of cURL.
Unfortunately the sources are only available in a zip file. I am using a private TFS repository as source control. However, I have seen other problems with cURL, so I would definitely like to have support for SteamTools. If you want to implement it, I would very much welcome that! Make SteamTools the default way of communication. Test it thoroughly, and send the source to me. :) You might want to add me on Steam for any clarifications.
TwiggyIt sometimes outputs strange stuff with loose cannon (damage labeled as grenade launcher and kills as lc), half zatoichi, shortstop, and some other unlocks i canr remember right now.
This is a bug in TFTrue.
KanecoSince you're answering some questions, I have noticed a bug with times and dpm calculations, for example if you join a pickup as sub but only play 5 mins the logs still calculate dpm and heals per minute and all the time stats as if you played the whole 30 mins. Is that a bug in tftrue as well or is it a logs.tf bugs?
Ex: http://logs.tf/645676?highlight=76561197991320838
This is a bug on logs.tf.
zoob should answer this, but I think I read somewhere it will be fixed in the next big logs.tf update (see screenshots of it on page 4 of this thread).
KanecoF2nahkakakkoneBlack Box damage is counted as RL damage, is that just because of how TF2 works or the site?No, it doesn't.
Check this log, for example.
If you look at C4's stats, you can see individual stats for Rocket Launcher and Black Box.
The LogsTF plugin isn't the only plugin uploading logs to logs.tf
Other plugins, like TFTrue, have a lot of bugs in this regard (incl. the Black Box bug). See ninjakalas in this log as an example.
So the only way to get real accurate stats for those kind of stuff is to have the official logs.tf plugin? Or otherwise we could ask for tftrue bugs to be ironed, I have encoutered this problem a few times but never guessed it was due to tftrue
Yes, TFTrue is logging the wrong weapon, so it must be fixed in TFTrue.
nahkakakkoneBlack Box damage is counted as RL damage, is that just because of how TF2 works or the site?
No, it doesn't.
Check this log, for example.
If you look at C4's stats, you can see individual stats for Rocket Launcher and Black Box.
The LogsTF plugin isn't the only plugin uploading logs to logs.tf
Other plugins, like TFTrue, have a lot of bugs in this regard (incl. the Black Box bug). See ninjakalas in this log as an example.
darkidThere seems to be a rounding issue with medstats, it counts 12/17=.70588 as 70% but 5/17=.29411 as 29%.
This is a bug on logs.tf - please post it on http://teamfortress.tv/thread/2934/?page=5
Senseiplx fix to - dont work for sm 1.7.0-dev+4871 linux
SM 1.7 is a development branch. You are not supposed to use it for production servers.
Instead, use the stable branch: SM 1.6
SenseiDont work with sourcemod 1.7.0.4886 linux
pls fix
Use the 1.6 branch.
Jopperi tried the logs.tf plugin apparently im getting this error
Logs.TF Uploader: Wrong log buffer
is the api key messed up?
No, that is not the issue.
This error should never happen, and I have never seen it happen before. Weird.
1) Does this happen all the time? (ie. have you tried restarting the server)
2) Which version of SourceMod is your server running? rcon sm version
3) Which version of MetaMod is your server running? rcon meta version
4) Have you compiled the plugin yourself? (you shouldn't - just checking)
SupStats2 v2.2.2
LogsTF v2.2.3
MedicStats v1.3.2
- Fixed plugins not working with the latest snapshot version of SourceMod
ComputerThe latest logs have, at least for my server, been lacking in damage and medic stats. I would assume that this is due to the newest update.
It turns out that the SourceMod Team are making a breaking change to a core function in SourceMod in the next version. So if you are running a snapshot build of SourceMod, supstats2 won't work.
For now, please use the latest stable version of SourceMod (1.6.1). I'll be working on a fix, such that supstats2 will work with the next version of SourceMod.
Thanks for making me aware of this.
That looks awesome! Been waiting for profile pages for a long time. Good job.
A quick suggestion: One of my main use cases of logs.tf is to find the log from the most recent match I played. Perhaps you could put your recent 1-3 matches on the front page for easier access?