Sebast1an

Windows 10 Pro (10.0.19045) 64bit ET Legacy v2.81.1 win-x64 Mar 12

Hey, my screen keeps freezing. Meaning I can hear the game and play (judging by sounds) but the screen freezes - only restarting the game helps. Happens most on Decay and Venice for some reason. Could not play 5sec on Venice yesterday without the screen freezing. Playing on the latest Legacy client and reinstall did not help. Any ideas?

Disabling the axis spawn nearest to the radio would create a huge bottleneck on the ladder. I imagine it would only take 2-3 allied players to completely block any axis coming up the ladder and after that, axis have no chance to defend the objective or radio from either spawn available. As for the flag, I agree it should be made a permanent spawn after a certain time. But I'm not sure if most of the sk would still be allowed as there technically is another exit available (towards the beach)? Of course permanent spawn means axis could no longer shoot right into the spawn so that's still something.

When thinking about the situation when allies have possession of only 1 gold crate while the other is still on the ship, the axis defence tends to be split up between the ship and the truck. If allies deliver the first crate, from there on axis will be on a backfoot and won't have an effective defence on either spot anymore and it's easier for allies to control and win. I think the whole map is so challenging for allies until that point though that they deserve that little extra time bonus to help them finish strong.

I find the suggestions in the opening post quite reasonable, however the discussion has drifted towards more drastic changes and we all know nothing of the kind will be implemented on such a successful server. Taking a few nades off or changing spawntimes maybe but bigger changes in classes seem unlikely to me. People prefer different things, as annoying as they may be, and that's their prerogative. Medics want to limit nades and heavy, engis want to limit medics... Quite logical, however the suggested changes depend on who you ask so there's really no way to please everyone.

1203 words about putting people to spec. Would love to see a topic about you getting banned for example - not that you should be.

Stealing it will be impossible if axis can just damage it over and over.

If axis get stuck on the first part, 3 minutes less of that is always welcome in my opinion. 6+6 addition instead of 5+5 isn't unreasonable either.

One easy way to figure out the approximate percentage amongst players is to use /players ingame. It will display their client version amongst other information. But anyway, I use ETL.

I'm sure you were warned beforehand and took no action other than continue spawnkilling. For future reference, it helps to read the warning messages (and also the spawnkilling rules while you're at it).

I feel like if you can't put the changes into one sentence and still make sense, it is too much of a change.

If I played as a rambomedic, I would not trade the ability to heal myself for +16hp and hp regeneration. Healing oneself is what makes rambos so powerful, as most of the time they will be able to win any given 1v1 and even if not, selfhealing will give them another chance at it. Not to mention after you win your duel, you can heal yourself and go on to the next. With soldier class, you're just stuck with the low hp and are basically useless in regards of the next duel. Health regeneration at low hp, say it's 6hp/sec at 30hp, to regenerate the remaining hp takes 21 seconds. Might as well respawn at that point. This topic about medics being overpowered has been brought up about 600 times already. Usually people don't like making changes to it so I'm quite confident this time is no different.

I might have argued my point poorly but nevertheless I didn't mean people should be kicked for inactivity after 20 minutes regardless of server population. Kicking people for inactivity when the server isn't full sounds horrible. One helpful command for admins would be something that prints all the specs and their inactivity times into the console so it's easy to pick out the AFK's. Just confirm by asking before !kick.

In my opinion there is no reason to set the time for inactivity for as low as 5-10 minutes. When the server is full, there are usually people who have been in spec for several maps in a row. Instead, I would suggest a time of 15-20 minutes. If you're AFK for longer than that, it is no longer a "brb" and players would most likely understand getting kicked after that. Getting kicked over a 5min AFK would annoy me at least. If the game can't find anyone worthy of a kick, then admins could step in to ease the situation. One other thing that came to mind was a popup in the chat, telling people to "consider joining the game as the server is full". This would prompt admins to act quicker as well, as it is not always obvious that the server is indeed full with the private slots and whatnot. Also could be a popup for the admins only, so the chat doesn't get spammed with it for the regular players who can't do anything about it.

It is a difficult topic, especially now that the war is happening in Europe. As you mentioned, no one bats an eye anymore when it's not in Europe since it isn't relevant to them. Myself included. Looking forward to seeing how TM decides to handle this one. Banning support for Ukraine seems dumb but on the other hand, supporting Russia should be allowed as well even if most people disagree with Russia's actions these past weeks. Suggestion for solution: let players colour their names all they want but any political discussion or changing their names to support either side is prohibited. If players wish to discuss, there is a topic about the war on the forum so direct them here in that case.

Don't punish individuals ingame or in real life over something they have no control over.

Oh damn hahaha

Exploitable yes but apart from a select few, people don't usually realize how easy it is to hold command posts in general. Also, I have never seen anyone hold the command post like this for very long because eventually your teammates will build it if you don't. As for Battery: the map is over if allies capture the command post while axis still hold the flag. Should not make the map any easier in my opinion. It is by no means impossible as it is.

Never really understood the issue with selfkills but if any changes were made, they should be towards counting selfkills as kills/deaths and not anything related to delays. Pretty sure nothing will change though, people don't usually selfkill to avoid deaths so it'll keep happening.

Me too but that's a separate issue. Ideally the working principle is good in my opinion.

I think it is fair as it is. Picks the last one to join a team after a certain time. Simple.

I don't think medics with 2 nades are the main issue. Engineers with a rifle have 16 nades to play with which seems excessive in my opinion. If possible, I'd give them 6 for rifle and 4 regular as a start.

Hello and welcome.

Your maths is a little elementary in this case. You assume it is as likely to capture the flag on any given second when I would argue that it is less likely if allies have just respawned and more likely the more allies are dead. But of course this is difficult to calculate accurately without sufficient data, seeing there are so many variables to consider. I think you are both right. But as Ande said, to me the best solution would be to just experiment with it. I think you can't really go wrong here with a 2sec adjustment on either side.

Spawntimes and probabilities aside, many maps would be better if they skipped the first part entirely. I hope you can agree on some solution to make Caen a bit more balanced in the beginning.