suggestion
mitigation crowding the skins
(put one inside and if i click above appears
the other skins colors there like this)
result this=
1-more tidy and easier for see
2-makers the skins can make more than one for same a skin
with other color or design without been haveing problems
3- two enough XD 
suggestion
Update ddnet skin system to 0.7 skin system
result = everyone happy 
CLIENT_MAIN and CLIENT_DUMMY already, just add another entry NUM_CLIENTS or so
line = line * 1000 > %
ARC-Authentication-Results: i=1; mx.google.com;
dkim=pass header.i=@news.digitalocean.com header.s=m1 header.b=Z+Z3Objp;
dkim=pass header.i=@mktdns.com header.s=m1 header.b=ICTVrDiZ;
today i needed like 15 minutes for both (edited)
for i in …:
…
else:
…
does
typing
--frozen
Wants and Depends and ConsistsOf etc and in the end just gave up separated them, put restart=always on all of them so they crashed until the services connected in the right way xD/home are automounted even with the noauto option. So because I don't want my /home automounted (it needs to be decrypted first) I had to remove it from /etc/fstab and specify the full path + options in the script that mounts /home for me
types=$(cat all-types) so I did not quote that it needs some more advanced workaround.
I did not test any of the scripts but it should be safe refactors.
bind <key> rcon_auth <password>bind <key> rcon_login <username> <password>bind <key> password <password>
password nimrocks work?error: incompatible types: int cannot be converted to ArrayList<Integer> does anyone understand thistable.add(i).add(k) = s.next().charAt(i); eh i did this xd
I think systemd is far from perfect, but it's the right way to go. It's definitely better than that SysV mess we had before. Even Windows has service manager better than SysV init. Declarative unit files with unified syntax are just better than doing everything manually in shell scripts. It's even faster.
Here's one real life example: I bought new keyboard with backlight yesterday. Unfortunately, the keyboard doesn't remember its settings, so it has to be configured by some app after boot, otherwise you always get some rainbow nonsense. There's no official app for Linux of course, but someone has reverse engineered the protocol and created a simple command line app for configuring the backlight. So far so good, but there's one more thing. If you put your computer to sleep mode, the keyboard automatically turns off its backlight. The problem is that the backlight is not automatically turned on after computer wake up. To fix that you need to run the app again. And this is where systemd comes into play. Just look at this lovely thing:
[Unit]
Description=Restore keyboard backlight after suspend
After=suspend.target
[Service]
Type=oneshot
ExecStart=/usr/bin/g213-led -p /etc/g810-led/profile
[Install]
WantedBy=suspend.target
It's so simple and clean solution. No dirty hacks that don't survive next OS update are needed. How many service managers can do such thing? I'm not systemd fanboy because I've had a lot of troubles with it in the past, but it gets better and better. All you need is to get used to it. disassemble should work, you want to disassemble at %rip
objdump -dCS ?
disassemble CMoney::Snap in gdb--visualize-jumps=extended-color is really nice thingobjdump --disassemble=CMoney::Snap DDNet-Server I guess?
-M intel for sane assembly syntax (edited)python -c 'print(hex(0xabc + 25))'
Team() in that function?rdi 0x55555590c4d0 93824996132048CGameMask::TeamMaskm_pOwner->GetPlayer()->GetCID() chainrsi 0x41 65 isnt 65 a bit high for a clientid?m_pOwner->GetPlayer()->GetCID() chain?
(edited)
=================================================================
==18192==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 992 byte(s) in 1 object(s) allocated from:
#0 0x4f3d02 in __sanitizer::InternalMmapVectorNoCtor::Realloc(unsigned long) (/home/teeworlds/servers/DDNet-Server-asan+0x4f3d02)
#1 0x7f59e7c7dc08 (/lib/x86_64-linux-gnu/libsqlite3.so.0+0x49c08)
SUMMARY: AddressSanitizer: 992 byte(s) leaked in 1 allocation(s).