find this kinda not so pretty, as it makes kind of not much sense to use a class if there is no internal state saved at all. https://github.com/teeworlds/teeworlds/blob/master/src/engine/shared/compression.h. might as well save the pointer that is being returned internally and return it when asked via another method. usual use case if ptr = varInt.Unpack(ptr, &integer)
04:46
I think it would look better if the pointer was not used at all here. the VariableInt could be constructed by passing the pointer and the pointer could be returned via a method resulting in an interface that looks like this: integer = varInt.Unpack()
04:46
when one is done with unpacking, one might retrieve the pointer via some method like GetPtr() or GetPos()
04:48
as it's c++, the construction might get a size attribute as well in order not to enter unexplored territory
This addresses #2389
Replacing the NetBool with NetEnum works because RECORDTYPE_NONE maps to 0 and RECORDTYPE_PLAYER to 1. The modder has to ensure that RECORDTYPE_MAP is only sent to 0.7.5 clients.
Let's say I have 2 user accounts user1 and user2. When I login as user1, and then switch to user2 using su, I can execute command-line programs, but GUI programs fail.
Example:
user1@laptop:~$ su -
well... what changed? basic gameplay didn't change within the last 10 years :D
with 0.7 we have a new menu. there are several details that changed but there havent been any major changes
@ChillerDragon just for curiosity... what are the major things that 0.7 is missing compared to ddnet?
obviously is does not have all the ddrace specific stuff...
antiping
15:42
i used ddnet myself but i hardly used any non vanilla features
@redix well i can speak best for me and i try to find out every day why others do not update but i guess not updating is also a coninience and bubble thing
For me personally as i already said i can not properly control my mouse in 0.7 idk if ddnet had a influence on that. Also I really depend on demo features like demo cutting and sort by date or name. @redix
and those were only the things that quickly came to my mind and are non ddrace. But you have to keep in mind that a big part of the player base plays a lot of ddrace and needs the clientside predicition and map editor features etc
if i wouldnt care i would have never updated because of the slightly off mousesense and played 0.6 until im the last one there
15:51
everytime i advertise 0.7 ingame people ask me "whats new" like "why should i do it" and "what changed". I really lack arguments in these situations. Should i say its a new protocol so ddnet client wont work anymore and this removes antiping and name changing... but you get a new menu (which some people actually dislike).
15:52
you can not advertise a new vanilla gametype to the average ddrace player or fixed anti spoof for people who are save from spooing with ddnet client already.
i think if the 0.7 name system gets fixed (reset to 0.6 state) with a lot of effort we could migrate the community to the new version and restore all the old standards
the 0.7 has undistinguishable names which is annoying in whispering spectating and chatting not to mention modifications where playernames are arguemnts to commands
15:59
well i personally do not care about changing names but seems like others do and thus 0.7 looks like a downgrade. I havent seen a single person saying yay finally i cant change my name anymore.
Oy: btw do you think of a way a vanilla server could signal client-sided bots? right now it is not possible without a code modification, which is forbidden
what about more than is bot or not. What about a int with flags what type of client it is. Like chatbot/aimbot/spider and the admin can see these flags in status but the vanilla client can not set any of these flags without modifying the source code.