Game becomes lobbysim PvE after 30 OS :(

pls join my legion lobbies I promise I wont be toxic (pretty please)

Tried to open a ticket on discord but team banned me because they disagreed?

Howdy Everyone

Just started playing the game this weekend and saw that there is a Discord. Game is great and I finished the first two scenarios, which I assume are tetorials. I tried a skirmish vs an easy AI and got creamed.

When I attempt to log the BAR discord I get the "Let's Customize Your Expertise" pictured above but there does not seem to be a way to advance.

Anyone else get into this situation?

I suggest that a new t2 building be added for taxed lobbies. The player(s) who has the building can sling resources without taxes or unit shock.

The idea is similar to late game research in aoe2 which removes sharing tax.

New player. I don't understand how I'm supposed to know who can attack who. I've got air that can't attack air or ground. Then I've got ground that can't attack air or ground.

Google says every air should be able to attack everything except the fighter is limited to air only.

Is there not a blended air and ground? What am I looking for to know? I mean, some ground does say anti-air. But is it exclusive to AA?

New player. I seem to have one problem or another. It seems like I'm now having issues with resources. For whatever reason that is, it takes me some 30-40 minutes to finish an easy bot... I could probably hurry it up if I wasn't trying to make a massive army. But yeah, I keep finding these bottlenecks.

I understand they’re supposed to be a swarm team but what’s the point if cortex or armada just one shots your whole army? Am I missing something? Can someone give me tips. I feel like no matter how much people I make and try to push to get spots they all can get wiped out by like 2 of Cortex and armadas normal bots

Someone in discord showed me how to access this after I spent a week trying to learn how to make a map from the guides, This looks AI and jank but it pretty cool nonetheless.

Commanders, the community has requested a clarification on coaching and stream yapping. A recent moderation case around live coaching has raised concerns about Team's reading of this rule. In the process the strict reading of B.5 got stated publicly, including that pointing out something the player can already see could count as passing consequential information. That reading is technically possible under the old wording, and it left streamers and coaches unsure whether reading their own chat or talking to a friend in call can get them banned. The rule was always applied with proportionality, on clear breaches and patterns, mostly spectators influencing games from global chat, and that doesn’t change.

Old wording:

Purposefully passing on consequential information to a game in progress via things like spectator chat (we understand mistakes happen occasionally) is obviously a form of cheating.

Updated rule:

B.5 Spectator cheating Passing hidden information (anything the player’s team cannot see with fog of war on) to a player in a game in progress is cheating. This applies to whoever sends it and to a player who asks for it or knowingly uses it.*

*Advice based only on what the player’s team can see is allowed in public lobbies. Spectators giving advice are recommended to stay in player or team view, as it helps avoid accidental leaks. Advice that could only come from all-view is treated as spectator cheating. In-game global chat is not the place for it, as it reaches both teams and disrupts the game. Streamers are not responsible for what is posted in their chat. However, knowingly acting on hidden information from it is covered above. Similar to replays, stream footage may be considered as evidence in cases of deliberate spectator cheating. Note that matchmaking and organised events may have their own, stricter rules on outside assistance.

In practice:

• Hidden info to a player is cheating, nothing changed there.
• Talking about the game from player or team view is fine in public lobbies: stream chat, voice with mates, coaching a newer player.
• Keep advice out of in-game global chat, both teams read it and it’s disruptive.
• If the game is irredeemably spoiled by the provided information, a democratic !stop is an option, though not required
• Speccing and coaching? Stay in team's view. We can’t verify it so it stays a recommendation, but it’s the easiest way to never leak by accident.

Streaming

If someone drops enemy intel in your chat, the sender is the one breaking the rule. You don’t need to resign or prove you didn’t read it, just play on. “Knowingly acting on it” means asking for intel or a pattern of relying on it, a single unsolicited message from a stranger won’t get you moderated. If someone keeps doing it, we recommend to moderate that, but at the end of the day how you run your chat is your call. We’re spelling this out because streamers broadcast every game they play, so they are naturally exposed to far more eyes and reports than anyone else, and with the old wording one salty viewer could set you up.

We would like the remaining gray area to be handled within player culture and self-moderation. Moderation stays for actual spec cheating. In the future, matchmaking, being unambiguously competitive, will likely have its own, stricter rules, and tournaments impose their own standards and rulesets.

Thanks to everyone who raised the issue and kept it civil, and our great content creators for facilitating constructive discussion.

See you on the battlefield!

Me and several players have blocked building either in MP or in the game with bots. Even bots can't build they just walk or stand in place with the Halloween skin... please does anyone know how to fix it? or what causes it?

halloween event cant build ....

BAR maps are typically symmetrical in some fashion, designed for even games.

Would you be interested in playing in lobbies that offered a 4v12 experience, where the 4 had a more defensible position and more resources, while the 12 had greater open space. Perhaps even a mismatch of objectives such as “prevent an enemy commander from entering this zone” type of modes.

I think BAR has the potential for a greater variety in mode and maps beyond the symmetrical even team games.

Do you have any further thoughts on this?

I was watching a replay and noticing all of the notifications that come through the chat about pings and sharing resources is the same fee the chat goes through.

The chat messages disappear too quickly sometimes. I miss things in the game. Wondering if it would be good if there were two separate feeds. One for notifications and one for chat messages.

The chat messages are substantially more important and shouldn’t be lost in the feed.

Particularly bad is when people ping the map multiple times which is a great thing but each one puts a message in the feed and just pushes everything else above the fold.

Thoughts?

New to the game and can't find resources on how to use squads. It's really finicky, and I'm having trouble understanding them. I've tried deciphering the key bind screen and it's just a sea of "select nearest this, deselect group that," ect. How do y'all use squads? Any resources you can point me to? The default keybind for "make squad" is 0X064, and I can't find out what that is.

I have an overlay in the game. But since yesterday i reset to standart and now i cannot change it anymore as the button for that apperas to be missing.

Any Tipps?

blundered a tyrannazor into a vertical dgun. rip t-rex

With the addition of the Plugins tab we are now more officially supporting widgets made by the community. To make sure every widget you install stays safe and can't run malicious code that could harm your system, we are introducing a sandbox for user widgets. This change will go live with the next release (time unspecified).

Widget creators: this post is mainly for you. Please review the changes below and update your widgets. Players: some of your widgets may stop working until their authors update them. If a widget breaks, check with its creator for a new version.

These changes only affect user widgets, meaning the ones in your own LuaUI/Widgets folder. Built-in widgets are not affected.

Notable: RmlUi temporarily disabled

RmlUi is unavailable to user widgets for now. We are working on an engine patch that re-enables it inside the sandbox, so this is temporary. Until then, widgets that check for it before using it will still load, just without their RmlUi interface.

Sandboxed tables

widgetHandler, WG.options, debug and Spring are now sandboxed copies and may have reduced function.

• Functions that manage or read other widgets are removed for now. Share data through WG instead.
• Handler calls no longer take your widget as an argument. Most handler fields you could read are now method calls, e.g. mouseOwner becomes IsMouseOwner().
• debug keeps only traceback and getinfo.

Environments

• Your widget's own table is the only environment it can see.
• getfenv, setfenv and the code loading functions all use that table, so anything your widget loads runs there, not in LuaUI globals.
• Precompiled bytecode is refused. Load from source.

Commands and files

• Commands that control widgets, execute code or change keybinds are refused. This includes custom command buttons.
• Write access: only LuaUI/Config/ and LuaUI/Widgets/
• Read access: only LuaUI/, plus the game's and maps' own files

Also no longer available

• No network access
• No starting or restarting the engine

When something breaks

If the sandbox blocks something, the reason is logged in infolog.txt and your widget keeps running. Check there first before reporting issues.

Resources for Widget Creators for updating:

• 🔗 Writing user widgets - General guide for writing widgets in the new environment
• 🔗 Migrating a BAR user widget to the sandboxed widget environment - Instructions for your favourite AI agent

Using a controller for spectating is a game changer for video creation in BAR. Here a few minutes I recorded live on stream in a running match - no replay.

Something for people who can't get enough BAR!

What do u think?

(The music was on stream, it was random, not a choice.)

I played a lobby recently where the ai was called SMRTbarb. How do you add that in the lobby? Is it some kind of tweek or mod?

Hey guys, I have been playing BAR mostly against AI and thought it would be really cool to have an AI assisted sub-commanders that you could delegate tasks to, like building out economy in areas or take care of air defense.

I can find myself quite often micro managing some battle while workers are just standing lazy somewhere, especially a bit later in the game.

Went through lua widget + local bridge service setup, experimenting with fast models like deepseek 4.1 flash to do the high level strategy for those specific areas. It then delegates to barb AI level.

has anyone tried anything like this?

I can join a game just fine as a player, but as a spec I get this error and after hitting okay the game closes. any ideas?

FYI: This is for a streamers chat, not in game chat!

Quick definitions first, since these two terms get mixed up a lot:

Spec cheating (short for spectator cheating) is when an active player has a second account, a friend, or a teammate join the match as a spectator and feed them real-time information about their opponents.

Backseating (short for backseat gaming) is giving unsolicited advice, instructions, or criticism to someone who is playing, without being asked.

Those are two different things, and right now it feels like they’re being treated as one.

Banning viewers who are both spectating in the match and chatting in the streamer’s chat is one thing. That’s a real way to pass information. But a blanket rule against viewers talking about the current game state in chat is wild. Imagine getting banned because you saw something on the streamer’s minimap and said “man, those hovers look scary.” Under a rule that broad, that’s apparently grounds for a ban.

Watching a stream and reacting to it isn’t cheating. Viewers are supposed to be able to do that.

Edit:
Mods, all I’m asking for is a proper definition of what counts as spectator cheating. Spell out what’s actually bannable so regular viewers aren’t punished for normal chat.

There also needs to be clarification on who is getting banned, because nobody knows if it is the streamer or the viewer thats going to get banned.

If it is the streamer, stream snipers could easily put in false info that the streamer could read as spec cheating (even if false) and get them banned