OpenRA

Does viewtopic.php?f=82&t=20562 answer your question?

You should use an IDE like Visual Studio Community 2019 to add and edit those files. It'll make it a lot easier for you (i.e. automatically adding the files to the csproj, or displaying errors).

I don't think there is a really easy way to do this currently. The best is probably using SpawnActorOnDeath with dummy actors that look like flames.

Saying that "mammooth" tanks underperformed in the last release is just ridiculous. I suppose you've never even played a game online. 0/8 bait.

A bit offtopic but still: I think a faster release cycle will at least mitigate the "playtesting problem" somewhat.

We don't really have a exhaustive manual on that, the best is probably https://github.com/OpenRA/OpenRA/wiki/Map-scripting and the links mentioned there. Looking at the existing missions is also a good starting point.

Thanks for the report. I opened a ticket (OpenRA/OpenRA#17354) so we don't forget about this.

That is odd, I just added a ClassicProductionQueue for Building.GDI (Group: Building) to the Player actor in TD and it worked fine. Which version are you using? (I suppose this could already be fixed, since the new spectator UI has the Production tab on F4. ^^)

Sadly I don't think this is currently possible. We have an open issue for it: OpenRA/OpenRA#6433

Ah right, I forgot that, sorry. In that case using Lua might really be the cleanest solution for you. I think looking at the existing mission yaml and script files would be a good starting point.

The easiest solution for you is probably setting an mcv owned by Creeps outside of the playable map area and removing NonCombatant.

Neat. Does the track have a name?

To A2/A3: VS 2019 Community is free, you just need to log in with a Microsoft or Skype account after the thirty day trial period.
For C1: You could try using Visual Studio Code with C# extensions.

Tick and Render ms are the average ms spent either ticking or rendering during the last second (one second usually equals 25 ticks). Batches are the amount of times the game had to wait on the GPU (e.g. wait for a render to finish to change GPU parameters). Iirc the graph simply visualizes those val...

You can enable performance text and graph in the settings (advanced section), they can give some hints.

The same, some games are soviet vs soviet.