Forum

Apart from the drama, and noting that I voted "random spawn for AA3 maps only".

I think that adding more randomness would be a very exciting option. Because of obvious limitations, we can't have good quality, but completely random maps (and I think this is and will be true for any games for a long time). However imagine an FPS game where you have to fight in a completely unknown environment each round. Some very limited idea of this is already present in the game, think about the more-or-less random state of ew/ww doors in hospital.

Random spawn points, if implemented wisely, could add an extra aspect to the game. And because of the randomness, advantages/disadvantages would even out for the teams in consecutive rounds (note the word "wisely" in the prev sentence). Someone noted that bridge would become unfair with that, however I think that it's the best example where it would be useful. Random spawns in def hills/assault insertion area would invalidate a lot of spams, and you couldn't be sure which side's rushers are about to reach mid first.

And by random spawns, I think the devs meant random team spawns, and not random individual player spawns. Such as in extraction, where btw indeed there are very imbalanced spawn combinations.

I like this map, I think the concept shouldn't be changed. Indeed it's a camping map, but sometimes it's good.

I prefer the current silence. For weapons, I think it's good that there is no 203, it would soon become a spamfest otherwise. I wouldn't have any kills w/o scope in this map, so it can stay

Bug report: visually own team has opfor weapons (ak74 and rpk), but weapons sounds are mostly as they should be. (Except for own gun, it's correct.)

Rgr, wasn't complaining, just notifying

Just a minor update process bug report: when upgrading from the old client, the new binary isn't set to be executable, so it fails to restart.

Anyway, I like the new look, it's still upgrading the maps, so I can't be more specific yet

Developers [snip] developers.

I mentioned in two threads that I could help in development, and one of you pls pm me if help is needed

And no, existance of TOS does not change anything. TOS doesn't magically make illegal things legal.

Have you ever read any licence agreement from MS/Google/Apple/etc? They can do with your personal data pretty much anything they want (and screenshots would be the least of the concerns...). (Although I'm myself very keen on privacy, that's why I'm trying to help arriving at a design which is acceptable from this viewpoint, too.)

I think we can't stop MITM attacks and wifi sniffing, Assist is vulnerable just as your web browser or instant messanger is.

We can make the communication flow through a more secure channel BUT nothing is perfect,
See the recent News 

Math is almost perfect General consensus is that even NSA can't break it, but they are doing their nasty things mostly with cheating.

Yes, using secure channels would be a must, with proper pubkey authentication (to mitigate easy MITM threats). Security is all about making an attack more expensive than the possible gain.

There are two aspects here: 1) protecting the game environment (aa+assist) from hackers and 2) protecting the host system from compromises through assist. As I see, only 1) is being addressed, and the measures for doing that can hurt 2) in terrible ways.

(Please also see my post from yesterday.)

Hi guys,

I'm not very active on the forums but some of you may know me from the game.

On the licensing model: I would be very happy with open source. Generally security by obscurity does not work. Indeed if anyone can read the source then unknown mistakes may be exploited, but I think that this is easily detectable and if there is a known issue, then a lot more ppl can help fixing it. (For example I wouldn't have time for development, but I would happily try to help in finding and eliminating security issues/exploits when they arise.) I think that the infrastructure should be restored as soon as possible with the current model (otherwise players will be lost), but then the development model should be discussed before doing actual work. Open sourcing would also provide the chance to avoid the death of the project in case the original developers leave for whatever reason (or at least enables resurrection).

On the security issues/design issues: although I'm not a cryptography expert, I have some knowledge on the topic (although mostly on the theoretical part). I would be happy to participate in the discussion concerning this topic. (I can help with system design, some cryptography, and algorithmic questions; I hate working on anything GUI related.) Spanky if you think that the project would benefit from my input please PM me and I can share IRL information with you to let you verify my background.