Community rules

1. Game rules & roles

Be a Weather is a survival game: the Weather controls hazards and Survivors try to outlast them in the arena. Follow the role, objectives and round instructions displayed in your build.

• Use only the abilities and actions provided by the game.
• Do not use bugs to reach protected areas, remain invulnerable or interfere with another player’s controls.
• Respect round boundaries and do not deliberately prevent a round from finishing.
• Do not arrange unfair teaming or manipulate results in competitive public play.

Timers, damage, cooldowns, rewards and exact victory conditions are still being developed. This website does not invent fixed values for unfinished features. Private practice and bot matches may use different settings.

1. Follow the rules of the active round

Play the role assigned by the game. Survivors should use movement, positioning and the available game mechanics to survive. The Weather should use the abilities provided for that role. A visual effect, spectator view or unfinished interface does not give permission to interfere with a role you were not assigned.

The instructions displayed for the current mode take priority over general strategy advice on this website. Different test builds can have different objectives. If the instructions are missing or contradictory, describe the problem instead of inventing a competitive advantage from it.

2. Arena boundaries and protected areas

Do not deliberately enter unfinished geometry, hide beneath the map, bypass a boundary or remain in a location where opponents cannot interact with you because of a bug. If you accidentally become stuck outside the intended arena, try the ordinary recovery options available in your build. Record the problem if you cannot recover.

Using a legitimate obstacle for cover is allowed. Repeatedly forcing your character through that obstacle to become untouchable is not. Standing in a difficult but intended position is not automatically an exploit.

3. Cooperation, competition and stalling

Helping another Survivor is allowed when the mode permits teamwork. Secretly agreeing with an opposing player to manufacture wins, feed rewards or exclude everyone else from a fair match is not. Do not repeatedly reset or obstruct a match solely to prevent other players from finishing it.

Taking a break, disconnecting unexpectedly or making a poor tactical decision is not by itself misconduct. The distinction is between ordinary play and deliberate, repeated interference.

4. Examples

• Allowed: dodging a visible hazard, choosing a defensive route or practising ability timing.
• Not allowed: repeating a known invulnerability bug after discovering how it works.
• Report: an ability hitting a protected spawn, a round never ending or a player appearing in the wrong role.

5. Unfinished mechanics

Do not treat promotional artwork, an old video or a previous build as a promise of specific damage values, cooldowns or rewards. Those details must come from the actual released mode. Report a mismatch with the build version and the instructions you saw.

Back to rule contents ↑

2. Respectful behaviour

Treat other players with respect, including when you lose or disagree.

• No threats, targeted harassment, bullying or encouragement of self-harm.
• No hate speech or attacks based on someone’s identity or background.
• No sexual harassment, sexually explicit content or attempts to exploit younger players.
• Do not impersonate another player, the developer, a moderator or platform support.
• Keep display names and any shared content appropriate for the community.

These expectations apply wherever you interact with other players about the game. They do not imply that an in-game chat or moderation system is already available.

1. Competition without personal attacks

You may disagree with a strategy, describe a frustrating match or criticise a game mechanic. Focus on the action or feature rather than attacking the person. A lost round is not a reason to target someone’s appearance, accent, disability, nationality, religion, gender or other personal characteristic.

Friendly banter depends on the people involved. If someone asks you to stop, continuing to target them is not justified by calling it a joke. Repeating an insult through multiple accounts or encouraging friends to join in makes the conduct more serious.

2. Threats, intimidation and sexual conduct

Do not threaten violence, encourage someone to harm themselves, make sexual demands or send unwanted sexual material. Do not try to frighten someone by claiming to know where they live or by pretending that you can access their account. Threats are not acceptable simply because you say you did not intend to carry them out.

3. Names, images and shared content

Use names and content that do not impersonate staff, promote hatred, expose private information or deliberately target another player. Changing spelling, using symbols or splitting a message into several pieces does not make prohibited content acceptable. These expectations apply to any communication feature that is actually available, not to an assumed chat system.

4. Unwanted contact and group behaviour

Do not follow a player between rooms to continue an argument, repeatedly invite them after a refusal or organise a group to overwhelm them with messages. Do not publicly demand that others punish someone based only on your allegation. Use the available reporting route when one is provided.

5. Context matters

• Allowed: “That ability feels too strong; here is what happened.”
• Not allowed: turning that disagreement into repeated personal abuse.
• Allowed: declining an invitation or leaving an uncomfortable conversation.
• Not allowed: pressuring someone to stay, disclose personal information or apologise publicly.

Accidental misunderstandings should be handled calmly. Clarify, apologise where appropriate and stop the behaviour that caused the problem.

Back to rule contents ↑

3. Cheating, exploits & automation

Compete using the tools available to everyone in the game.

• No cheats, unauthorised modifications, injected scripts or tools that provide an unfair advantage.
• No automated reward farming, match manipulation or deliberate exploitation of duplicated progress.
• Do not attack servers, overload services or deliberately disrupt connections.
• Do not use another account to evade an access restriction.

The game’s built-in practice bots are allowed. A visual bug or an ordinary mistake is not automatically cheating. Describe suspected problems accurately and do not organise harassment against a player.

1. Unfair tools and modifications

Do not use tools that alter gameplay to provide information, movement, accuracy, damage or protection that normal players do not have. This includes manipulating network traffic, injecting gameplay scripts, changing protected values or bypassing restrictions intended to keep matches fair.

Ordinary accessibility tools, controller remapping, recording software and performance overlays are not automatically cheating. The relevant question is whether a tool provides an unauthorised gameplay advantage, performs gameplay automatically or interferes with other players or the service.

2. Exploits and accidental discoveries

Finding a bug accidentally is different from repeatedly exploiting it. Once you recognise that an action bypasses the intended rules, stop using it for advantage. Do not distribute instructions or tools designed to let others abuse the issue. A private room does not authorise attacks on shared services or manipulation of persistent rewards.

3. Automation and reward manipulation

Do not automate matches, movement or repeated actions to farm rewards while absent. Do not arrange fake matches, intentional losses or multiple-account participation to manufacture results. Built-in practice bots are part of the game and are permitted; unauthorised scripts pretending to be real players are different.

4. Connection interference

Do not intentionally lag, flood, crash or disconnect another player or server. Do not exploit a host’s control over a session to falsify results. A genuine network failure, a slow device or a crash is not proof that someone is attacking a match.

5. Fair assessment

Do not accuse someone of cheating solely because they played well, appeared to move strangely during lag or won repeatedly. Record observable behaviour and describe uncertainty honestly. Reports should distinguish what you saw from what you suspect.

• Allowed: practising with bots and changing ordinary input settings.
• Not allowed: using an external script to play or collect rewards for you.
• Report: a reproducible bug that grants an unintended advantage.

Back to rule contents ↑

4. Private servers & invitations

Hosts decide who they invite and which available practice settings to use. Tell invited players about those settings before starting.

• Share room codes only with the people you intend to invite.
• Do not publish someone else’s private code without their permission.
• No repeated unwanted invitations or pressure to join.
• Do not demand passwords, payment or personal information in exchange for entry.
• Community safety and fair-play rules still apply in private rooms.

Hosting does not grant access to other players’ accounts. A room code does not bypass Epic application permissions. Private online play remains under testing.

1. Hosting responsibly

Explain the intended activity and relevant settings before a private session begins. Tell players whether the room is for practice, friendly competition or testing a feature, and whether bots are included. Do not advertise one activity and deliberately switch to another in order to trick invited players.

Hosts may choose whom to invite, but hosting does not give ownership of other players’ accounts or permission to demand private information. Any host controls are limited to the features the game actually provides.

2. Codes and invitations

Treat a room code as an invitation intended for a particular audience. Ask the host before forwarding it to additional people or posting it publicly. If a code is exposed, explain that to the host so they can use the available room-management options. Do not repeatedly try to re-enter a room after being told you are not welcome.

An accidental invitation is not the same as harassment. Repeated invitations after a clear refusal, or invitations sent through alternate accounts to avoid that refusal, are unacceptable.

3. Custom arrangements

A practice group may agree to unusual challenges or test strategies where the game allows them. Agreement among participants does not authorise cheating against outsiders, manipulating persistent progress, attacking services or sharing another person’s private data.

Do not claim that a private-room agreement overrides platform account rules. All participants should understand what is being tested and be free to leave.

4. Hosts leaving and connection problems

A player-hosted room may become unavailable when the host exits or loses connection. This is not automatically evidence of misconduct. Before reporting deliberate disruption, record what happened and whether the behaviour was repeated.

5. Examples

• Allowed: inviting friends to practise with bots after explaining the settings.
• Not allowed: publishing a private code to send unwanted players into the room.
• Not allowed: charging players for a supposed official access privilege that you do not control.

Back to rule contents ↑

5. Accounts & identity

Use an account you are entitled to use and follow the applicable platform account rules.

• Do not steal, buy, sell or impersonate accounts through this community.
• Do not ask for or share passwords, login tokens, recovery codes or verification codes.
• Do not claim to be official support to gain access to another account.
• Use Epic’s official support channels for Epic account recovery.

Be a Weather Support cannot reset Epic passwords. There is no account-login form on this website.

1. Use legitimate access

Use an account you are authorised to use. Do not access another person’s account without permission, impersonate its owner or use information obtained from a leak. Do not advertise stolen accounts or offer to bypass application-access restrictions.

A development application can restrict access even when an Epic account works normally elsewhere. Repeatedly creating accounts does not grant permission to enter a restricted test.

2. Passwords and verification codes

Never give another player your password, verification code, recovery code or authentication token. A person claiming to be a developer, moderator or helpful tester does not need those secrets. Do not paste them into bug reports, screenshots or public messages.

Account recovery belongs in the official account provider’s recovery flow. Be a Weather Support cannot inspect your Epic password or complete a recovery on your behalf.

3. Impersonation and misleading identity

Do not use names, images or messages to make others believe you are official staff, an Epic representative or another player. A fan name or joke becomes a problem when it is used to deceive people, collect information or intimidate someone.

4. Alternate accounts and restrictions

An alternate account must not be used to continue harassment, evade a restriction or obtain rewards unfairly. Do not help another person bypass a restriction by lending an account or disguising their participation.

5. Suspected compromise

If you think an account has been compromised, use the provider’s official support and security tools. Stop sharing codes with the suspected impersonator. Do not attempt to “hack back”, buy recovery services from strangers or send further secrets to someone who claims they can fix the problem.

When describing the problem to support, share only the details requested through the legitimate support channel.

Back to rule contents ↑

6. Personal information & younger players

Keep private information private. Do not publish another person’s real name, address, phone number, school, private messages or other identifying information without permission.

Never pressure a player to share personal details, photos or private contact information. Do not use the community to groom, exploit or endanger anyone.

Follow the age requirements, parental permissions and controls applicable to your platform account. The game’s final audience and public-release safeguards have not yet been finalised.

Read the development privacy information →

1. Information that should stay private

Do not publish someone else’s home address, phone number, private email, school, workplace, identity documents, precise location or private conversations without permission. Combining small details to identify or locate a person can also violate this rule.

Information being available somewhere else does not make it appropriate to repost it to target, embarrass or intimidate a player. Do not threaten to expose information in order to influence a match or an argument.

2. Screenshots, videos and streams

Before sharing a screenshot or recording, check for account identifiers, private-room codes, messages and personal information in the background. Do not use recordings to organise harassment. Respect requests concerning private conversations and private sessions.

A public display name appearing in ordinary gameplay footage is different from deliberately collecting personal information about the person behind it. Keep reports limited to evidence relevant to the issue.

3. Younger players and unwanted pressure

Do not pressure anyone to share their age, school, photographs, location or private contact details. Do not ask younger players to hide conversations from a parent or trusted adult, move to private communication for inappropriate purposes or exchange personal material for rewards or access.

Respect the account provider’s age requirements and parental controls. Do not advise others to provide a false age or bypass consent requirements. This project has not yet announced its final audience or all public-release safeguards.

4. If information is exposed

Stop forwarding the material. Where you control the post, use the available removal tools. Report the location of the content through the appropriate service instead of copying the sensitive information into additional public messages.

If someone is in immediate danger, contact the relevant emergency service or a trusted person who can help locally. A game support page is not an emergency-response service.

Back to rule contents ↑

7. Scams, downloads & payments

• No phishing links, fake rewards, fake staff accounts or misleading giveaways.
• Do not offer stolen accounts, unauthorised access or paid methods of bypassing restrictions.
• Do not claim that an unofficial download is approved by the developer.

This website currently sells nothing, processes no payments and provides no public Unreal game download. It has no purchase or refund form. If you paid an unrelated seller, contact the relevant payment provider or marketplace through its official support route.

1. Misleading offers

Do not promise access, rewards, items, currency or staff privileges that you cannot legitimately provide. Do not advertise fake giveaways, pretend that a player has won a prize or claim that sending a password is necessary to claim something.

An offer is still misleading when it uses a small disclaimer to conceal the real purpose. Do not impersonate an official event or use the game’s name to make an unrelated payment request appear authorised.

2. Links, files and downloads

Do not distribute malware, credential-stealing pages or files disguised as game updates. Do not tell players to weaken device security in order to install an unofficial build. Check the actual destination of a link rather than relying only on its visible label or the sender’s name.

This support site currently has no verified public game download. A promotional image or a page using the game’s name does not establish that a download is official.

3. Payments and trading

This website does not currently operate a shop, process payments or provide item trading. Do not describe an unofficial sale as a Be a Weather purchase or promise an official refund for an unrelated transaction.

If you paid through another service, contact that service using its official support route. Do not send a second payment to someone claiming it is required to recover the first one.

4. Spam and advertising

Do not repeatedly post unrelated promotions, referral links or mass invitations. Do not disguise advertisements as urgent support advice. Relevant discussion of a game issue is different from flooding people with unsolicited commercial messages.

5. Reporting suspicious material

Record the location and a short description without opening suspicious downloads. Do not repost an active phishing link publicly to warn people; that can spread the risk further. Use the reporting features of the platform where the material appears.

Back to rule contents ↑

8. Reporting a problem

Keep reports factual: explain what happened, when it happened and the steps that reproduce it. Include only relevant information.

• Do not submit knowingly false reports or encourage mass-reporting.
• Do not include passwords, authentication tokens or private room codes.
• Remove unrelated personal information from screenshots and logs.
• Do not confront or harass a player while collecting evidence.

The website can prepare a report file locally. It does not yet send reports to a live support inbox or create tickets.

Prepare a report →

1. Write a useful report

Describe the issue in a short title, then explain the steps leading up to it. Include the game build, mode and approximate time if you know them. State what you expected and what actually happened. If the issue is intermittent, say so rather than claiming it always occurs.

Separate direct observations from assumptions. “The room closed when the host left” is an observation. “The host attacked my computer” is a much broader allegation and should not be presented as fact without evidence.

2. Evidence and privacy

Use relevant screenshots or short clips where available. Preserve context that helps explain the event. Do not misleadingly edit evidence, impersonate another reporter or fabricate an error message. Remove unrelated personal information and account secrets before sharing anything.

Never include complete logs without reviewing them for credentials, identifiers and private connection details. A support request does not require another player’s password or a leaked room code.

3. Responsible use of reporting

Do not report someone merely because they beat you, declined an invitation or disagreed politely. Do not knowingly submit false allegations, organise mass reports or threaten to report someone unless they give you an advantage.

An honest report that turns out to be mistaken is different from a deliberately false report. Correct factual errors when you discover them.

4. What this website currently does

The report tool creates text on your device and lets you download or copy it. It does not send a ticket, upload evidence, create a case number or notify a moderator. Share the file only through a contact route that the developer has actually provided.

5. Follow-up

When contacting Ilias Henderickx by email, keep related information together and avoid sending duplicate reports to demand attention. Response times and appeal procedures must be published before they can be relied on.

Back to rule contents ↑

9. Bugs & security issues

If you discover a bug, stop using it to gain an advantage. Record the smallest set of steps needed to explain it.

Do not test a security issue against other people’s accounts or attempt to access, copy or alter private data. Do not publicly post credentials, working attacks or sensitive logs.

For a security concern, email Ilias Henderickx at sianhenderickx@hotmail.com with a brief description; do not include secrets or other players’ private data. This page does not grant permission for security testing or promise rewards for reports.

1. Stop at the discovery

If ordinary use reveals a possible security issue, stop once you have enough information to describe it. Do not expand testing to other accounts, services or people. Discovering an unexpected response does not authorise attempts to retrieve additional private information.

This website does not provide a penetration-testing authorisation, a bug-bounty programme or permission to attack the game’s dependencies.

2. Protect data

Do not copy, publish, alter or retain another person’s private data to prove that a vulnerability exists. Do not use a discovered token, password or private key. If sensitive information appears unexpectedly, avoid spreading it and describe the issue without reproducing the secret.

3. Describe safely

A useful description includes the affected feature, the expected result, the unexpected result and a minimal explanation of the circumstances. Include the build version if available. Keep public descriptions general enough that they do not provide a ready-to-use attack against players.

A private security channel has not yet been announced for this project. Do not assume the local report-download button sends information securely to a developer; it sends nothing.

4. No threats or extortion

Do not threaten to exploit or disclose an issue unless you receive money, access or recognition. Do not offer to sell another person’s private data. No reward or response deadline is promised by these community guidelines.

5. Ordinary bugs

Visual glitches, balance concerns and loading problems generally belong in normal game feedback. If an issue might affect privacy, accounts or service security, explain that concern clearly without conducting further intrusive tests.

Back to rule contents ↑

10. Moderation & appeals

These rules describe the standards intended for future public play. A live moderation team, reporting service and appeals process are not operating through this website.

Before public testing, the developer needs to publish how reports are reviewed, which restrictions may apply, how users are informed and how decisions can be challenged. No automatic ban duration or guaranteed response time is promised here.

An Epic account restriction and a Be a Weather application-access restriction are different issues. Use Epic’s official support for restrictions on your Epic account.

1. Current status

A live Be a Weather moderation and appeals service has not been connected to this website. The standards below explain the intended approach for a future public service; they do not mean a team is currently reviewing reports or that a particular penalty system is already implemented.

2. Context and proportionality

A future review should consider the conduct, its effect on others, whether it was deliberate, whether it was repeated and the available evidence. An accidental disconnect should not be treated like a deliberate service attack. An isolated misunderstanding should not automatically be treated like sustained harassment.

Depending on the implemented system, responses could include explaining a rule, asking someone to stop, removing inappropriate content or limiting participation. These are possible responses, not a published schedule of automatic penalties.

3. Serious and repeated conduct

Threats, exploitation of players, account theft and deliberate attacks can require a different response from minor disruption. Repeating behaviour after being told to stop, evading restrictions or using alternate accounts to continue it can make the situation more serious.

4. Review and appeals

Before public moderation begins, the developer needs to publish how decisions are communicated and how a player can request review. An appeal should explain the relevant facts, identify an error or provide additional context. Harassing the reporter or the person reviewing a decision is not an appeal.

No appeal form, response deadline, case-tracking system or guaranteed outcome is available through this site today. Do not trust someone claiming they can sell you an official unban.

5. Platform decisions

Epic account decisions are handled by Epic through its own channels. A restriction on access to an unreleased Be a Weather application can be a development-permission issue rather than a punishment for misconduct. Keep those situations separate when asking for help.

Back to rule contents ↑

11. Characters, progress & rewards

Use the game’s own character and progress systems. Do not tamper with progress, duplicate rewards or distribute tools for manipulating other players’ saves.

Development builds may change features and save formats. Back up your own save before testing changes; deleting a save can reset your profile and progress.

Rewards, trading, cloud saves and progress restoration are not guaranteed by this website. There is no active reward-claim or item-trading service here.

1. Use the supported systems

Choose characters, colours and settings through the game’s available interfaces. Do not manipulate another player’s profile or distribute tools intended to falsify progress, duplicate items or bypass restrictions.

Making a backup of your own local save for recovery is different from altering values to gain an unfair advantage. A backup does not create a right to import unsupported progress into future online systems.

2. Development saves

Test builds can change their features and save formats. Keep a copy of your own data before experimenting with a different build. Do not delete a save as the first response to a cosmetic issue: it may contain character choices, settings and progress that are not recoverable elsewhere.

The appearance shown in a lobby can differ from a saved gameplay colour because the lobby applies its own presentation. Describe where the mismatch appears instead of assuming all progress has been lost.

3. Rewards and economy

Do not use automated farming, arranged fake results or known duplication bugs to obtain rewards. Do not sell unofficial reward packages or claim that editing a save creates a legitimate purchase.

The website does not guarantee specific drop rates, item values, rewards, trading rights or refunds. Those details require a clearly announced, implemented system.

4. Missing progress

Record the build you used, the mode you played and what changed. Avoid repeatedly overwriting your local save while investigating. Keep account secrets and private files out of public reports.

There is currently no connected progress-restoration service on this website. A support article or downloaded report does not mean a developer has received your save or can restore it.

5. Other players’ appearances

Do not impersonate another player to deceive people or use a cosmetic feature to display prohibited content. Choosing a similar legitimate colour or outfit is not by itself impersonation.

Back to rule contents ↑

12. Using this support website

Use the help center to find information and prepare clear problem reports. Do not use it to impersonate support, spread misleading instructions or misrepresent development features as released services.

Search runs in your browser. A downloaded or copied report is not a submitted ticket. The privacy notice explains the current website and game-data arrangements.

Be a Weather is an independent project. These community rules do not replace the terms of Epic Games, Roblox or any other platform you use. This rule center is community guidance, not a completed legal end-user licence agreement.

1. Purpose and scope

This help center explains Be a Weather’s development features, community standards and common troubleshooting steps. It is an independent project website, not an Epic Games or Roblox support portal. Links to those services lead to their own support systems.

These community guidelines describe expected behaviour. They are not a substitute for a completed privacy policy, licence agreement, platform terms or purchase terms.

2. Accurate information

Do not present edited screenshots of this website as official announcements. Do not claim that a draft feature is publicly available or that a local report has been submitted when it has only been downloaded. If information appears outdated, identify the article and the part that needs correction.

3. Search and reports

Search is performed in your browser. The report tool prepares a local text file. There is no website account, ticket inbox, attachment-upload service or live support chat in this version. Do not enter unnecessary personal information into a report.

Leaving or reloading the report page can discard what you typed. Download or copy your report if you want to keep it. A successful download message confirms only that the file was prepared, not that a support agent received it.

4. Availability and updates

Development information can change. Read the date and the current game-availability page before relying on old instructions. Website availability does not guarantee that public game servers or a public download are available.

5. Respectful feedback

You may criticise the game, the website or these rules. Explain the issue and what would improve it. Do not use feedback as a way to threaten people, expose private information or spread malicious files.

6. Rule changes

Material updates should be explained clearly and dated. Where a rule is unclear, ask for clarification through an available contact route. A future clarification should not be misrepresented as proof that every past mistake was intentional misconduct.

Back to rule contents ↑

13. Chat, voice & communication

Communicate to help the game

Where a build offers chat or voice, use it to coordinate, ask questions and enjoy the match. Call out an approaching hazard, explain a strategy or congratulate someone. Disagreeing about a tactic is allowed. Repeatedly attacking the person who chose it is not. These standards also apply to room names, invitation messages and other text that players can see.

Keep conversations usable

Do not flood a channel with repeated messages, long blocks of symbols, microphone noise, sound effects or unwanted advertisements. Do not repeatedly contact someone who has asked you to stop. Sending the same message through several accounts or asking friends to continue it is still unwanted contact. When a conversation becomes heated, step back rather than trying to win an argument through volume.

Voice etiquette

Use a comfortable microphone level and avoid deliberately playing loud or startling audio. Respect players who cannot or do not want to speak. Nobody must join a private call, reveal their voice or move to another application to prove that they deserve a place in a match. If communication controls are available, use mute or block when appropriate; their absence never makes harassment acceptable.

Language and context

Players may speak different languages and make mistakes. Do not treat an accent, spelling error or translation problem as permission to ridicule someone. A brief tactical instruction is different from repeated hostile demands. Friendly joking should stop when another person says that it is unwelcome.

Example

“Please stay near the safe area next round” is useful feedback. Following a player between rooms to insult them for losing is not. Voice and chat features are build-dependent; this article does not announce that either system is currently available.

Back to rule contents ↑

14. Names, profiles & player-created content

Choose an appropriate identity

Use names and profile content that other players can encounter without being targeted or deceived. Do not put threats, hateful messages, another person’s private information, sexual solicitation or scam links into a display name. Deliberately misspelling a prohibited message, substituting symbols or placing it in an image does not change its meaning.

Do not impersonate

Do not present yourself as a Be a Weather developer, moderator, Epic employee or official support representative when you are not one. A name such as “official support” combined with requests for passwords is deceptive even if you later describe it as a joke. Do not copy someone’s identity to damage their reputation or trick their friends into sending information.

Cosmetic expression

Players may choose different colours and styles using supported game options. A preferred colour, character choice or ordinary outfit is not a reason to exclude or insult someone. Custom names, images and uploads are only permitted where the game actually supports them; this page does not create an upload service or authorize modifying someone else’s content.

Content belonging to others

Do not upload or redistribute another person’s private photographs, recordings or creations as though they belong to you. Get permission where it is needed. A player appearing in your match has not automatically agreed to endorse your channel, product or community.

Correcting a problem

If you realize that your visible content exposes someone’s information or misleadingly claims official status, remove or change it through the available platform controls. Explain an accidental mistake clearly if it is reviewed. Do not recreate the same content under a different spelling to avoid that correction.

Back to rule contents ↑

15. Harassment, hate & threats

Competition is not personal abuse

Winning, losing and disagreeing are normal parts of competitive play. Threatening a player, targeting their family, encouraging others to abuse them or repeatedly following them to continue an argument is not. Harassment can happen through a single serious incident or a pattern of smaller actions across several matches.

No hateful targeting

Do not attack people because of characteristics such as race, ethnicity, nationality, religion, disability, gender or sexual orientation. Do not use dehumanizing comparisons or tell a player that people like them should be harmed or excluded. Quoting hateful language to target someone remains harmful even when surrounded by a claim that it is only a meme.

Threats and intimidation

Do not threaten physical harm, publish someone’s location, threaten to expose private information or pretend to arrange an attack on them. Do not pressure someone to stay in a room by threatening their account, their friends or their reputation. Claims that you can identify or punish a player outside the game can be intimidating even when they are false.

Coordinated harassment

Do not organize a group to overwhelm someone with invitations, messages, false reports or hostile comments. Asking your audience to “teach them a lesson” can cause the same harm as contacting the player yourself. Leaving the original room does not give you permission to continue the incident elsewhere.

When an incident happens

Stop engaging if doing so helps you leave the situation safely. Save only the evidence needed to explain what happened, without circulating private information. Use available platform safety tools. The local report download on this website is not an emergency service and does not notify a moderation team.

Back to rule contents ↑

16. Teams, cooperation & match manipulation

Play the role assigned by the mode

Cooperation is welcome when the rules of the selected mode allow it. Survivors can coordinate movement and warn teammates about hazards. The Weather player can choose abilities and tactics supported by the game. Do not secretly work with an opposing player to deny everyone else a fair round or manipulate an outcome that is meant to be competitive.

Friendly practice versus arranged results

In a clearly identified private practice room, players may agree to experiment, teach controls or repeat a scenario. That is different from arranging fake competitive results, farming rewards through deliberately thrown matches or pretending that a rehearsed result was fairly earned. Practice rules should be explained before the session begins.

Do not sabotage teammates

Do not deliberately block a teammate’s escape, reveal their position to opponents through an outside channel or repeatedly disrupt them to force a loss. An accidental collision or unsuccessful strategy is not automatically sabotage. Look at what actually happened and whether it was deliberate instead of assuming that every mistake was malicious.

Outside information

Do not use a friend’s spectator view or live stream to obtain information that your own role is meant to lack. Discussing a completed round is different from receiving a live location feed during a current one. If a casual room explicitly allows coaching, make that clear to everyone and keep it separate from any future competitive mode.

Rewards and ranking

Do not sell arranged wins, account boosting or guaranteed progress. This rule applies if those systems become available; it does not claim that a ranked ladder, trading system or competitive reward economy is already running.

Back to rule contents ↑

17. Joining, leaving & active participation

Join when you are ready

Read the room description and mode before joining. Take a moment to check your controls, audio and connection where possible. In a private session, tell the host if you only have time for one round. Nobody can guarantee an uninterrupted connection, but clear communication prevents avoidable confusion.

Stay involved

Participate in the round instead of intentionally remaining inactive to collect progress or occupy a slot. Do not use tools that simulate activity to bypass an idle check. Briefly stepping away for an unexpected interruption is different from repeatedly joining sessions with no intention of playing.

Leaving a match

You can leave an uncomfortable or unsafe interaction. Do not threaten another player to make them stay. At the same time, do not repeatedly join and leave to disrupt a lobby, evade a role assignment or manipulate a match result. A disconnect alone does not prove deliberate misconduct.

Connection problems

If your connection fails, note the approximate time, build and message shown. Rejoin through the supported controls if that is available. Do not repeatedly trigger reconnect requests at a high rate or install unofficial “connection fix” tools from strangers. This website does not promise reconnect protection, restored rewards or a penalty-free recovery system.

Host responsibilities

A private host should explain planned restarts or changes when practical. Ending a session unexpectedly may interrupt everyone, so avoid presenting an experimental session as a guaranteed service. A host’s connection can affect the room, and a lost host is a technical event rather than proof that every guest was banned.

Back to rule contents ↑

18. Spectators, streams & recordings

Watch without disrupting

If a build includes spectating, use it to watch or learn. Do not use spectator access to interfere with an active match, reveal hidden positions to one side or continue unwanted contact with a participant. Being outside the active round does not remove the community rules.

Streaming responsibly

Before sharing footage, check for private room codes, personal messages, account information and other details that should not be public. Crop or hide sensitive elements. Showing a game screen can unintentionally reveal a notification from another application, so review recordings before uploading them.

Do not weaponize an audience

Do not ask viewers to join someone’s room, overwhelm their invitations, submit false reports or contact them outside the game. Disagreement with a player does not justify sending an audience after them. If you discuss an incident publicly, avoid sharing details that identify private individuals unnecessarily.

Stream sniping and live information

Do not deliberately exploit another participant’s broadcast to gain information that is hidden in your own game. Joining a public session by coincidence is different from repeatedly tracking a specific player to disrupt them. A streamer’s visibility does not make targeted harassment acceptable.

Honest presentation

Label edited, staged or private practice footage accurately when the distinction matters. Do not present an old test build as proof of current public availability. Creating a fan video does not make you an official representative of Be a Weather or its platform providers, and this article does not grant rights to third-party music or other protected material.

Back to rule contents ↑

19. Private host responsibilities & house rules

Explain the session

A host should tell guests what kind of room they are joining: ordinary play, learning controls, testing abilities or an agreed challenge. Explain whether bots are enabled and what settings are supported in that build. Do not promise configurable features that the room does not actually offer.

Agree before changing expectations

If you want a special challenge, such as avoiding a particular ability for practice, explain it before starting. Guests should have a reasonable chance to decline or leave. Do not announce a hidden rule only after someone wins and then accuse them of cheating for not following it.

House rules have limits

A private room may set reasonable participation expectations, but it cannot suspend the standards against harassment, scams, privacy violations or account abuse. “The host allowed it” is not an excuse for threatening a guest. Do not require passwords, personal photographs or payment to prove that someone is trustworthy.

Invitations and access

Share room codes only with the intended participants. Ask before forwarding another host’s invitation to a larger group. If a code is exposed, use available room controls to limit access or start a new session if necessary. Do not advertise a private code as a public event without the host’s agreement.

Technical limitations

Hosting through a player’s machine depends on their connection and the game’s networking implementation. A private room is not a promise of dedicated hosting, permanent availability or an always-online server. This website does not provide a room-management backend and cannot remove guests or recover an expired room from a downloaded report.

Back to rule contents ↑

20. Bots, offline play & practice sessions

Know the type of session

Offline practice and online play serve different purposes. Offline sessions can help you learn movement, abilities and the map without depending on other people. Bot options depend on the current build; only settings that are actually shown and functioning should be described as available.

Be honest about opponents

Do not deliberately label a bot-only recording as a victory against real players when the distinction is central to the claim. In a private session, tell guests whether bots are included. A bot’s display name or behaviour should not be treated as evidence that a particular real person is present.

Practice safely

Experiment with supported settings and controls. Keep notes on unexpected behaviour rather than repeatedly exploiting it for progress. If a bot becomes stuck, fails to react or spawns incorrectly, describe its position, selected mode and what happened just before the issue.

No false progression promises

Offline activity does not automatically qualify for online rewards, rankings or achievements. Whether progress transfers depends on an implemented system and published game information. Do not sell an offline save or bot-farming method as a guaranteed way to obtain legitimate online items.

Distinguish bugs from misconduct

A malfunctioning bot is a software issue, not a player to punish. Do not name or accuse a real player based only on a similar bot name. Reports about bots should explain reproducible behaviour, while reports about people should explain observed conduct without guessing about their identity or intentions.

Back to rule contents ↑

21. Accessibility, skill levels & inclusive play

Welcome different ways of playing

Players have different experience levels, reaction speeds and ways of interacting with games. Do not mock someone for learning controls, taking longer to respond, using a different input device or needing written instructions. A private practice room can be a useful place to explain one mechanic at a time.

Communication choices

Do not require a person to disclose a disability, medical condition or other private information to justify a communication preference. If a player cannot use voice, use available text or agreed signals where practical. Avoid treating silence as proof of bad intentions.

Accessibility and fair play

Ordinary supported control remapping and accessibility settings are not cheating. Tools that reveal hidden information, automate competitive decisions or alter protected game behaviour raise different concerns. This website does not certify third-party software or provide a complete approved-device list. When a tool’s function is unclear, describe what it does without sharing credentials or private medical information.

Helpful feedback

When suggesting an accessibility improvement, explain the barrier and the desired result: for example, text that is too small, an effect that obscures an opponent, or a control that cannot be rebound. You do not need to provide a diagnosis. Screenshots can help if they do not expose personal data.

No guaranteed features

These expectations do not mean that every accessibility feature is implemented. Players should be able to describe problems without being blamed for them. A feature request is not a promise of a release date, but it should identify a concrete issue the developer can evaluate.

Back to rule contents ↑

22. Community events, challenges & competitions

Identify the organizer

A player-run challenge is not automatically an official Be a Weather event. Make clear who is organizing it and do not use official-looking statements to imply developer sponsorship. Participants should understand whether they are joining casual practice, a fan competition or an announced official event.

Publish clear expectations

Before an event begins, explain the mode, permitted settings, method of choosing winners and what happens if someone disconnects. Do not change the winning condition after seeing the result. If the available build cannot reliably support a proposed rule, adjust the event instead of pretending the game can enforce it.

Prizes and entry

Do not promise prizes you cannot provide or falsely claim that the developer will supply rewards. Do not ask participants for account passwords, verification codes or session tokens to register or receive a prize. This website does not operate tournaments, entry payments, giveaways or prize fulfillment.

Disputes

Keep disagreement focused on the event facts. Preserve relevant screenshots or match details without spreading personal information. Do not pressure a winner into surrendering an account or item, and do not organize harassment against an organizer over an unresolved result.

Separate rules may be needed

A real public competition may require its own eligibility conditions, prize details and appropriate review before launch. These community guidelines are not a ready-made tournament contract. They do not authorize gambling, paid entry arrangements or the use of another company’s branding to imply endorsement.

Back to rule contents ↑

23. Downloads, links & unofficial tools

Check before opening

Be cautious with links or installers sent by strangers, especially if they promise free rewards, secret abilities, account verification or a guaranteed fix. A familiar logo is not proof that a page is official. Check the destination and whether the download is actually announced through a trusted project or platform channel.

Do not distribute harmful files

Do not send malware, credential-stealing tools, disguised executables or instructions intended to compromise another person’s device. Do not rename a program to look like an image or support document. Calling it a prank does not make it acceptable.

Support should not need your secrets

Never give another player your password, two-factor authentication code, recovery code or access token. Do not paste unreviewed account logs into a public chat. A legitimate troubleshooting question can usually begin with an error message, the build version and steps to reproduce the issue.

Unofficial modifications

This website does not maintain an approved mod directory. Do not describe an unofficial tool as developer-approved without a real announcement. Tools that change competitive behaviour or expose hidden data may violate fair-play expectations even when they do not contain malware.

If something looks suspicious

Stop using the link or file and avoid forwarding it as a warning in a way that exposes others to it. Record the sender and relevant message if needed. For an Epic account issue, use Epic’s official account-security and support channels rather than the contact details supplied by the suspicious sender.

Back to rule contents ↑

24. Evidence, report quality & corrections

Report what you observed

A useful report separates facts from interpretation. Describe what happened, when it happened, which build and mode were involved, and what you expected instead. “The player moved through this wall twice” is more useful than “everyone knows they are a hacker.” Explain uncertainty instead of filling gaps with guesses.

Keep enough context

A short clip or screenshot can omit what happened before it. Include relevant context when available, but do not collect or publish unrelated private conversations. Preserve an original copy for your own reference if you make a cropped version to remove sensitive information.

Do not fabricate evidence

Do not alter a screenshot, create a fake conversation, impersonate a witness or present staged footage as a real incident. Do not submit a report to retaliate against someone for winning or disagreeing with you. Several people repeating the same accusation does not establish that it is true.

Correct mistakes

If you discover that a report named the wrong person or misunderstood a technical issue, clearly correct it through the same available channel. An honest correction is more helpful than continuing an accusation to avoid embarrassment. Do not contact the reported player to demand a confession or threaten public exposure.

Local report limitation

The website currently prepares a text report on your own device. Downloading it does not submit evidence, create a case or start an investigation. Keep the file only as long as you need it and review its contents before sharing it by email to Ilias Henderickx at sianhenderickx@hotmail.com.

Back to rule contents ↑

25. Personal boundaries & younger players

Keep interaction focused on the game

Players do not owe one another personal details or private contact. Do not pressure someone to reveal their real name, age, school, address, telephone number or social accounts. A friendly conversation is not permission to repeatedly ask for information after the person declines.

No coercion or exploitation

Do not offer access, rewards, status or friendship in exchange for intimate content, private images or secrecy about an uncomfortable interaction. Do not threaten to remove someone from a group because they refuse personal demands. These expectations apply regardless of the ages of the people involved.

Respect refusal

If someone says no, leaves a conversation or stops replying, do not pursue them through other accounts or ask others to pressure them. Do not frame a refusal as a loyalty test. Room hosts and experienced players have no special authority over another person’s private life.

When help is needed

If an interaction makes you uncomfortable, leave it and talk to someone you trust. Younger players can ask a parent, guardian or another trusted adult for help using platform safety controls. Do not send additional personal information to someone claiming that it is necessary to investigate an incident.

Service boundaries

This support website is not an emergency service, safeguarding hotline or live reporting channel. It does not establish an age rating or replace platform age requirements and parental settings. Public availability and any age-related access conditions must be communicated accurately when the game is released.

Back to rule contents ↑

26. How to read these rules & handle uncertainty

Examples explain a principle

The examples in this handbook help explain expected behaviour. They are not a list of every possible action. A new way to steal an account is still account abuse even if the exact method does not appear here. At the same time, a vague suspicion is not proof that a player has broken a rule.

Consider the situation

Distinguish accidental errors, technical limitations and deliberate misconduct. A player disappearing may have disconnected. A surprising movement may be a bug. A poorly translated message may not express the meaning that another reader assumes. Relevant context should be considered before drawing a conclusion.

No loophole hunting

Do not deliberately recreate prohibited conduct using different spelling, accounts, channels or tools and argue that the exact wording was not listed. Asking another person to carry out harassment or cheating on your behalf does not separate you from the conduct.

Good-faith questions

It is reasonable to ask whether an unfamiliar tool, event format or private-room challenge fits the rules. Describe the actual behaviour and who it affects. Do not publish a dangerous technique merely to ask whether it is allowed. Questions can be emailed to Ilias Henderickx at sianhenderickx@hotmail.com. Sending a question does not itself grant permission or approval.

Community guidance and platform terms

These are original Be a Weather community guidelines for a project in development. They are not copied Rocket League rules, a finalized legal agreement or a promise of functioning enforcement systems. Platform requirements still apply through the relevant provider. Future material changes should be dated and communicated clearly, with real reporting and review arrangements published before those services are represented as available.

Back to rule contents ↑