test content
Logo
What is the Arc Client?
Install Arc
Log trash
eragon1392
Member Posts: 5 Arc User
With todays patch cryptic has changed the log structure of sto. After every reboot, sto creates new logfiles with different names once per hour(up to 7). through this change sto generate a lot of datatrash in the folder. this make it way more difficult to select the logfile with programs like combatlog reader with an automated function. it would be good if this could be reversed.
0
This discussion has been closed.
Comments
That sucks.
did you stop to think maybe this was done deliberately to discourage the use of parsers?
#LegalizeAwoo
A normie goes "Oh, what's this?"
An otaku goes "UwU, what's this?"
A furry goes "OwO, what's this?"
A werewolf goes "Awoo, what's this?"
"It's nothing personal, I just don't feel like I've gotten to know a person until I've sniffed their crotch."
"We said 'no' to Mr. Curiosity. We're not home. Curiosity is not welcome, it is not to be invited in. Curiosity...is bad. It gets you in trouble, it gets you killed, and more importantly...it makes you poor!"
I sometimes wonder whether certain Devs do nothing but finding ways to try and sabotage their own game!?
I have just to say that this is really anoying and I don't understand why this has been changed.
"Another thing is, that Cryptic changed something with STO’s CombatLog file. You have to manually select the new combatlog. It’s not anymore CombatLog.log, it’s now combatlog_date_time.log (e.g. “Combatlog_2016-02-25_18-00-00.Log”) and you have to select the newest one. We are investigating that and working on a fix. Please be patient."
I bet they can come up with something to reconstruct the full name from something that takes a base path + base name + date. Or just use the 'Last Modified' file, LOL.
Thank you.
I understand the rationale behind rotating logs and all; but I manually (via parser) purge my logs on start-up anyway; so the option is appreciated.
Other comments not needed.
I hope they fix this for the players to whom this is important.
Huh? By momentarily (and for all I care, permanently) breaking some 3rd-party log parsers, Cryptic is sabotaging its own game? When did maintaining a file-naming format and interior log format (should that ever need to change) become an obligation?
Rather, when did breaking the log mechanism become a necessity?!
Anyway, it's all moot now, as the Dev already said they'll add an option to disable it (thus de facto acknowledging parsing is an actual thing in this game, and they kinda broke something ppl were using).
this year? next year? did you know you were wrecking the parsers when you decided to do this? was it a surprise? why did you do it? do you care?
Rotating logs is a normal thing (especially on servers). So, I understand the rationale behind this change (long logs can cause lag on ppl with crappy machines). But parsers really need the data, so this was obviously not well thought-thru. But the way the Dev said it, I think he meant that the option to disable this rotation 'feature' will be implemented already before the next official Holodeck patch (or maybe a week later; not months or years, at least).
I don't work for Cryptic, but I am a lead software developer. No, we do not make changes just to ruin your life. Yes, there are reasons behind us making changes. Yes, we do think about the consequences of a change but can't always predict all of them in advance.
I'd guess the log code needs to be updated often in order to be able to, y'know, log things. If a new thing is added, people expect that thing to show up in the logs. That doesn't happen through dark magic, it happens through developers.
Who was attacking the Dev?!
It doesn't take a true genius to realize that rotating logs may start to break parsers. :P This isn't higher math.
A good Developer should, IMHO, also live by the Hippocratic Oath: "Above all, do not harm!" Aka, if you haven't tested it enough, or really haven't thought it thru yet, don't deploy!
Also, I do not for the life of me get what 'If a new thing is added, people expect that thing to show up in the logs' has got anything to do with the meta change of how logs are generated now. *boggle*
cool beans, thx for the update
we want to change the log system"
"that might ruin things for a lot of our customers"
"who?"
"you know the players the customers"
"who?'............"sorry not ringing any bells here, as I was saying we need to change the file naming system"
"shall we phase it in after letting the players/customers get their parsers updated or something?"
"who???"
its just not handling the data as it was. so as long as you are /combatlog 1 it will still be recording all the data, it will just be recording it to chronologically ordered log files. it will just mean that on some runs, you will need to wait till you complete, before being able to point your parser at the most recent file. at most, an extra few moments to pull your run up, and possibly not having any live data for a while as you are parsing, but that's no reason to get ones knackers in a twist now is it?
5 forum posts and nothing but complaints and personal attacks. You truly are a wonderful member of this community.
And agreed with what davefenestrator said. You should be happy a Dev takes the time to answer this. Most of them rather post on other sites and I'm beginning to understand why...
For some people it apparantly is. Which is pretty sad of course.
I mean, people even claim here that they're breaking their own game, while it has been pointed out that they have no obligation to allow third party software to do its thing.
Edit: Don't expect too much reason when DPS is involved
there is much truth in that wee statement lol
The CombatLog stuff isn't even officially supported. :P Doesn't mean one can't wonder as to why on Earth they broke it (yes, you can break something, even when you're not obligated to provide the service), full-well knowing this is going to affect all their parsers.
Anyway, like I said, a Dev came out, to quickly say they realize it's apparently an issue for people, and that they will fix it shortly (with a disable option), for which I thanked him.
Nothing to see here; please, move on.
Nah. Rather, especially when people want to parse now more than ever (to test the effects of new Tribble skill revamp), I'd say the log change came at a most in-opportune time.
Hm yeah that's true. I hadn't considered that. Though it's still possible to compare builds, by checking tool tips, skill stats etc.
While parses usually provide a more complete picture, I generally prefer to judge my own builds by checking how fast I can take down certain enemies.
If you do it in a standardised environment like a Foundry mission, those few extra clicks for each parse shouldn't be really a problem anyway