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

@heinrich5991 I actually do, but am so busy writing my masterthesis. The Teeworlds docs lack some information how to compile everything with cmake. I would like to try it out. https://teeworlds.com/?page=docs&wiki=compiling_everything_linux

06:34

The docs should imo also cover how to fix cmake when adding source files to the project.

The docs were not updated since. If you would like to do it, there is a github for that @Slayer *gV*

Hmm im not sure if these new chat commands are nice. Imo it is very confusing especially on a modded server that also accepts commands. I tried /team in a ddrace mod and expected to join a team but i was using the teamchat .-. I mean who types /team instead of pressing a teamchat bind. It just adds more confusion. Opening a seperate console where you know its for client commands is very nice imo. It also has autocompletion and information to the commands. I don't really see the benefit of handling chat commands client side. Also I don't know any game that supports clientside chat commands. I mean you expect the chat to be sent to the server right?

That should be discussed, yes. Some games do that, all blizzard games afaik

08:51

Chat commands are supposed to help addressing the issue of selecting the person you want to whisper when there are 64 players

08:52

Also it lets you mute and befriend people with keyboard only

08:52

You can send /team using Escape in the chat.

@Dune I would gladly like to help. But due to my lacking knowledge about cmake I wouldn't add anything helpful.

08:57

@ChillerDragon Chat commands work for many other games, too. I don't see any problem here. But there is no doubt that mods have to adapt to the new situation.

08:58

E. g. you could use "/mymod chat-command" over "/chat-command". Or "//chat-command". etc.

ye sure mods can adapt but imo it is adding conufusion and not a better ux

09:03

not only for the mod support. It just feels wrong even in vanilla to use chat commands for client stuff.

It was engineered to not restrict any chat message (with Esc), if you have any suggestion to make it more accessible, I'm all ears

09:53

We can also remove it altogether, but then we need another solution for whisper target selection

yes i assumed it was built for whisper. I dont get the Esc part tho.

If you type /r and press escape you leave the command mode and can send "/r" in the chat

11:49

Same with /team

so you wanted to keep the ability to send those in chat hmm

12:04

i wonder why tho. If you want to communicate something you can prefix it with a space. And if the server would process the whisper command mods could even overwrite that serverside to use their own /team and /whisper commands

12:05

so remove all commands from client completly and only keep whisper in server. problem solved.

Overwriting vanilla commands should never be possible. That would add ALOT confusion.

true

12:47

But is it possible right now that the server handles the whisper how he wants? I guess so.

12:48

Or we move the wisper target out of chat to an ui like in spectator. You press the wispeher bind and select a tee to wisper to. If you press it defualt selects the last conversation so you only have to press enter or select a new tee.

how would you select it? if you make an UI to select it with a keyboard, chances are you will end up with something similar to the chat commands, which you can already consider as an UI

do you know the spectator select thingy?

13:11

i forgot how its called

well that's with the mouse

yes

13:13

we can add empty names agian if we dont have to type it hehe (just jokin empty names are evil .-.)

I think keyboard selection is important for something like chat where your hands are on the keyboard

13:14

imagine you had to use your mouse to ping someone or to select the chat mode

i would also suggest improving this menu to allow for keyboard selection

the spectator menu?

yes would be nice

13:15

additional

you can already go to previous/next spectator with a bind

not replacing

13:15

it combines well

13:15

you type d. And then you spectate Dada. You press next and then you spectate Dune.

well you could implement /spec

13:28

that would trigger in spec only

what? no please not more chat commands but less.

then I don't quite understand what kind of feature you want for spectators

13:45

there are already binds

13:46

if you make an UI that lets you type and autocomplete a name you're basically going to rewrite chat features and have a similar functionality

yes haha but not in chat.. i was thinking of filebrowser controls. But im not sure how it should look exactly but this chat doesn't feel good.

Exported 48 message(s)