There is a mod that stops the replay at a certain timestamp, so you go +10 and do something else for 5-10 minutes. Don't have the name though.

Micro is king. I remember Gyle casts where Zock killed 3 T1 tanks with a fucking lab. Is that cheating? No it's regular game mechanic.

Somebody once tried to train me air fights. We both took (cheated) 500 ASF and battled each other, he did good micro, I did bad micro he emerged with 400 ASFs while my ASFs were wiped out. There was not cheating in the air fight involved. We did it multiple times. It was reproducible.
You don't have to like the impact that micro can have (I don't), but it's been there forever and was always a part of the game.

But will the current working authentication method work in the future (the one that the Java client 1.4.7 uses)?

No. It will be removed once all FAF services are migrated to the new version. This will probably take a very long time, but I wouldn't put any app to the old solution anymore just because it seems easier.

Of course it can. We can give it it's own OAuth client id.

You need to implement the OAuth 2.0 PKCE flow with OpenID connect (https://oauth.net/2/pkce/).
It will require you to use a webview and hijack the redirect - which is what we started doing in the java client 1.5.0 RC1.

Our new OAuth service implements the auto-discovery feature (all data available at https://hydra.faforever.com/.well-known/openid-configuration).

How to do it in Python? I have no clue.

(version from 07.07.2021)

Introduction

This code of conduct applies to all spaces managed by the FAForever project, including IRC, Forum, Discord, Zulip, issue trackers, wikis, blogs, Twitter, YouTube, Twitch, and any other communication channel used by our communities.

We expect this code of conduct to be honored by everyone who participates in the FAForever community formally or informally, or claims any affiliation with the Association, in any FAF-related activities and especially when representing FAF, in any role.

This code is not exhaustive or complete. It serves to distill our common understanding of a collaborative, shared environment and goals. We expect it to be followed in spirit as much as in the letter, so that it can enrich all of us and the technical communities in which we participate.

The Code of Conduct may be supplemented by further rules specifying desired and undesired behaviour in certain areas.

Specific Guidelines

We strive to:

1. Be open. We invite anyone to participate in our community. We preferably use public methods of communication for project-related messages, unless discussing something sensitive. This applies to messages for help or project-related support, too; not only is a public support request much more likely to result in an answer to a question, it also makes sure that any inadvertent mistakes made by people answering will be more easily detected and corrected.

2. Be empathetic*, welcoming, friendly, and patient. We work together to resolve conflict, assume good intentions, and do our best to act in an empathetic fashion. We may all experience some frustration from time to time, but we do not allow frustration to turn into a personal attack. A community where people feel uncomfortable or threatened is not a productive one. We should be respectful when dealing with other community members as well as with people outside our community.

3. Be collaborative. Our work will be used by other people, and in turn we will depend on the work of others. When we make something for the benefit of the project, we are willing to explain to others how it works, so that they can build on the work to make it even better. Any decision we make will affect users and colleagues, and we take those consequences seriously when making decisions.

4. Be inquisitive. Nobody knows everything! Asking questions early avoids many problems later, so questions are encouraged, though they may be directed to the appropriate forum. Those who are asked should be responsive and helpful, within the context of our shared goal of improving the FAForever project.

5. Be careful in the words that we choose. Whether we are participating as professionals or volunteers, we value professionalism in all interactions, and take responsibility for our own speech. Be kind to others. Do not insult or put down other participants. Harassment and other exclusionary behaviour is not acceptable. This includes, but is not limited to:

   • Violent threats or language directed against another person.
   • Sexist, racist, or otherwise discriminatory jokes and language.
   • Posting sexually explicit or violent material.
   • Posting (or threatening to post) other people's personally identifying information ("doxing").
   • Sharing private content, such as emails sent privately or non-publicly, or unlogged forums such as IRC channel history.
   • Personal insults, especially those using racist or sexist terms.
   • Unwelcome sexual attention.
   • Excessive or unnecessary profanity.
   • Repeated harassment of others. In general, if someone asks you to stop, then stop.
   • Advocating for, or encouraging, any of the above behaviour.

6. Be concise. Keep in mind that what you write once will be read by hundreds of persons. Writing a short message means people can understand the conversation as efficiently as possible. Short messages should always strive to be empathetic, welcoming, friendly and patient. When a long explanation is necessary, consider adding a summary.
   Try to bring new ideas to a conversation so that each message adds something unique to the thread, keeping in mind that the rest of the thread still contains the other messages with arguments that have already been made.
   Try to stay on topic, especially in discussions that are already fairly large.

7. Step down considerately. Members of every project come and go. When somebody leaves or disengages from the project they should tell people they are leaving and take the proper steps to ensure that others can pick up where they left off. In doing so, they should remain respectful of those who continue to participate in the project and should not misrepresent the project's goals or achievements. Likewise, community members should respect any individual's choice to leave the project.

Diversity Statement

FAForever welcomes and encourages participation by everyone. We are committed to being a community that everyone feels good about joining. Although we may not be able to satisfy everyone, we will always work to treat everyone well.

No matter how you identify yourself or how others perceive you: we welcome you. Though no list can hope to be comprehensive, we explicitly honour diversity in: age, culture, ethnicity, genotype, gender identity or expression, language, national origin, neurotype, phenotype, political beliefs, profession, race, religion, sexual orientation, socioeconomic status, subculture and technical ability.

Though we welcome people fluent in all languages, all official FAForever communication is conducted in English. Translations may be provided, but in case of contradictory wording, the English version takes precedence.

Standards for behaviour in the FAForever community are detailed in the Code of Conduct above. We expect participants in our community to meet these standards in all their interactions and to help others to do so as well.

Reporting Guidelines

While this code of conduct should be adhered to by community members, we recognize that sometimes people may have a bad day, or be unaware of some of the guidelines in this code of conduct. If you believe someone is violating this code of conduct, you may reply to them and point out this code of conduct. Such messages may be in public or in private, whatever is most appropriate. Assume good faith; it is more likely that participants are unaware of their bad behaviour than that they intentionally try to degrade the quality of the discussion. Should there be difficulties in dealing with the situation, you may report your compliance issues in confidence to either:

• The moderation team members indicated in our communication mediums
• The president of the FAForever association: Sheeo (admin at faforever dot org)
• Any other board member of the association as listed in our association forum.

If the violation is in documentation or code, for example inappropriate pronoun usage or word choice within official documentation, we ask that people report these privately to the project maintainers or to the DevOps Team Lead (Brutus5000, brutus5000 at faforever dot com).

Endnotes

* This Code defines empathy as "a vicarious participation in the emotions, ideas, or opinions of others; the ability to imagine oneself in the condition or predicament of another." Empathetic is the adjectival form of empathy.

This statement was shamelessly copied and modified from the Apache Software Foundation Code Of Conduct and it’s honoured predecessors.

Hello everybody,

we apologize for the technical issues in the last 2 days. Nevertheless the vote ended and Morax is the official winner of the election.

We thank FtxCommando for his service in the last 2 years.

Voting details

The mode of vote was instant run off. So every round we eliminate the candidate with the least votes and transfer his votes to whatever the voter has defined as the next fallback vote.
Since we only had 3 candidates that makes it fairly easy to lookup.

Results of the 1st iteration (primary votes):

FtXCommando is last and his 175 votes are transferred to:

This gives us results of the 2nd iteration:

As it's only 2 candidates left, the one with the majority wins. In this case it's Morax.

Voting distribution over time

Also people wanted to know when was voted and if we can shorten future voting periods. Here is some data:

Where is the Kangaroo? Michelangelo would be disappointed.

You could also snipe the enemies energy.
(Assuming the chickens are already in the enemy base)

Connectivity problems like this are beyond our control. The FAF client expects a working network connection, and if it doesn't have one it will malfunction.

That looks really cool.

Also the eastereggs. Lovely. The UEF uses power point? No wonder the almost lost the war.

Also:

Not more than you could do in any other map or mod.

All files are just loaded by the game in a structured way. Let's assume somebody packs a malicious exe file into a mod, the client and the game would ignore it and never open it.

@ftxcommando said in Lagging games:

1 minute real time (not game time) per player needs to pass before a game is ranked.

With the first ACU dying it's also ranked.

What exactly have you searched for?

Abusing my ultimate server powers I trashed the article now.

We only have limited access over the installer routines since we use a dedicated 3rd party tool for this and have to look into what can actually be implemented. If even, I highly doubt we'll be able to squeeze out more than a button opening a browser.

And for sure we'll not switch to a different installer.

I locked this topic (not moderators), because the user @Hashbrowns69 is a fake account that was just created today in order to perform some trolling.

However to people reading this.

I'd like to remind you that we are all working on our free time here. I have a full time job, a little son, a server to run and an association to setup.

Yes, I did not actively stop this nonsense (question is if I could), but I would like to remind you that apart from some drama nothing really happened now.

The server is running, the client receives updates, tournaments are still happening. Every organisation can have issues and yes this time it went public. That's sad but we're also all human.

FAF won't die just because there is some drama going on. There has been drama in the past, you just didn't notice.

Can you give a sample replay id that you cannot start?

@katharsas said in desyncs and patch versions:

@Brutus5000 That would not happen very often at all, while right now it can affect anybody even long after the patch has been deployed.

Well then this should not be tied to joining queues, but the client should download new game files after start.

@katharsas said in desyncs and patch versions:

Cant we just delay any queue joining on the client side if game files arent upt to date?

Doesn't cover the problem if you already joined a queue and then a patch is deployed.

The problem with AI screwing up regular ladder could be solved by building an beginner-AI-matchmaker pool that is only for people below X rating, but you can farm rating and games for ladder.

Solves the negative ratings. Solves the lack of games problem. Teaches players basics of the game (assuming the AIs behave a little bit like real ladder players e.g. spam instead of turtle).