Attention to mappers and testers.

[laxa]

Hello everyone.

I really enjoy when maps have a nice gameplay.
And I feel, a lots of mappers / testers forget something that is quite important to me.

The freeze entitie is only for drag parts, not to increase your time by 3 seconds each time you have to go through it.

That's why I would point out that the unfreeze entitie is really important. You should use it anytime you can't unfreeze your partner.
On solo maps, you can use too freeze on switch layer with a freeze of 1 second.

I see some maps with freeze with teleporter, and I feel like it's really terrible.

So, that's my 2 cents, I really hope everyone take into consideration this.

[Lady Saavik]

You are right. Sometimes I fix maps and add few unfreezes or suggest it on screenshots.

Sometimes it makes sense to have unfreezes when you get teleported back, especially in parts where you need many tries.

[Nigel]

I totaly agree this is horrible when you play a map with tele freeze ! this feeling that you'r wasting your time everytime that you restart the part is .. wtf.
I rage quit all maps with that.

[deen]

On the other hand, the freeze increases your time, so people who can do the part in 1 try have an advantage, while just rushing through the part and getting frozen 3 times gets you punished.

[laxa]

They already get punished by failing the part, so being freezed is more annoying and useless than anything else.
And if you want to punish noobs for being noobs, you can use the entitie you created that increase time !

[Broken]

On the other hand, the freeze increases your time, so people who can do the part in 1 try have an advantage, while just rushing through the part and getting frozen 3 times gets you punished.

But yea unfreezes are nice.

[Anqel]

It should be mapper's decision to use unfreeze or not.
Sometimes a mapper has a reason for not using unfreeze.
There is a simple reason for it. If they would be unfreezed directly they could run and use speed.
Or they could fail because they still hold a key. And there are many other advantages they should not use maybe.
So I don't like the idea.

[laxa]

It should be mapper's decision to use unfreeze or not.

Yeah maybe it's mapper decision.
But if you make a map full of freeze and no unfreeze at all, players will dislike it and won't play it.
Is this really a good decision then ?

Sometimes a mapper has a reason for not using unfreeze.

Not really.
As said previously, there is an entitie for that.
You can increase the time of a runner if he fails. But I don't know why you should do such a thing since failing is loosing time.

There is a simple reason for it. If they would be unfreezed directly they could run and use speed.

Depends on the context, if you talk about teleporters, use red one, no more speed after being teleported.

Or they could fail because they still hold a key. And there are many other advantages they should not use maybe.

Well, their fault, you have to be reactive in teeworlds. And if you map correctly, you know there is unfreeze.
If you make it a standart for all maps (which should be the case), then they know exactly how to behave.


Don't forget that I am saying that to improve the overall gameplay of all new maps.
I personally hate to wait 3 seconds for no reason at all.

[imp]

There are so many annoying parts which take forever to finish.. unfreezers are the last thing I worry about

[Anqel]

U just need to wait 3 seconds if u fail laxa =P
Yeah maybe the people will dislike the map and won't play it.
So that mapper knows ok, next time I need to do something different.
Don't understand me wrong. I am using unfreeze nearly everywhere, but simetimes i don't when i think it's better without.
And that it's mappers decision should be stay. And I totally hate when anybody changes parts in my maps.

For example purple panic 2. There was a part changed by anyone because he/she thought it was "luck" to do that right.
But that was no luck. U can do it every single time u try. Just a simple trick. So somethimes a mapper just know why he is doing something and it should not be changed.