Sebast1an

Best of luck.

please dont replace goldendunk with baserace.

no

Don't know if it's this one (can't test it myself) but atleast the readme in the download mentions a bunch of changes, including "1 more set of cliff climbing ropes". It also doesn't say anything about allies attacking so maybe this one is different from the one you have checked. https://et.splatterladder.com/?mod=mapinfo&idx=7249 Should give it a shot. The current one uploaded on the server is balanced horribly.

I appreciate you looking into it. I hope you will find a solution.

- Yes I'm sure it is only when someone connects. The demo will show you this. - Amount of people doesn't matter. Happened yesterday with full server, today the server was about half full. - Apparently also happens on ETL2, don't play there myself. - I believe it has been since the last update yes. Several weeks anyway, maybe even a month. - I don't know what is unusual... Here are the demo timestamps when someone connects (pay attention to the lagometer, some spikes are smaller than others): 11:38 11:16 10:15 8:50 8:34 lagspikes_supply.dm_84

The port makes no difference. Usually I connect using the ingame server menu but connecting by /connect makes no difference with the issue.

I'll try these suggestions later, will try to take a demo as well.

Are the constant lagspikes that have lasted for weeks now under investigation? Didn't see a post about them here so figured I'd make sure they are being dealt with. If you're not familiar with the issue, it seems like every time someone connects to the server there's a lagspike. On my lagometer it usually last 2-5 seconds but it gets annoying as the server is quite popular and people connect all the time. Took me a long while to figure out it wasn't my internet but the server causing it. I think kyuss pointed it out that it's everytime someone joins the server and never on any other time.

To my understanding, you are allowed to do anything except mortar in a case of multiple exits or a capturable spawn. On your example the axis have 2 spawnexits so it is allowed to mine/nade one and arty the other. And if allies played it really smart, they would mortar the corridor to the bank as well.

My take on the points brought up: - I don't think satchel was ever thought out to be something to do damage with. No opinion whether it should do more damage than now as I rarely see it used for that. And never use it myself. - I think most people won't rely on signal 4 to spot disguised enemies. Like ryzyk pointed out there's plenty of other ways. But removing the signal 4-way could do them some good. - Health regeneration is quite high but I don't see the issue. Most medics rely on the medpacks anyway and at level 3 they are plenty. - Not sure how half hp revives would play out on large scale. Would affect both sides and often attacking team will rely on full hp revives to get an engi through. As will the defending team to get a defuse. You are right, it is now a bit overpowered but on the other hand reviving is a skill as is gibbing. So I think the current system works fine. - Thing about SK areas is that spawnkilling is allowed with some weapons and some not. And wouldn't these red/yellow areas generally be the spawn anyway? I feel like everyone knows where the spawns are and that their location isn't the real issue. Would do no harm to mark them on the map but I'm not sure it would do any good either. - Agree, limit the rifles. 3 sounds reasonable for a 20man team - 2 might be a little low. - Agree, remove every version of goldrush. Or at least remove one from the main server.

Shouldn't be too difficult but I've never really felt the need to have it on public servers. Scrims sure but it's been a long time since I last did any.

Is it possible to change the enemy spawntime with a single command, at the beginning of every map? Or is it more complicated than that?

Fascinating read. It is a shame some people can't recognize the effort the ETL dev team puts in, without any compensation, on top of their real life obligations. But I guess everytime you are dealing in any form of customer service, some bad apples are always bound to show up to throw some insults. I feel like players need to get better at dealing with small issues, like a reset. I mean prestiges take some time to gather, as does SR, but in the end neither will really help your gameplay. Inconvenience for sure but really nothing more. Just be happy the server runs smooth and you're getting the frags. From my experience I think bugs that truly affect every day gameplay are rare and in the event of one it is usually promptly reported/fixed. Thank you for all your work Spyhawk and the rest of the dev team.

While I would also like to see the map back, there actually was a valid and understandable reason for deleting it. https://teammuppet.com/home/forums/topic/18135-etl1-map-poll-may/?tab=comments#comment-195722

This is a shame. Hope you guys can figure something out.

Thanks for the responses, I guess it's a bit more clear now. Actually I find this happens all the time on ET_Beach while spawnpassing as an allied player. You are bound to run into someone and quite regularly they will move to the spawn to avoid being killed. And as I've been warned for this before, I wanted to clarify it for myself now that there's a topic about sk rules. Your responses show a mixed opinion so I guess it's up to whoever is online at the time. Cheers.

Sorry if you answered this but I really won't read your book to find the answer. Figured it's easier to just ask. Is it allowed to kill a player in their spawn, knowing they have not spawned recently but are also not technically shooting back? For example: You see a player heal themselves in their spawn. Or you shoot at someone who runs to their spawn to heal and then dies there. Map scenario (Oasis): Axis player heals at the final spawn area and an allied player goes by towards the north gun. Sees the axis player through the gateway healing and kills him from a distance. Another map scenario would be ET_Beach: Axis player spawns near the transmitter, down the ladder. He leaves the spawn (but not the bunker) to look at the stairs and an allied player shoots him. Axis player doesn't shoot back but rather goes to the spawnpoint to heal but allied player follows and kills him inside the spawn. Are these scenarios within the rules or is it classified as spawnkill?

Honestly I don't see much of a improvement in average player skill happening even if everyone suddenly had this disabled. Sure their gameplay would become easier but no one gets good without running into using configs. And I dare say vast majority of players who are "good" have all this disabled in their configs. Makes no sense whatsoever to play with these effects if there's an alternative. But if you want to level the playing field, why not keep the cvar as it used to be but default it to 0 instead of 1? This way the explosion effects would have to be turned on if someone wants to play with them.

Basically explosions hide everything behind it. I used to have all this disabled so there were only a few tracers showing but it didn't really disturb your gameplay.

Well, to me the issue is that the way it used to be (while disabled), things like artillery and grenades had only the tracers of the explosion showing and it didn't disturb your gameplay at all if somewhere on your screen a support fire went off. No unnecessary explosion effects that you can't see through. Basically people have been playing with all the explosion effects disabled for years and now they can't be disabled anymore. I think most people like them disabled as it makes the game easier to play, not because their hardware sucks.

I don't think anyone would prefer to have them on given the choice. Game looks weird with all that added on the screen and as mentioned above, all explosives are plenty on the main server. Also it's ugly.

Best of luck. unrelated note: didn't know there's any of the competitive ET left in the game. Glad to see atleast some of it is.

Hey, stay safe.

Would it be possible to default the cg_bobbing value to 0? Quite a few people were asking about the crosshair moving yesterday and everyone got their issues fixed by changing the value to 0. Personally I didn't even realize it's a cvar issue, figured it was something you guys added in the update. But it sure is annoying to play with.