Fffreak9999

You can ask all the questions you want, we won't guarantee to answer them In our testing phase, we had Nod with artillery. As above, we had the A.APC and S.APC as well Nod had units with different powers, Jump Jets were limited to GDI units. FYI: All the above is based on the Alpha footage you saw, and is subject to change at any point and without warning.

Can you please provide the log file from your system, You can find it in your Renegade X install location, under UDKGame

Currently testing is limited to Developers and Closed Beta Testers.

64 bit server works fine, but we can’t guarantee bug free.

No problem

Certain vote types are already limited on either a team limit or player limit per vote. Surrendering is limited to a team wide limit of 1 per 5/10 mins. I can't recall the exact value. This is not currently possible Your vehicle enters the queue on purchase, it is something that didn't exist in the original Renegade (except as part of a server modification). While this is something that COULD be done, there are times where this could be abused. The only thing I can recommend at this time, is just to be careful. While we would like to do so, it is not easy to have filters in place, and they are not effective in other games either, as you would need to add a million different variants of insults. We would rather deal with individuals rather than limit conversation entirely, and potentially affect legitimate chat. Try typing !rules in chat, many servers run a Jupiter bot, which has a small list of rules which are visible once the command is typed.

Again, please raise this on Discord, it makes it easier to track where the connection issue lies.

If you have any connection issues, please put a post in #support on discord. We are more rapidly able to support you from there.

We will be pushing for AFK kicking to resume automatically soon, we have only been lenient on it so far due to the issues we have been having with our DDoS protection. Expect to see aggressive AFK kicking in place within the next week on the official servers.

@Handepsilon - Something for you to look into?

Map change is meant to be instant and available at any time, and award the teams no victory. Surrender is meant for what you want. (As to the comment from Mystic saying: I would personally prefer that surrender auto-destructs the teams own base instead of making the other team all become heroic.) This used to be the functionality of Surrender, but we implimented the change as it felt like you were cheating the enemy team out of a victory by ending it early, even if the credit was still awarded. We can easily adjust this on a per server basis as well, since Server Owners can adjust the Surrender duration, and can choose to drop it to 0, automatically ending the round with the enemy victory. We are not likely to change the functionality of change map votes. Consider this: PUG Match: We use Change Map to end the existing map (due to Warm up or some other reason) So lets take into account the criteria you specified below: 1. 2 or More Structures Lost - Not likely to occur in a warmup, but could occur due to a slow lockbuildings command. 2. 15 Minutes or more - The warmup map often is on-going for more than an hour. So based on your criteria, We would be unable to use change map voting to switch to the next round without going through surrender, un-necessarily extending gameplay (or forcing an admin to use a command). Also Change map is a [Global] vote which means that the vote is effective for both teams to vote for, or against, unlike the surrender vote which is [Team]. If your team all votes "No", then the vote stands no chance to pass, as the required votes would be far greater than the enemy team has players able to vote. Also lets take into account the following: The vast majority of "Change Map" votes do not succeed.

By default, the required values for players needed to activate beacon purchasing is 1. This means that the first player to join unlocks beacons straight away.

Just to confirm this: Vet does improve the repair tool power. Recruit - 1.0x Veteran - 1.11111x (17) Elite - 1.22222x (19) Heroic - 1.33333x (21)

Good Evening, DDoS is the primary reason for the laggy state of play.

We are aware, keep using the launcher in the mean while. We are working on a solution.

Also @Everyone - Merged this post as this appears to be related to the same bug.

I can confirm the same behaviour exists for me as well, I have posted the log in our Discord.

All over the world.

In most cases, the providers do provide DDoS protection without extra cost. As to the servers being provided right now, the protection isn't amazing, but they do have some protection. We are doing the best we can to mitigate what we can, but there is multiple steps to prevention, and we cannot block every attack either.

Yes, It is a combined total of NetWait and DonationsDisabledTime

What you see is not a “default” commander. It is a commander voted in on previous rounds, keeping their role between rounds. You are able to override this behaviour by voting in another person, or evicting them from the role.

The clock does not take into account the wait time. (30 seconds for CT) (60 seconds for the PUG) 20 by default on other servers. So if you get to 3 minutes, you need to wait for the wait time to expire as well. Example: Default setting + 180 seconds means 200 seconds before you can donate

I will put the suggestion forward, we see this in IRC, so it should be easy to put it into a visible location in the chat box.

They are playing a private match, its no different than us putting a password on the server such as the PUG.

To play Nod vs Nod, you need to download the files you need. You can either download them from here: This will give you the bare minimum files Or you can download them from these 2 mirrors, which have the advantage of having shaders pre-compiled which will allow the maps to load faster. Primary Mirror: Click here to download Secondary Mirror: Click Here to Download