


The engine recreates many other games such as Tiberian Dawn and Dune 2000. This Wiki should not be confused with the official documentation, which is a Wiki about the OpenRA engine itself. This Wiki aims to document all there is to know about "OpenRA - Red Alert". There's a vibrant community and an active competitive scene surrounding this recreation. OpenRA - Red Alert Is a Free and Open Source recreation of the classical real-time strategy game by Westwood, "Command & Conquer: Red Alert". This can not be handled by the few people that develop the engine, but it would be a mistake to decrease the motivation for new people to work on integration of web services.The best way to browse this Wiki is through the search bar above. Instead, we should improve the possibilities to explore the RC ingame, integrate it with player profiles etc. For the second case, I don't see how lazyness can justify a change that effectively demotivates EVERYONE to use the RC services, which help both the community and map makers. The first case can be handled by sharing the map on your local network and have people add it to their map folder. satisfy people who are to lazy to create an RC account / upload their maps but still want an automated distribution system.The only improvements which I can see are to

Security implications due to P2P download inside of an application from untrusted sources

No linting of maps and protection against corrupted / incompatible maps, We have no possibility to track download counts etc. Maps that are not uploaded to the RC (or some other hosting service) are not available for the public and not protected against local data loss These are my considerations which make me believe that this is a step backwards:īy allowing P2P download, we eliminate the motivation to upload maps to the RC The peer-to-peer map download conflicts IMO with the concept of the resource center and its features.
