K4on Retired PR Developer



Join Date: May 2009 Posts: 4,998 Germany Germany Blog Entries: 9

Insurgency 2.0 Alpha Test Event - 07./08.02.2015 @16PRT



Over the past weeks the Project Reality team has been working together with UTurista in order to improve the current PR Insurgency game mode, based on several community ideas and feedback.



For the upcoming weekend, we would like to run an Insurgency 2.0 Alpha Test Event, to check one of two new concepts. The 2nd concept will be tested on a later date.



Insurgency 2.0 Alpha Test Event

Saturday, Feb. 7th, 2015 at 16:00 PRT

Sunday, Feb. 8th, 2015 at 16:00 PRT

(PRT = Project Reality Time)



on

Official PR Insurgency 2.0 Alpha Test - Event Server

(sponsored by New Era Warfare)





Testing Conditions:

We'll be testing the new (work in progress) Insurgency 2.0 settings for PR 1.3.

The changes are purely server side, so you don't have to take care of anything apart from joining the server.

We would like to mention again, that the concepts are not guaranteed to be in the next patch. That's depending on the feedback we get. At a later point when one of the concepts has been chosen, we will be extending the tests to other PR community servers in order to get more feedback. More info to come. Over the past weeks the Project Reality team has been working together with UTurista in order to improve the current PR Insurgency game mode, based on several community ideas and feedback.For the upcoming weekend, we would like to run an Insurgency 2.0 Alpha Test Event, to check one of two new concepts. The 2nd concept will be tested on a later date.(PRT = Project Reality Time)on(sponsored byWe'll be testing the new (work in progress) Insurgency 2.0 settings for PR 1.3.The changes are purely server side, so you don't have to take care of anything apart from joining the server.We would like to mention again, that the concepts are not guaranteed to be in the next patch. That's depending on the feedback we get. At a later point when one of the concepts has been chosen, we will be extending the tests to other PR community servers in order to get more feedback. More info to come.



INSURGENCY 2.0 ALPHA CHANGELOG:



UAV - Unmanned Aerial Vehicle Updated the UAV uptime to be limited again.

The UAV loses 0.2% fuel/sec while travelling, 0.1% fuel/sec while loitering (operating) and refuels at 0.2% fuel/sec.

UAV can be send back to base at any point to start refueling (deploy UAV within 1 big grid of command post). Returning to base does not consume any fuel.

UAV deploy time depends on distance to travel. The UAV travels at 50 m/s.

The UAV takes 45 seconds to land/start.

Hideouts Updated Hideout minimum build distance to other hideouts to be 150m instead of 200m.

Caches Updated Caches to only have one available at a time.

Updated Caches to be revealed, 5 minutes after the last one got removed.

Updated Caches to get relocated after 40 minutes if they haven't been destroyed (Insurgents will win the map if the cache has been moved two times successfully).

Updated Insurgents to see on-map markers of previous cache locations.

Added new function that allows to decide on the area of the next cache, it will be set by the server in case the commander doesn't set the next cache area in time.

Civilians Reduced Civilian help radius to 3m horizontal and 1.5m vertical meters.

Reduced Civilian ROE time from 2 to 1 minute.

Vehicles Updated CAS and Tanks to re-spawn after 20 minutes instead of 15.

Updated APCs and IFVs to re-spawn after 15 minutes instead of 10.

Intel System The BLUFOR cache marker can be inaccurate if BLUFOR doesn't gather any Intel points.

Insurgents will see the real cache location as well as the inaccurate marker.

The Intel system now correlates with the maximum distance that the cache-marker for BLUFOR can be from the actual cache position.

Heavy assets and long distance kills no longer generate intelligence points.

What do these changes mean in terms of gameplay? It allows more opportunities and gameplay variety for Insurgents. Although the first cache will be random, allowing the commander to set the next cache position will add a new dimension of gameplay: Insurgents need to consider possible locations for the next cache while BLUFOR need to prevent them from placing the cache by controlling these possible locations.

Intel-system: The cache marker, which is visible for BLUFOR, will appear after 5 minutes have passed - this marker is not guaranteed to be accurate though. With a maximum spread of half the map size (e.g.: 500m on 1km maps), BLUFOR will need to obtain Intel points to reduce this distance and get an accurate cache position.

Deploying the cache In this Alpha test the cache is deployed in the same way you build a hideout - as a commander, you select your phone, press T and select 'build hideout' (temporary) - this will check all possible cache locations in your area and the cache will be selected randomly.

Don't forget that you should do this while the current cache is still in-play, otherwise the game will select one for you when the cache is destroyed.



Make sure to to post your feedback here:

https://www.realitymod.com/forum/f25...est-event.html





Thanks for your consideration,



- The Project Reality Team Thanks for your consideration,