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 2020-06-14 00:00:00Z and 2020-06-15 00:00:00Z

lol Digit

Yo Oy any way I can get you to merge my change in the old editor? Im sure there will be a legacy editor cult for some time and who knows when the new editor rlses?

09:23

Also I do not want to mess with the WIP code

ZillyHuhn: all the other issues and PRs related to editor1 were also closed

09:48

https://github.com/teeworlds/teeworlds/pull/2291 https://github.com/teeworlds/teeworlds/pull/2469

Refresh map/mapres list on filter update (#2290) by ChillerDragon ·...

This fixes selecting a map/mapres with arrow keys in a filterd list. And the wrong sized scrollbar in a filtered list.

Add Ctrl+Q shortcut to create quad at mouse position, add label for...

Pipette apply button: Fixes some of #1931.

Yea sure it makes sense and all. Its also motivating to look into editor2. But after testing editor2 I realized its not only improvements its also changes that have to be relearend.

relearend?

Yea

09:50

its a different editor you have to learn how it works again

got an alternative word?

isnt that a word? :D

ah, relearned

09:52

well yes, it's a complete rewrite. 0.7 rewrote some things too, but you don't see PRs for 0.6

09:52

the sooner you get into it, the more you benefit :)

was about to mention 0.6

09:52

that didnt work out too well

09:52

and there were even less changes than in the editor

09:52

and yes there was 0.6.5 after the development of 0.7 started

09:52

also 0.6.4?

09:53

0.6.3?

because of security patches

09:53

no features

09:53

I'm more comfortable with the old code too

I think yes it makes sense to not maintain two editors but stopping updates on the current editor because eventually some new editor will come isnt to productive imo.

09:56

We do not know if a new editor will ever finish or if it will be used by users and if that happens how long it will take.

I agree actually. We could still update the current editor while adding these new features as issues for the new one, which would then be implemented when it catches up.

while adding these new features as issues for the new oneThe issue is when you add features for the editorv1

10:11

without adding them to v2

10:11

it just increases the porting burden

not necessarily, the core features stay the same

10:12

it does in the long run

Q: Does anyone remember how the tee colors changed since 0.6?

10:48

If I send the exact color from 0.6 it's too dark, if I unclamp lighting before sending it, it's too bright

10:51

And I agree with still allowing patches for editor1, editor2 is a decent while away

meh

didn't we go from rgb to hsl?

packed tee colors were always hsl, 3 bytes

10:58

it used to be that the entire L space was mapped onto the upper half of the L space though

we also have white base skin parts now

the whole tee redering changed

Oy: Are colors artificially lightened in some way?

11:04

Or is it just HSL packed into 3 bytes now?

Learath2: didn't write that new rendering, but i think it's still packed the same way

11:07

but there're more layers for a body now and colours are allied differently now

https://github.com/teeworlds/teeworlds/blob/0.6/src/game/client/components/skins.cpp#L157 0.6

teeworlds/teeworlds

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

11:16

https://github.com/teeworlds/teeworlds/blob/master/src/game/client/components/skins.cpp#L409 0.7

teeworlds/teeworlds

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

aha the darkest color is much darker in 0.7

11:26

that's why I've been getting way too dark with old clamping and way too light with new

11:26

.s/with new/without clamping/

11:26

Thanks Oy

Exported 50 message(s)