Jump to content
Forum Shutdown 28/7/2023 Read more... ×

Hanse77SWE

Players
  • Content Сount

    1,518
  • Joined

  • Last visited

  • Battles

    28995
  • Clan

    [INTRO]

Everything posted by Hanse77SWE

  1. Hanse77SWE

    Weekly Combat Missions: Lunar New Year

    Well that was a big fat lie. I've opened all eight and no ship and no perma-cammo.
  2. Hanse77SWE

    I wonder about this spotter plane design

    I've read somewhere that the italian navy used landbased planes that returned to an airfield or ditched at sea. Since most of the mediterranean is in range from an itailan air base most of the war this might work well enough to skip building specific floatplanes.
  3. Hanse77SWE

    About disciplinary penalties!

    No he wasn't. With your definition anyone that is within 150% of the torpedo range in a 360 degree field is in range and good luck working like that. Same here. I don't hit teammates every time I fire torps. So...never fire torps then? WG doesn't disagree. They just use an automated system that can't separate between intent and result ( and it seems like alot of the playerbase can't either) because they know if someone should sit down and "judge" every time FF happens they would an herculean task to infront of them and they don't want that.
  4. Hanse77SWE

    How to lose Karma

    Losing karma is the easiest thing there is. You don't have to do anything. In fact that's one way to do it. "Damned if I do, damned if I don't" - Bart Simpson
  5. Hanse77SWE

    About disciplinary penalties!

    No ,he's not. So, "Never" then? Why doesn't WG just remove torps from the game then? A ship can be 20 km away but if he really wants to he can still be hit by a 12 km torp. This was co-op. Wrong, in two ways. I say "don't blame anyone unless it is obvious." We can't say "Its always the shooters fault" because, as you just said, we don't know what the rest of the players will do. "Never say never" and all that... Sometimes it's the shooters fault, sometimes it's not. We can't tell without all the evidence. In this case it's not a couple of seconds. As I said, 55 seconds of run time and he still got hit. I'm sorry guys but you are never going to change my mind on this. There is no way in hell we can pin the blame on the shooter every time. It's statistically impossible no matter how you twist and turn. If it can be shown one time, just one time, that it wasn't the shooters fault (and you emitted it yourself that this happens) then whole "Always" bit goes out the window.
  6. Hanse77SWE

    About disciplinary penalties!

    Because if I take time to type in chatt and wait for a response, then the opportunity would be gone. Do you ask your team if it's OK every time you shoot torps? Because I've never seen it done in over 13k battles. I fired to the NW. He's to the north. He is in no danger from me where he is. He did just that. But he didn't run from them. He ran towards them. But I should read his? I didn't use the word "often". I was in the first line. There are no green ships between me and my target. He was hit 3-4 km behind the target ship. The torps run for 32 seconds. Then one hit the target. Then they remaining two run for 23 more seconds before he's hit. He is not between me and my target. The ship marked in the SS is not the ship I'm shooting at. Replay bug.
  7. Hanse77SWE

    About disciplinary penalties!

    Oh but the signs are there, and they looks like this: or this: Look around you. Where are his guns pointing? Could he be shooting at those ships over there? Does that cruiser have torps and is the enemy in range of those torps? Then perhaps I should stay out of his line of fire. Or even better: Always make an effort to stay out of your team-mates line-of-fire. You are not alone on the playingfield so stop acting like you are. Blocking your temmates shots is not a productive way to play because it reduces the efficiency of the team as a whole. Where I live the is a law that cars must stop at zebra-crossings. IF the pedestrians clearly show that they intend to cross the road. There's been plenty of case where old ladies have been run over and it turns out that they just stept out onto the road without any warning. (I have a friend that ran over and killed an old man on a moped. My friend was acquitted because the man turned without warning and without giving a signal. He was also not wearing a helmet.) I had a game today where I was sitting in a smokescreen in a DD shooting at an enemy 3 km away. Then this idiot in a Hipper drives inbetween me and my target. 3 km! Just so he could get his torps away. I had to hold my fire of course because I knew that even if he was doing the stupid and wrong thing, I would get the blame for it. Moral of the story: Sometimes people are just "rectums". And how many times have we seen some jerk on our team drive up next to an enemy that everybody is shooting at just to get hit by FF? Now your team have to stop shooting because of that guy and the enemy get a second chance! I remember once were I had the perfect broadside of a cruiser. Just one pull of the trigger and he'd be dead. But no, a DD on my team had this bright idea that he should ram instead. Result: I had to hold my fire, the cruiser kills the DD and now the DDs wreck covers the cruiser citadel and I can't kill him. Moral of the story: You can't blame your team when you place yourself infront of the bullseye. Once I was playing a BB. Low tier, slow, so I knew there were no risk of me running into someone else. Aiming at the enemy, shooting, all is fine. Then I hear "Don't fire at your allies!" and I was "WTF!?" Look down. A fast cruiser, from behind, drives infront of my whole broadside that is flaming with every gun I have. (This was before the change to the secondaries, they could still do damage to friendlies.) Moral of the story: Stay away from the side of you teammates that are turned towards the enemy. And if you really have to, make sure that you're only "passing through". Pehaps honk your horn to let him know you are there. Long time ago I was grinding the Iowa. Suddenly an enemy cruiser pops out from behind an iceberg not far from me. Problem is that between me and him is a friendly Atago. I aim and I can clearly see that if I fire, I'm gonna clip the superstructure of the Atago but I have a really good chance to kill that cruiser before he gets his torps of. I have to act fast. I shoot! My shells clip the Atago and kills the cruiser. I type in chatt: "Sorry, but I had to take the shot." The Atago responds: "NP, I would have done the same." Moral of the story: Sometimes you have to take risks to avoid something worse. Another time I actually TK a guy on my team. Hit him with one 105 mm shell just as he was about to burn to death. I said I was sorry but he admitted that he had no clue to where he was going and turned into my shots. I knew where he was but his turn came without warning. (105:s fire fast so there was literally a rainbow from me to my target. Hard to miss.) Moral of the story: Sometimes you can't predict what your teammates will do. Have a look at this: This screenshot is taken just as I fire a set of torps. I fire them at that cruiser in F7 that is going SE. The torps have a range of 8.2 km and a topspeed of 59 kts. One torp hits the cruiser and one will go on and hit that DD in E8. The time it takes from I fire to he gets hit, is 55 seconds. Almost a minute. Visible to him all the time. The last 15 seconds they are in his line-of-sight as he shoots at the cruiser that just ate my torp. He is looking in the direction of the torps, fully visible torps, and yet he can't avoid them. I have a vid of this and in that vid you can see that he's actually turning into the torp. Thing is: I saw him before I fired. I saw him 6 km away (3/4 of my torps max distance) and going away from me, in behind an island. I did some quick math and I thought to myself "With that course and speed, he'll be safe." So I fire. I fire knowing that I couldn't hit him. But he had other plans. He chased that torpedo, he wanted to get hit knowing that I would turn pink. This wasn't a case of "He's-in-my-line-of-fire-but-I-don't-care." His actions took him to that torp, not mine. He steered towards it, not the other way around. He stept infront of the oncoming train but still it's the traindriver that gets the blame. Moral of the story: Sometimes it doesn't matter how carefull you are or how many precautions you take. Murphy's law will step in and something will go wrong. Look, I'm not saying that everybody should be able to fire torps willy-nilly without responsibility, but we can't always say that "Mr. X is always guilty when Mr. Y gets hurt" especially if Mr. Y has been acting like a moron. Sometimes on pupose. We can't asume that every time FF is taken that it's the shooters fault. We have to look at the whole situation. It's called "The benefit of the doubt." Therefore it is wrong by us to claim that it is always the shooters fault. We can never say that one guy is 100% responsible for everything 100% of the time if he doesn't control 100% of the environment. And guess what? No one does! Conclusion: Friendly Fire is NOT an absolute truth! ( https://simple.wikipedia.org/wiki/Absolute_truth )
  8. Hanse77SWE

    About disciplinary penalties!

    No. But if you saw this sign: Would you be without fault for going past it?
  9. Hanse77SWE

    New gameplay mode

    I agree that a new game mode is needed. Can make many sugestions but I'm not interested in talking to deaf ears.
  10. Hanse77SWE

    Friendly Fire- why still present in game?

    This. As Bart Simpson says: "Damned if I do, damned if I don't." If I fire I might hit a friendly and if I don't fire I might miss out on that kill/damage/torphit-ribbon/whatever that I've been working on for the last couple of hours. It's frustrating to see that opportunity slip away all because of someone else. There is a reason why line-tactics were used. It's so that everybody stay in their places and no one goes into the line-of-fire of someone else. It's a shared resonsibility. I keep an eye down my line of fire and stop shooting if a friendly drifts into it and everybody else, at least try to, stay out of my line of fire. Now, the world isn't perfect and sh1t happens but let us at least make an joint effort to keep the sh1t away for as long as we can?
  11. Hanse77SWE

    Is there any point?

    I started out as a one-man-clan. Today we have 34 members. It's just for the bonuses and we don't care about CB and such. And yes, we are open to new members.
  12. Hanse77SWE

    About disciplinary penalties!

    Many say that a shooter on a range always have the responsibility. That is wrong. Bystanders have the responsibility to stay off the firing range.
  13. Hanse77SWE

    Friendly Fire- why still present in game?

    The guys shooting up his teammate should be punished but why should the guy geting shot at lose his HP? Register the hits and warn the shooter but leave the victims healthpool alone. One possible downside could be that trolls will "catch" or block friendly shots and torps so they themselves can get the kill. Question is: Which is the lesser of two evils?
  14. Hanse77SWE

    0.9.0 - British cruisers: Early Access

    YES!!! I have that feeling!
  15. Hanse77SWE

    0.9.0 - British cruisers: Early Access

    Yes it says "If you receive a ship that you already have in your Port, you will get compensation in the form of credits, a Commander, and Port slot." but it doesn't say that the two "lotterys" run independently.
  16. Hanse77SWE

    weird sound

    Nope I have vids that go back two years and the bell is there.
  17. Hanse77SWE

    0.9.0 - British cruisers: Early Access

    Bummer. And this means that the chances to get ships is even worse since the the two "lotterys" that don't "corporate". You don't gain anything by using both.
  18. Hanse77SWE

    0.9.0 - British cruisers: Early Access

    @YabbaCoe I don't know if this is the right place but here we go... I got the Hawkins in a gold bundle. Fine, no problem there. But today when I used tokens to open a bundle there it showed that the next bundle is....the Hawkins! Can I get the same ship twice or go I get credits or a cookie or what?
  19. Hanse77SWE

    weird sound

    Replays use the setting you have now. A vid made 18 months ago used the current settings. And how do you watch a two year old replay? They stop working when a new patch comes out. All I know is that the bell isn't new and I haven't changed my audio-settings for years.
  20. Hanse77SWE

    Karma

    Had a good game tonight. Talked to my team, we worked together and won. I gave compliments and got one myself. Fine. Two games before that I ended up second on team in XP. Not talk in chatt, no team-damage. Got -1. I have no idea what I did "wrong". That's the downside with this system. Since I don't know what I did "wrong" then I can't stop doing "it". Whatever "it" is. Just keep on playing as best you can and rejoyce over the compliment you get. If you get reported and you know why, fine. If you don't know why, just move on.
  21. Hanse77SWE

    Pr event appears to be a success for WG

    When I logged out just before the end 166 players had reached the Hall of Fame on EU. Also, you don't have to do all seven directives to get the PR for free. If you were fast enough you could do it in six. For me, I spent less money than a "regular" Xmas and I still got her. So I'm satisfied.
  22. Hanse77SWE

    weird sound

    I just checked a video of me playing in june 2018 and the bell is there so a least one and a half year. In fact, iirc it's always been there.
  23. Hanse77SWE

    A small psychological insight for you WG

    I've opened 13 or 14 bundles and not a single ship so far.
  24. Hanse77SWE

    Cap buoys invisible since latest patch

    Played two minutes ago. No problem.
  25. Hanse77SWE

    6 t8 carriers one match possible, apparently

    Always hardcap of 1 in co-op.
×