Houndeye

Member
  • Content count

    35
  • Joined

  • Last visited

About Houndeye

  • Rank
    Fireteam Leader
  • Birthday

Profile Information

  • Gender
    Male
  • Location
    Ukraine

Recent Profile Visitors

287 profile views
  1. CoG in Yehorivka Conquest
  2. CoG in Chora AAS 1
  3. Cool story, OP. Pretty convincing proofs and no way it can be a resentful attempt to publicly throw some shit on a server admins* for whatever reason.
  4. FUBAR in 1 squad Map - Sumari AAS v1
  5. FUBAR, 1 Squad, Kokan AAS
  6. I had issues with switching between game and other applications w/ alt+tab when loading levels. On Saturday it was like, if I'm connecting to server, then do Alt+tab to get to the desktop and back, I'll see not a loading screen, but a main menu, and I can't use it (game becomes "stuck"). Same as I disconnect from the game and do the same thing, I'll see not a loading screen, but a starting scene from the map I've been played on, and again, I can't interact with menu anyhow, I had to shut down game process in Task Manager. Sometimes when doing the same trick it is just a black screen, and again in that case I have to shut down game manually
  7. FUBAR in. Yehorivka
  8. Nice! I personally would like to also have simple patches of Squad logo(s), to be able to attach them on backpack/tracksuit/bathrobe.
  9. FUBAR in, Chora
  10. FUBAR in Gorodok AAS 2
  11. FUBAR in. Yehorivka AAS
  12. The way it works now: - killer receives a notification about team kill he committed (so he is aware of his actions and probably should to say 'sorry' to the victim) - victim does not receives notification about the killer (so it helps preventing retaliation in pub matches) - admins receive notification about committed team kill (they know the victim and the killer, so they can apply sanctions to the latter) Also there is a system which bans the player for the match, after reaching specific amount of team kills by him.
  13. well, people would still be able to reconnect, and choose team anew, and I'm not sure if it is possible to control that. basically, it's not an ultimate solution to prevent ghosters from ghosting, but rather a small step, to prevent accidental team asset compromise. So you are not getting "spoilers" e.g. by looking with peripheral vision on the team map, when you realize that you must/want to be on the other side.
  14. Now, when player joins the game, he is automatically assigned to one of the teams, so he has access to teams map, squads and assets location and etc. Which may not be good, in case if player wants to play on the other team (like, if he joins the game and sees his friends on the other team). Thus, he may accidentally compromise his first team key assets like fobs, rallies, caches, etc. And IMO auto-assignment feels like some legacy from Battlefield. I was planning to make a mod which also relies on some kind of asset, that should not be revealed to the enemy for as long as possible. And I'm thinking to make flow, when player on joining server is not assigned to the team, and can only see list of player names on each team. So he decides which team he wants to play initially. So the questions are, is it planned to make this kind of flow above in vanilla game? Or is it possible to override it in SDK? Also, feel free to bring up pros and cons of auto-assignment, which I haven't touched