Teeworlds - bridge

Teeworlds

IRC / bridge

One-way IRC channel bridge. If you want to be able to send messages to IRC, contact @Dune or @heinrich5991. https://www.teeworlds.com/?page=docs&wiki=rules/irc_rules

Between 2019-10-10 00:00:00Z and 2019-10-11 00:00:00Z

Dune : you felt wrong, and I might did too, the pic was to illustrate a wider view while being playable and nice (basically 2 times larger)

14:17

and since the pic is static, I added that It does nt show the whole map thanks to network clipping that mitigates the "cheat"

14:18

finally, this is exactly the example of what you call a stable dynamic camera in all directions

14:19

iirc, with a zoom around 1.4, the screen starts to be bigger than the clipped view

14:20

but it is a huge addition in terms of information on the map since you can see player arriving farther, and then anticipate a bit more

yes, all that I agree with

14:21

but I don't understand where your point is, then

14:21

it seems it was not meant as a counterpoint, at least?

I was adding elements :)

ah, my bad then :)

it was not that clear from my messages ^^'

so what's your opinion on the current state of FoV?

current is fine by me, I played with dynamic camera as a beginner and I played without now while being beaten by players using it

14:27

since any player can use dynamic camera to get maximum information, everyone are equals

14:27

we can't prevent all cheats any way

this isn't really about dynamic camera though to me

or we can adapt network clip to dynamic camera, not sure it is a good idea

14:28

about the possibility for race/etc, it could be an addition

14:29

but, it is part of the game not to see everything on the map

yeah of course

14:29

players got to a speed where rocket jumping without knowing the map well kinda sucks

the map is discovered, then the player learns the details

14:30

and finally can play almost without looking the screen

dyn cam is a plain cheat imho

14:38

or rather changing the camera to fixed is self applying a malus to oneself. dyn just feels so bad that i cant stand it

I have wet dreams of player friendlier mechanics. Bullet reloading could be less tedious and demanding as well imho :/

main grudge i have is that the game rewards defensive nade spam way too much

14:43

past a certain skill level it is down to luck to capture a flag carrier

14:45

this may not be an issue in competitive 3v3 or 5v5 with coordinated teamplay but i dont think teeworlds has the luxury of catering to that crowd :P

yeah well ctf5 feels like "play TDM in the middle part and shoot at the flagger if you randomly meet him"

14:46

dying from grenades thrown back gets old after 4min of killing no one

yeah they need to stumble into you while you have full armor and a shotgun

exactly yeah

14:47

does not apply if you're in the very top of the players though, where you can outmove the flagger

i think the nades need a serious spamability nerf

14:48

you cant outmove the flagger 1v1

14:48

he has free movement while the chaser doesnt thanks to nade area denial

I guess you're supposed to gang up on flaggers and not be 1v1

just a thought, maybe the flagger could lose armor over time. e.g. after 15s you lose 1 armor/5s

14:54

with 10hp you are still somewhat beefy, but not an always 20hp juggernaut that always manages to slip away

CTDFC, capture the dying flag carrier

nah not dying. his hp is unaffected

CTNFC then

14:55

the nake(ing) flag carrier

nade(ing)*

maybe, kill rather than Capture, KtnFC

14:57

ending to king of the hill

14:58

CTF is a team based gameplay though

14:58

the 1o1 frustration is something that should motivate player to play with team

15:00

I admit that I'm chassing the flag carrier most of the time, and alone

day: in some games the flagger cannot acquire armor

yeah it is certainly a map issue too

15:01

and i admit i mostly play ctf5 because theres nothing else

but the frustrating part is not the nading of the flag carrier, it is the instant I succeed to damage almost to death the flag carrier and some random player kill me defending it's team

there are issues with juggernaut-flagger-man in teamplay as well afaik, with games that last forever because flaggers don't die

ctf is played because it's easy to run away, carrier goal :p

15:02

*ctf5

really?

even a newbie can capture if lucky enough

15:04

and there are huge corridors to get high speed

15:05

on ctf5, there is 4 different escape routes when you get the flag

15:05

while at most 2 on others vanilla maps

ctf1 is quite hilarious too. you just stay top side and spam nades into the abyss beneath you while sitting on a fat stack of hearts/armor :P

15:08

the revamped ctf1 map was a bit better in that regard imho, but noones hosting/ playing it \o/

this doesn't work with few players

15:09

I don't know about the revamped ctf1

as i said, im mainly concerned about the pub game quality. where the 1vs1 situation frequently occurs over long periodes of time

rand: i thought it was just because it's the only map that uses new mechanics like unhookables and death pits, and that it makes it fun

the unhookable thing is super annoying too. flagger rocket jumps to the top, chaser cant follow because he can just throw nades down the wall

the error is to follow him, you cannot do better on 1v1 in ctf5 but this map is not suited for 1vs1 anyway

15:17

(and, I'm not sure ctf is playable in 1v1)

first aimbot spottet on zCatch Grenade

17:45

nice

is the person around who had that problem https://github.com/teeworlds/teeworlds/issues/2263 ?

Error while compiling official Teeworlds (last source-release 0.7....

I get followed error while compiling teeworlds with bam5 client: [1/2] [1] c++ src/engine/client/backend_sdl.cpp src/engine/client/backend_sdl.cpp:18:21: error: function 'void glTexImage3D(...

Oy: no but it was fixed

19:30

I just deleted the GLAPI from GLAPI void APIENTRY glTexImage3D and renamed the datasrc folder to data now its working

19:31

(From Jay)

huh datasrc to data? sounds wrong

And it seems @Assa 's PR is related

19:31

Yeah it does

but you build with bam?!

He had a first workaround resulting in no successful build but no textures

19:32

Yes it does not fix bam for sure @Assa

that error he pasted looks like he build with gcc, would like to know the version, can't reproduce with my mingw

Ooh didn't think of that

19:33

Probably best to ping him on github

19:33

He was on irc once

ok

Ah the data bit is because he did not do bam content, rand helped with that

ah ok, he just built the client or server

19:38

as target

Yeah

19:40

I thought content would be a dependency of client or server

where are projectiles added to snaps?

projectiles.cpp?

hm, k xD

20:00

thx

lol

where are particle effects like explosions added to a snap?

20:27

hm seems to be Projectile:.Tick

particle effects are client side

20:29

explosions on the other hand look CGameContext CreateExplosion

it seems like dummies are not being correctly taken into concideration with that new FriendlyFire test.

22:32

hm, it seems I'm wrong.

Exported 104 message(s)