We are planning to activate Reverse Friendly Fire on the Test Server. This is the latest feature we are working on in our efforts to address toxicity.

The goal of this system is to contain the impact of players abusing the friendly fire mechanic, while maintaining a degree of flexibility for accidents. We will collect data and feedback from both ranked and casual playlists on the Test Server, and iterate before releasing it live.


With Reverse Friendly Fire, when a player shoots an ally or the hostage, a warning message will appear on the offending player’s screen. The same will occur if a player uses their unique operator gadget to hurt a teammate (i.e. Maestro's Evil Eye or Twitch's drone).


After a player’s first validated team kill, all further damage inflicted upon teammates or the hostage is reflected back to the player. When a player uses a unique operator gadget to deal this damage, reflected damage will impact the gadget itself.

A message will pop up for the offending player to notify them when Reverse Friendly Fire has been activated. All players in the match will be notified of this change to the offending player's status through the kill feed.



During the kill cam, a team kill victim is able to validate whether they were intentionally team killed. If the player confirms that the kill was intentional, Reverse Friendly Fire will stay active for the offender. If the player believes it was unintentional, Reverse Friendly Fire will be deactivated.

Should the victim not make a decision, Reverse Friendly Fire is activated by default.



After an intentional team kill is validated, Reverse Friendly Fire will stay active for the match instead of kicking that player. We will continue to track team kills, and we may issue appropriate sanctions after multiple offenses.

We will continue to address toxicity as we proceed into Year 4 and beyond. We look forward to hearing your feedback and findings on the Reverse Friendly Fire system through the forums and on the official subreddit!

Rainbow Six Siege is currently on sale for £9.34/10.99/$10.99 on Ubisoft’s own store.

Source :


Battlefield 5

In continuation of the support plan for Battlefield 5, EA has officially unveiled the next Royal Battleship under the name Firestorm, with a date later this month.
The gamingbolt report confirmed the availability of the addition on March 25, 2019 for the PlayStation 4, Xbox One and PC. EA reviewed the advantages of the Batel Royale in a new film show that demonstrates the importance of team play and collaboration with the rest of the team and takes a look at the driving vehicles.
The DICE studio plans to support this style with more additions and modifications in the future to compete with the most popular online games on the scene, although Firestorm provides a much different experience .

Battlefield 5

EA beat the Beatles Royal with Apex Legends, which had a spectacular success and surpassed 50 million players one month after the launch, and is still in the battle of the American publisher for the upcoming Battle Royal game, namely Firestorm developed for the game Battlefield 5, which has been leaked recently Whether on the level of information or propaganda.
The players' effort to search for hidden information in the game data resulted in the release of new details posted through Reddit, which showed that the Patel Royal will not only play with teams of 4 people but will also offer individual and team matches, as well as 4 levels of equipment, All over the map can grab their contents.
The Firestorm development provides one map to be set in Norway, as well as players can find backpacks to carry more tools, plus the presence of various vehicles such as helicopters, sports cars, vans, and tractors.

The video conduit confirmed the same details above, in addition to a separate Rank system for the Patel Royale and the ability to call reinforcements such as getting a truck or using heavy artillery strikes.

A function of Intel's processors dealing with speculative execution has another vulnerability that affects all Intel-based computers including Apple's Mac, researchers have revealed, with "Spoiler" potentially allowing an attacker the ability to view the layout of memory, and in turn potentially access sensitive data stored in those locations. 

The speculative execution function of Intel's processors, used to increase the performance of a CPU by predicting paths an instruction will go through before the branch is completed, is a useful function but one that has caused Intel issues in the past. A new report from security researchers from Worcester Polytechnic Institute and the University of Lubeck published on March 1 indicates there's another issue that needs to be fixed. 

Dubbed "Spoiler," the technique is able to determine how virtual and physical memory is related to each other, by measuring the timing of speculative load and store operations performed by the processor, reports The Register. By spotting discrepancies in the timing, it is possible for an attacker to determine the memory layout, and in turn know areas to attack. 

"The root cause of the issue is that the memory operations execute speculatively and the processor resolves the dependency when the full physical address bits are available," researcher Daniel Moghimi advised to the report. "Physical address bits are security sensitive information and if they are available to user space, it elevates the user to perform other micro architectural attacks." 

Speculative execution typically works by using a memory order buffer to track its operations, by copying data from a CPU register to main memory in the order it appears in code. Data can then be copied from the main memory to a register out of order, which potentially speeds up the overall speed of the operation if the speculative elements are right. 

If they are wrong, the speculative elements are discarded and a normal non-speculative load of data is performed, allowing the instruction to be carried out, but without the performance boost. 

The paper advises the main issue with Spoiler is Intel's performance of memory disambiguation, which tries to prevent computation on data loaded by an incorrect speculation attempt, with its timing behavior being the actual vulnerability. 

By filling the store buffer with addresses using similar offsets but different virtual pages, then issuing a memory load with the same offset on a different memory page, the team measures the time of the load. After performing multiple loads across numerous virtual pages, the timing differences provide clues about the memory locations. 

It is believed by the researchers the technique could make existing cache and "Rowhammer" attacks easier to perform, while at the same time enabling attacks using JavaScript to take seconds to complete, rather than weeks. 

"There is no software mitigation that can completely erase this problem," according to the researchers. While the chip architecture could be fixed, it would considerably cut into the chip's performance. 

Intel was advised about the vulnerability on December 1, 2018, and was disclosed to the public after a typical 90-day grace period. So far, Intel has not issued a CVE number for the problem, with Moghimi speculating the issue is not easily patchable with microcode in an efficient enough manner, and that a patch for the attack vector may take years to produce. 

As it is an issue that affects all Intel Core processors from the first generation onwards to the most recent releases, regardless of operating system, it is almost certain that all Macs are susceptible to attacks that take advantage of the vulnerability. It is unclear if Apple has specifically responded to the issue due to it potentially affecting its macOS-running products. 

The researchers note that ARM and AMD processor cores do not exhibit the same behavior, which means iPhones and iPads are safe from such attacks. 

The speculative execution function was core to the Spectre vulnerabilities found in January 2018, which affected Intel processors as well as ARM-based versions, including both macOS and iOS devices, something which Apple quickly released mitigations to defend against. While similar in this regard, Spoiler functions quite differently from Spectre, and is a completely separate vulnerability. 

"We expect that software can be protected against such issues by employing side channel safe development practices," said Intel regarding Rowhammer-style attacks. "Protecting our customers and their data continues to be a critical priority for us and we appreciate the efforts of the security community for their ongoing research."


Rainbow Six Siege

About two weeks after the release of Burnt Horizon's Rainbow Six Siege content, Ubisoft shared the official release date for the first additional content dedicated to the fourth year, which provides two new customers and a first Australian map.
The comicbook report reviewed the observations and changes that the game has undergone in the past few days based on the opinions of players who have had the opportunity to experience expansion through test servers. The Ambulance System has been modified and minor changes have been made to some characters such as Capitao and Dokkaebi. While jogging.
The Burnt Horizon process is officially released on March 6 for PS4, Xbox One and PC devices .