Hmm. Is it possible to show us how you would do your logs?

It's not normal to execute a vocal player on D2, unless they were talking nonsense, which I doubt you were doing.

About warping the right people, I don't know what happened in your case so I cannot comment either.
Everyone has their idea of who is worthy of being healed/guarded.
Players say that to me when I don't heal an outted prince or important BD class (even if the person who outted is not proven).
Players also have something against healers/knights who choose to target the king, even though the king is likely to attacked by Drunk redirection and Pretenders. Maybe it's because visiting kings is more difficult for observers to confirm logs or that players do not trust kings as witnesses to your ability in action.
I sometimes cry out: "He must be evil because he's not healing this guy" because the evil one is me and I want to get the other guy killed.

People will also say 'bad logs' if the healer/knight has not succeeded in saving a player in certain number of nights. After all, healer/knight logs are easily faked.

Well As a NK sorc I was aware of a healer (I attack someone and they didn't die) so when i bomb the butler mystic and prince (he was outed) we up the chrono because the chrono didn't TW the prince when he was outed

most common reason (imo) for writing this, is, if they ♥♥♥♥♥♥ up and exe'd the wrong one. But to cover their mistake they rather blame your logs.

well if you type something like "healing 12" when you are chrono then its not good logs even though youd be technically correct. Also bad logs if you dont say "didnt heal/didnt delay" as chrono because you need to say if you saved someone

There's also a giant chance that it's the EVIL guys that are shouting "bad logs" to get you killed on purpose, whether they are good logs or bad? ;) the more you play the game, the more you'll realize that almost nothing is as it seems when you first start playing.

Don't take it personally: Anyone against you is going to twist & manipulate your words -- AND your logs.

Learn the game and ask questions @ https://discord.gg/tol

That being said, the tutorial is not being updated. The gap between the new comers and experience players is huge. Hence please update the tutorial, show some good example of how good logs should look like as well. :)

some people are sticklers for nice looking logs but keep in mind that some people will be evils who have figured you are very likely a REAL chrono and who will want you executed regardless, they will throw gasoline on the fire and try to make you seem bad, they will disrupt and distort, and then they will blame others/you for it. This is part of trying to win the game sometimes as evils.

So, good logs are important but you may have run into some players taking advantage of the situation also to purposefully get you killed.

Originally posted by probo_:

some people are sticklers for nice looking logs but keep in mind that some people will be evils who have figured you are very likely a REAL chrono and who will want you executed regardless, they will throw gasoline on the fire and try to make you seem bad, they will disrupt and distort, and then they will blame others/you for it. This is part of trying to win the game sometimes as evils.

So, good logs are important but you may have run into some players taking advantage of the situation also to purposefully get you killed.

That's true in this one context. Most of time i've read this (bad / ♥♥♥♥♥♥ etc. logs), it happened post-execution, when BD members realized that they accidently exe'd a buddy. i guess they just feel better about their mistake with throwing those words into the realm. Some kind of forced justification (and pretty pathetic).

Originally posted by Extra Big Meatball with Cheese:

Most commonly sighted reason I'm getting for being executed is '♥♥♥♥ logs', even when my logs are real and detailed. I think they're saying I'm not using the same acronyms people who have been playing for 400+ hours use? But this has happened to me like 5 times today; executed as BD for 'bad logs'.

There's a log-making guide on steam if it's your logging itsef that's the problem.
It's not ideal (for example it uses Day logging instead of putting day actions on the same line as night actions) but it could still help I guess.

Originally posted by Extra Big Meatball with Cheese:

When I play Chronomancer I get a lot of 'WHY ARE YOU TWing the WRONG PEOPLE" in a game where nobody seems to be confirmed or has called logs. Like, Day 2 execution or time warping a vocal player. Huh?

This is ToL, not ToS, if you're going to wait for people to get confirmed to heal them you'll barely ever heal anyone. If someone CLAIMED an important role that alone is reason enough to heal them. Also look for the TYPES of reveals. Most likely real are the ones that out with information, even when that information isn't an accusation. For example a phys that announces an exhume is a lot more likely to be real than a phys that outed as a part of vfr routine.

As for “vocal” players, the sooner you get rid of the “vocal=good, silent=bad” assumption the better. It's about as silly as believing in “I never lie” statement. Evil has about as many reasons to be vocal as BD, maybe even more. Look at actual info they give, and more importantly if they ever gave any at all. If anything, people playing cpnt. obvious with their constant “this could be fool” “this is the 2nd phys claim”, “this was a d1 alch claim” are the ones to be suspicious about. The more you're trying to keep up with the info flow the LESS time you have to talk.

Of cause there ARE people that freeze up and never talk when they are evil, but those are the worse players, and the ones you should be on the lookout for are the better ones.

P.S. While I've seen some false “bad logs” accusations most of them are actually on point. However without you giving any examples it's impossible to say whether yours were good or bad.
Either give US detailed examples, or ask people in-game why they called your logs for that game bad.

P.P.S. Don't try actually behaving in-game the way uncolober described. If BD that game are decent this kind of behavior gets you a fast loss. While he's correct on the principle of it, the actual implementation needs to be better than that. Unless the actual BD are bad. But in that case the original point still holds – it's the collective BD stupidity that got you executed.