NodSaibot

I suggest a bigger call to action on joining the community (mostly Discord, but also the forums). Knowing there's people in the community would let people know the game isn't dead if they go onto the launcher and see 5 people online

Was this on outposts? It’s not supposed to be that slow. Will be fixed in patch.

Elitest PUG? Watch any recent pug video and tell me which player I am. I almost never play PUGs.

Yeah, you're expecting teamwork in pubs. Good luck with that And yeah, everyone hates Snow. It surely never get's voted in. Liking maps and maps getting voted in are not necessary correlated.

Have you played recently? lol. The flechette hardly compares to the anti inf they used to be. Bad or lazy map design? Usually to counter SBH or stop early rushes from ruining games.

I think having a higher credit tick rate and lowering the harvy dump amount would be beneficial for the game. Personally I also don't like that you have to hold the button to fire the pic/railgun. Maybe lowering the dmg resistance of the meds/mammies would suffice, not really sure.

For this tutorial, it is expected that you have at least a little bit of knowledge of UScript and programming. There are many reasons you may want to change, interact with or edit the Purchase System. A few good examples would be to add new vehicles, replacing the vehicles with custom versions or for changing prices. The recent patch has made adding new vehicles slightly easier than before. For this specific example, I will be showing you 2 different classes for a single mutator. Our first class will be the "main" class, which will replace the original Purchase System, with a new one. The second class will be the extended Purchase System. Replacing the PurchaseSystem class in the game is actually quite easy. All you need to do is use the CheckReplacement function. class Rx_Mutator_NewPurchaseSystem extends Rx_Mutator; function bool CheckReplacement(Actor Other) { if(Other.IsA('Rx_TeamInfo')) { Rx_Game(WorldInfo.Game).PurchaseSystem = class'Rx_NewPurchaseSystem'; } return true; } No real fancy work is done here, it's very self explanatory. We will look at Rx_PurchaseSystem and search for the things we need to change to get the results we want. We are going to: change the price of items (beacon, airstrike and repair tool) replace a vehicle give ion cannon beacons to Nod Most of this starts at the DefaultProperties. The classes that can be purchased are defined here. However, the prices for the items are controlled via config files. We will be using the DefaultProperties instead of a config file for prices, for the sake of simplicity. However, if this was a mutator, it would be advised to set it via config, as this would allow you to change the price in the config file, instead of creating a whole new version of the mutator. For the vehicles, all we need to do is change one of the items in the arrays of NodVehicleClasses or GDIVehicleClasses. We will also replace the Nuclear Strike beacon with the Ion Cannon Strike beacon. However, the button for Nod will still be the nuke, they'll just receive the ion beacon. Unfortunately, items do not have PTInfos, and the way they are displayed is hard coded in a HUD class, and I don't care to go into that sort of detail for this tutorial. var array<class<Rx_Vehicle_PTInfo> > NewNodVehicles; simulated event PostBeginPlay() { super.PostBeginPlay(); ReplaceVehicleClasses(); GiveNodIonCannon(); } simulated function ReplaceVehicleClasses() { for(i=0; i < NewNodVehicles.Length; i++) NodVehicleClasses[i] = NewNodVehicles[i]; } simulated function GiveNodIonCannon() { NodItemClasses[0] = class'Rx_Weapon_IonCannonBeacon' } DefaultProperties { NewNodVehicles[0] = class'RenX_Game.Rx_Vehicle_Nod_Buggy_PTInfo' NewNodVehicles[1] = class'RenX_Game.Rx_Vehicle_Nod_APC_PTInfo' NewNodVehicles[2] = class'RenX_Game.Rx_Vehicle_Nod_Artillery_PTInfo' NewNodVehicles[3] = class'RenX_Game.Rx_Vehicle_Nod_FlameTank_PTInfo' NewNodVehicles[4] = class'Rx_NewPurchaseSystem.Rx_Vehicle_Nod_LightTank_PTInfo' // Assuming these 2 classes exist in your mutator NewNodVehicles[5] = class'Rx_NewPurchaseSystem.Rx_Vehicle_Nod_StealthTank_PTInfo' NewNodVehicles[6] = class'RenX_Game.Rx_Vehicle_Nod_Chinook_PTInfo' NewNodVehicles[7] = class'RenX_Game.Rx_Vehicle_Nod_Apache_PTInfo' } To break this down quickly, we call ReplaceVehicleClasses in PostBeginPlay because the function UpdateMapSpecificVehicleClasses is called there, and if the map has different than default vehicles, it would override our custom vehicle classes. Also note how super is called before we call our function, so that ReplaceVehicleClasses will be called after UpdateMapSpecificVehicleClasses. ReplaceVehicleClasses is just a simple for loop that calls the NodVehicleClasses array from the default properties. To change the prices, all we need to do is define a new array of prices and change the function that is called to get the prices. var int NewGDIItemPrices[8]; var int NewNodItemPrices[8]; simulated function int GetItemPrices(byte teamID, int charid) { if (teamID == TEAM_GDI) return NewGDIItemPrices[charid]; else return NewNodItemPrices[charid]; } DefaultProperties { NewGDIItemPrices[0] = 700 // (Beacon) NewGDIItemPrices[1] = 400 // (Airstrike) NewGDIItemPrices[2] = 0 // (Repair Tool) NewGDIItemPrices[3] = 150 NewGDIItemPrices[4] = 150 NewGDIItemPrices[5] = 200 NewGDIItemPrices[6] = 300 NewGDIItemPrices[7] = 300 NewNodItemPrices[0] = 1500 // (Beacon) NewNodItemPrices[1] = 2000 // (Airstrike) NewNodItemPrices[2] = 100 // (Repair Tool) NewNodItemPrices[3] = 150 NewNodItemPrices[4] = 150 NewNodItemPrices[5] = 200 NewNodItemPrices[6] = 300 NewNodItemPrices[7] = 300 } This is also extremely cut and dry. Simply define new prices and overwrite the original function with one that returns the prices from your new array. Only worry about the first 3 , the last 5 aren't used for anything currently. You will need to combine the last 2 code blocks into 1 class, Rx_NewPurchaseSystem class Rx_NewPurchaseSystem extends Rx_PurchaseSystem; ... Feel free to ask any questions if you don't understand something, or if it doesn't compile/work for you.

Airstrike frequency is also a per map setting. We can simply increase the time between airstrikes.

Well, queuing airstrikes doesn't really make sense to me, as if you queue it at a specific spot, the tanks/enemies could be long gone by the time it's ready to go. And the airstrikes are already pretty powerful, I don't think making them better would be good

[Mutator] Big Head View File This mutator will scale heads based on k/d. There are no configurable options. Put all files in UDKGame\CookedPC\. Add ?Mutator=Rx_Mutator_BigHead.Rx_Mutator_BigHead to your server startup line. Submitter taishō Submitted 09/24/2018 Category Modifications

Dead NA player base? Where the NA haters at now

Delete it and find out. It's almost as if there's some magical place where files you delete go to and you can restore them if necessary

Been going strong? Game has been around for around 10~ years? Something like that. I've only been around for 5, it's been decently active since then. If you use Discord, you should join ours! https://discord.gg/renegadex

Admittedly I don't know much about hardware, but I would say that sounds fine. Don't quote me on this or buy it just because I said it's good though.

Can't tell if trolling lol Is your game using your GPU at all? Sometimes it has trouble finding the correct graphics card to use

Online or skirmish?

The game is single core, so it would be better if it was higher clock. I didn’t see the clock of that cpu, just something to keep in mind.

I would say the CPU matters more than the GPU... but we really do need updated recommended and min specs for the game. This game is more CPU intensive compared to other games. My i5 quad core 3.10Ghz runs it decently. 2GB r9 270 GPU

This is no official guide, just my thoughts on how to write a good suggestion. Keeping these in mind and roughly following the outline should lead to a readable, understandable and useful suggestion. This could be used for the RenX website, servers mutators or just the game in general. When developing anything, whether it be a game, application or website, there are always going to be suggestions -- feature requests, changes and replacement requests. These are welcomed and sought after by development teams. However, not all suggestions are the same. A good suggestion consists of three main things (usually). 1. The issue that needs to be solved When posting a suggestion, the issue that you want fixed should be straightforward and explicit. Everything else in your suggestion should be based around this. This is the main idea, or topic of the suggestion. Each addition, removal or change you suggest should have direct correlation to the issue. 2. How the issue negatively impacts the game Why do you think that the issue is detrimental to the game? How does the issue negatively impact game play or ruin matches. (E.G. anti tank unit beats anti-inf unit) Give a few points and in-game examples. In some situations, this should be accompanied by examples of how something is broken, video or screenshot. 3. Proposed solution Arguably the most important part of a suggestion, is the proposed solution -- how should we fix the problem? How does your suggestion directly fix the problem, and why would it be better than others? There are a wide variety of opinions on issues, and we'd love to hear them all. TL;DR: When suggesting something, make sure the issue is known, how the issue negatively impacts the game and how to fix it.

H20 is around in original Ren, never heard of KOSs, former WNx clan member here.

Additional 2 download locations added. France (FPI): http://repo.fairplayinc.uk/renx/maps/CnC-Hourglass_3.1.rar New York (Personal): http://taisho.xyz/Maps/CnC-Hourglass_3.1.rar

Depends on the ad. Little popups or side ads usually annoy me. But when its a trailer for a new movie or a game, it looks more interesting.

I’m the laziest fuck on planet earth

The one that took 5 seconds to fix after someone actually gave me a log? lol Yes it's fixed