Gunfire Development 10.03.17 - new thread
514 replies Bad news: project is delayed at unknown time. Reason: DC.
CS2d for ANDROID Discord server is here: https://discord.gg/ww59nvf
@
StirlizZ-Fapicon: Why
DC? Can you tell us more information about it?


Stories are made individuality, one way or another.
@
Occasus: I can explain. Skeptic has to hack into CS2D network packed to make multiplayer, because DC wants to keep CS2D closed-source.

@
Chingy: So Skeptic doesn't want to work on it until DC helps him. Maybe we all could encourage him to continue anyway.
At this moment he wants to develop his own 2D shooter for Android with me.

At this moment he wants to develop his own 2D shooter for Android with me.
It's not that boring and may be even entertaining. CS2D packet structure is not that complicated. Wireshark is indeed great software.
I used wireshark to discover some packets and I also used "cs2d-bot" sources they helped me a lot. But there still a lot of undiscovered packets for me and game can't run without them. I can discover them, but I don't have so much time. So if I will continue to work on project - I'll let you all know.
i bought android just for this game and now maybe is gonna fail
hope is not gonna i think dc should help u with this bcuz is ll make cs2d more popular

maybe
DC: don't want Skeptic to make Cs2d for Android
everyone wants to know the "reason"

everyone wants to know the "reason"
The reason for projects like this to fail, is because the packet structure of cs2d is so damn hard.
Another project that struggeled with the packets was the open source custom cs2d server: https://github.com/FloooD/custom_cs2dsrv
They also had problems discovering what all the packets mean.
It would be helpful for the community if DC would be open about the packet structure, and share it with the community.
Great helpful tools could be developed, like you see in other open source games.
All of the data is verified on the server anyway, so hackers couldn't make use of this information.
I would therefor really like to see some more openness from the side of DC.
Another project that struggeled with the packets was the open source custom cs2d server: https://github.com/FloooD/custom_cs2dsrv
They also had problems discovering what all the packets mean.
It would be helpful for the community if DC would be open about the packet structure, and share it with the community.
Great helpful tools could be developed, like you see in other open source games.
All of the data is verified on the server anyway, so hackers couldn't make use of this information.
I would therefor really like to see some more openness from the side of DC.
DC dont want to share his honor.
CS2d for ANDROID Discord server is here: https://discord.gg/ww59nvf
Reason why @
DC: doesn't want to share the source code of CS2D is easy: open source = easy to hack = even more brazilian and turk hackers/cheaters


Reason why @
DC: doesn't want to share the source code of CS2D is easy: open source = easy to hack = even more brazilian and turk hackers/cheaters

This makes somehow no sense because they are already too many. So if cs2d sucks and game will be open source the game will suck even harder.
but dc can just share with @
Skeptic: and no one else ll know

I even added (simple) protections to exclude third party clients from joining original game servers. You could easily develop cheat clients with the knowledge of the packet structure and this would allow even more fine-tuned hacks. You could probably also develop clients that spam servers and make them crash.
Cheats and hacks and server crashers are already there but telling others the packet structure and the ways things are done would push everything to a completely new -and of course much worse- level. You really don't want to experience this!
I don't get why you guys don't simply write your own net protocol and continue developing the game without compatibility to the original CS2D servers (and if you do it right you can still try to add a CS2D compatible mode later).
The idea to make it compatible with CS2D is very questionable anyway.
The huge point is that people who play on Android would stand absolutely no chance when playing against PC players who actually have a real keyboard and a real mouse. Seriously, controlling a game like CS2D on Android can only be a huge pain in the ass and you can never be as fast and precise as a player who is using real physical input devices. I bet that I would easily beat everyone who plays this on Android (and I really don't play much CS2D).
Cheats and hacks and server crashers are already there but telling others the packet structure and the ways things are done would push everything to a completely new -and of course much worse- level. You really don't want to experience this!
I don't get why you guys don't simply write your own net protocol and continue developing the game without compatibility to the original CS2D servers (and if you do it right you can still try to add a CS2D compatible mode later).
The idea to make it compatible with CS2D is very questionable anyway.
The huge point is that people who play on Android would stand absolutely no chance when playing against PC players who actually have a real keyboard and a real mouse. Seriously, controlling a game like CS2D on Android can only be a huge pain in the ass and you can never be as fast and precise as a player who is using real physical input devices. I bet that I would easily beat everyone who plays this on Android (and I really don't play much CS2D).