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-12-14 00:00:00Z and 2019-12-15 00:00:00Z

f"" strings are a new addition

07:04

python 3.6

But the f string is used in a error message so something before fails already :/

how about a visual gimmick for the future: when playing a race gametype the tee wears race shoes? :)

yikes

@Zatline love that bumbler skin :)

ho the two big prs are in

11:09

good thing the gametype match is not case sensitive for icons

11:09

race tends to use lowercase

11:13

https://github.com/teeworlds/teeworlds/issues/2193 can be closed

Add new skins · Issue #2193 · teeworlds/teeworlds

#2152 ...

11:17

how about some space between callvote and browser in the gui?

11:18

local and global options were separated and I liked that

11:18

of course we can't eat up too much space on the left because locales have a hard time translating server info :/

11:18

ideally a browser icon would be nice :p

yeah more icons for the headers would be nice

11:29

dunno if more space would look odd

Image attachment

just need a browser icon :D

the font doesn't support it :p

oh :D

err, bridge didn't like it. waves at @Sonix

11:35

https://www.fileformat.info/info/unicode/char/1f310/fontsupport.htm not too many fonts

11:38

oy: build failing

11:38

int NewIndex = -1;

11:38

./root/project/src/game/client/components/menus.cpp:990:7: error: unused variable 'NewIndex' [-Werror=unused-variable]

could replace settings with the symbol from the server browser

11:47

makes up space

yeah not sure if we should do that

we shouldn't use different buttons/displays on different interfaces, they should be even

12:05

I agree with replacing settings ingame button with the symbol

yeah we should do that too

12:15

ah nvm read it wrong

12:15

Hopefully people still find the settings button :)

getting a lot of those on linux btw

Image attachment

12:17

window is opened at the right size, but the game still thinks it's on a 1920x1080 screen (my desktop size) when fullscreen'd

it stays white on hover though

12:22

when you use an icon instead of utf8 symbol

do you have a high dpi screen?

Which one is better: https://cdn.discordapp.com/attachments/511260449589821472/655383343134670858/screenshot_2019-12-14_12-19-08.png

https://cdn.discordapp.com/attachments/511260449589821472/655381852185690112/screenshot_2019-12-14_12-13-21.png

12:33

(Icon)

vote for 1st

no high dpi

12:39

for experimentation: https://github.com/teeworlds/teeworlds/compare/master...Dune-jr:exp-extendedbrowser?expand=1

teeworlds/teeworlds

A retro multiplayer shooter. Contribute to teeworlds/teeworlds development by creating an account on GitHub.

12:40

the zoom in makes the name column tight on 4:3 resolutions, although I believe the expanded view (the arrow on the right) was engineered for this use case

12:40

not sure if adaptative zoom in would be better

12:45

about sonix's icons, I think both look equally good

dunno if that's sdl or teeworlds causing that odd screen

never had this on other computers so its probably related to the distro or something

12:51

i don't play other games here so I can't tell

maybe outdated sdl2 version?

12:53

that reminds me: should check if sdl2.10 works on windows now

ah right

libSDL2-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libSDL2-2.0.so.0 (0x00007f9d6f565000)

12:54

2.0.8+dfsg1-1ubuntu1.18.04.4

According to ddnet 2.0.10 has the same issues on windows like 2.0.9

12:59

https://github.com/ddnet/ddnet/issues/1997

SDL 2.0.9 and higher run extremly bad on Windows · Issue #1997 ·...

So while i was on Windows now, I noticed, that SDL 2.0.9 and higher run insanly bad, and i really mean around 100% worse than 2.0.8. I used the latest client and run with 2.0.8, 2.0.9 and 2.0.10 fr...

@Oy happy to hear that

Image attachment

14:18

the 0.7 generics have a lot of space at the corners

14:18

looks kinda ugly with shadows sometimes imo maybe we could need some shadows that only cover the corners on all sides i mean we have a full tileset only shadows now anyways

why not put shadow layer below unhookable layer? (edited)

because then you just move the problem somewhere else

14:21

iif you want no shadow above or bewlow the generic

14:21

at somepoint it will look odd then

@Dune i still dont have any servers in my master

16:44

serverlist.json is full tho

you mean in your browser?

yes

favorites work?

havent tested

17:10

and cant rn, mobile

one question about server-side stats (https://github.com/teeworlds/teeworlds/issues/2255): should it be realized with a netmsg that just initializes the stats and then the client tracks the stats itself or should it use snapshots? advantage of snapshots would be that the server has more control over the stats and it would work in demos aswell. disadvantage would be more traffic, but thanks to delta, compression, etc. it shouldn't be that much

teeworlds/teeworlds

A retro multiplayer shooter. Contribute to teeworlds/teeworlds development by creating an account on GitHub.

17:22

netmsgs might work for demos aswell, but it needs some more code

good question

17:23

the traffic seems somewhat unnecessary

17:23

but if we want to implement some server-side stats we need snapshots I guess (speed, accuracy, wink @Sonix )

when nothing changes, the server won't send any data. otherwise it will just send the delta (+compression)

17:25

since these values dont change that much, this usually means one byte per field. after huffman even less

17:25

but you need to send all player stats to each other player

17:27

well i only thought about the fields currently supported by the statboard. avg. speed, accuracy (maybe even per weapon), ... would create even more traffic =\ (edited)

not sure yeah, should ask Oy later

okay

Image attachment

17:57

the bright eyes are a bit problematic in team based gamemodes =\

huh @Zatline

17:59

sounds like an annoying exploit

let the server handle all the stats

18:10

it's mod friendlier

[teeworlds] <redix> https://cdn.discordapp.com/attachments/490150878934990850/655468258115190794/screenshot_2019-12-14_18-56-15.png

Embedded image

19:57

some skins will need fixups

oh

still got a few things in my todo list

20:01

https://github.com/Dune-jr/teeworlds/projects/2

20:01

2297 and 2242 especially

translations need to be done before release, a week would be good i guess

20:05

so can't any strings then

nothing that I have planned requires strings

20:12

are there open PRs requiring strings?

20:12

https://github.com/teeworlds/teeworlds/pull/2305 removes locales

Improve visuals of some statboard columns by Dune-jr · Pull Reque...

Merge spree and best spree into one column if both is selected Carefully adjust column width if only one column is selected Frags/Deaths -> K/D to be consistent with scoreboard Flags are ...

20:12

https://github.com/teeworlds/teeworlds/pull/2314/files adds some

Add toggle dynamic camera to controls by ChillerDragon · Pull Req...

is automatic demo recording for races planned for vanilla or it will be for custom clients only?

can't you already auto record races?

you can use the auto recording to record everything... but it would be cool to only record the race itself and keep the one with the best time

20:24

the implementation from the old 0.6 clients is a bit hacky, so i did not include it in the pr

yes thats what I meant

it was basically more a matter of time and motivation ^^

Ye thats why I only asked if its planned, I guess its possible to make a non hacky solution now that race is supported in vanilla ^^

yeah the protocol now provides everything thats needed

:D

it's listed in the race issue

votes need to be reworked on a protocol level, I'd guess ._.?

20:27

in regard to #2242

yep. that at least need some slight changes

20:28

depending on how far you want to go, this might even be a breaking change =\

I think it's highly needed to work with ids

20:29

to identify every vote option

20:31

if I'm not mistaken it's currently using the actual description string

20:31

and if there are two equal strings, the first one is used?

20:31

not quite sure

yep

maybe negative ids for whitespace

20:32

dunno ._. ids should do

problem is that you still need to use the description for old clients since it's also used on network level

20:34

so either you have quite a lot compatibility code or you do a breaking change =\

prefer breaking change telling people who try to join to update their client

20:35

0.7 is young and can handle that

20:36

as there is a lot of stuff being done on the protocol level anyway(even tho most likely not compatibility breaking)

i guess to fix that eye thing, there needs to be a black outline in the image

@Dune should be an easy fix in theory team colored tees should either just always use standard black eyes or more complicated but better maybe have an if condition that checks for contrast or a range of acceptable black shades.

that sounds complicated

20:53

not sure if enforcing standard eyes is a good solution...

yeah that I guessed

20:56

well I personally don't like the way team colors are generated as a whole .. markings have a similar issue like the eyes they often get lost in the process

it's not team colour specific, you can also create that skin for dm

my impresssion is that the way 0.6 generated it's team color counterparts was working way better in preserving markings and details

21:07

most simple way to fix it I guess would be to have a condition that when "negative" white eyes are selected then the team colored tee uses "colorable" dark grey instead (edited)

serverside pls

21:09

modding has to be a part of tw

21:09

we shouldnt force too much

if you want the client to see a differnet KD, you can mod the killmessages

We could treat the eyes differently so that they don't get colored

oh, never thought of that

doesn't matter, already tried

21:17

when the body is similar you have that problem, same for non-team gametypes when the body colour is similar

21:18

standard eyes are pretty save cause u can't make a black body, rest isn't

Do we have non black/white colored eyes right now?

no

21:19

you couldn't colorize eyes yet

I saw some weird things because of your zomb eyes @LordSk 🦋

21:19

your zomb skins are popular and some people changed the eye color iirc

What I mean to say, if someone really wants its own skin to have red eyes on a red body, why forbid it?

because everyone else will see it?

As long as default eyes are working as intended it should be fine right?

if we force default eyes I agree, but then what's the point of eyes parts

yeah

21:24

like i mentioned if the eyes have an outline, that you can't colorize, would fix it in general

hmm what do you think of that, @zatline ?

probably have to test how it looks

Image attachment

21:30

So we have 4 default eye types now

21:30

One is colorable

the first one is a bit as well

first 2 are yeah, they're new

We could force black as a color for team based?

but you have the same problem in non-team

21:31

you can color your tee red

hm.

21:35

So I guess there is no way around it

either standard eye parts have to meet good defaults or we mitigate the eye colors so it can only be slightly different than black

or we compare body and eye color, adjust it towards black if they are too close

21:37

and only do this for default eyes

non-default*

I mean default as the 4 we have now

why wouldn't you do it for other eyes?

what if I have cool white outlined eyes, and I want red eyes on a red body

then just like dark skins: you don't

except I would be the only one seeing my own custom eyes right?

21:40

where is the harm in that

whgy are there even 4 eyes? I always had 3 eye types when I was deving the new skins

21:40

*why

lordsk got custom skins maybe?

Hum let me check

there are 2 default eyes which are similar

yea cuz there really only should be 3 options

just the distance between the eyes is a bit bigger i guess

21:42

u barely notice

black, dark grey and negative

Image attachment

standaardreal can get removed

21:43

it's just black with the gaps that nobody liked

alright

Oy btw. I think I may have to make another PR cuz during my work I changed some small details on some of the older skins that I totaly forgot about including in the PR .. and some of the old skins if I remember had inconsistant body outline values as well.

you could add a dot in the middle and have a pupil

one example: limekitty skin used to have lime colored eyes in 0.6 and in 0.7 they became pure black which for me ruined that skin I changed that back to the orignal look

21:57

which btw. actually kicked of me indroducing colorable eyes in the first place lel

I see no good solution for that though

what's wrong with the outline solution?

22:03

i see another option: give eyes/body a texture - yes I would hate that, too

https://gyazo.com/1cd3b2f6ee81c4e6d5433a738a692855

22:04

colorated eyes where a thing in 0.6 this is the old limekitty just saying (edited)

22:09

and it worked just fine back then, if I would make the eyes the same color now in 0.7 eyes would most likely get lost when team color is applied

then make eyes non custom colorable? that sounds reasonable

22:10

isnt there a flag in the json for that

yes

so u mean eliminate eyes color option ingame and just preserve it in the json?

yes

22:23

at least with default skins

22:23

unless you design eyes with an outline such that it is reasonable to allow custom colors

can I share file over here?

yes

try this as overlay layer for team

Image attachment

team is no different than no-team

22:30

this layer should always be applied

22:30

(to problematic eyes)

okay then try that

probably better to directly patch the eyes

hmm but I'm not really sure if I like the concept tho normal eyes were never suposed to have outlines :/

then apply my proposed solution: make such eyes not customisable

only in json I'd be okay with that

22:37

but note this is only making it slightly harder but the exploit would still exist and the way the mouse looks on teams doesn't really change either unless giving it more darker eyes

no, this would fix the exploit, as you wouldn't see others with such skins

but what about default skins like the panther and new mouse that have colored eyes as well as old limekitty that I'd like to reintroduce

I guess you need new eyes for each of these

22:43

hmmm, so we could allow custom colors for our skins, but forbid foreign skins with custom colors. as such, only "limekitty" can get green eyes. not sure if that is a pretty solution

22:44

@LordSk 🦋 might have a third solution with color detection

a well working color detection would be ideal I guess but also most complex sadly I'm aware that this would be not easy

okay outlining it could work doesn't look that bad but ...

Image attachment

22:55

Image attachment

22:56

now the but! look at the markings they as well get totally lost when team color is applied

that is another issue

22:56

I'm not convinced the eyes are fine here

it's nature is the same!

eyes probably should get colored black in team modes anyway

people complained the markings were too defined on team colors

22:58

this is tuneable

the beaver needs teeth

22:59

Exported 237 message(s)