Developed by Everreach Labs, web3 extraction shooter REVENGE is set to launch on Immutable in Q1 2025.
The game blends cooperative PvE gameplay with blockchain technology, providing players with ownership of in-game assets. One of its key features is the integration of spectator-player interaction, allowing live viewers to influence gameplay to create a more dynamic and engaging experience for both players and audiences.
As part of the game’s early development, a pre-alpha playtest is now available for registration, allowing participants access to an early look at the game before its full release.
Source: Revenge
What is Revenge?
REVENGE is a web3 extraction shooter set in a sci-fi world controlled by the MARA virus, which turns creatures into zombie-like enemies.
The game focuses on cooperative PvE gameplay, where players must team up to battle these infected creatures and extract valuable artifacts. However, these artifacts can only be kept if players manage to survive and successfully extract.
In addition to the standard gameplay, REVENGE features blockchain integration, allowing players to own in-game assets securely. The game also includes an innovative spectator interaction system that enables Twitch viewers to influence matches in real-time.
Source: Revenge
How to participate in the pre-alpha?
To participate in REVENGE’s pre-alpha, players must register on the official website.
The registration process requires an email address and the connection of an EVM-compatible wallet. After registering, players may receive a Soulbound Token (SBT), which provides access to the pre-alpha and offers various rewards, including in-game bonuses and the potential to participate in future playtests.
The pre-alpha is expected to begin in February 2025 and selected participants will have the opportunity to experience the game’s features and give feedback ahead of the full release.
For interested players, the game is also available for wishlisting on Steam and the Epic Games Store.
This marker is Chrome Shitiness Mitigation mechanism for Ultrawidify. It turns out that as of 2025-01, Chrome does not correctly respect allowTransparency property on certain iframes, and will force white or black background across the entire element. It is unclear what’s causing the issue — so far, it seems to appear randomly.
This marker is Chrome Shitiness Mitigation mechanism for Ultrawidify. It turns out that as of 2025-01, Chrome does not correctly respect allowTransparency property on certain iframes, and will force white or black background across the entire element. It is unclear what’s causing the issue — so far, it seems to appear randomly.
This marker is Chrome Shitiness Mitigation mechanism for Ultrawidify. It turns out that as of 2025-01, Chrome does not correctly respect allowTransparency property on certain iframes, and will force white or black background across the entire element. It is unclear what’s causing the issue — so far, it seems to appear randomly.
This marker is Chrome Shitiness Mitigation mechanism for Ultrawidify. It turns out that as of 2025-01, Chrome does not correctly respect allowTransparency property on certain iframes, and will force white or black background across the entire element. It is unclear what’s causing the issue — so far, it seems to appear randomly.
This marker is Chrome Shitiness Mitigation mechanism for Ultrawidify. It turns out that as of 2025-01, Chrome does not correctly respect allowTransparency property on certain iframes, and will force white or black background across the entire element. It is unclear what’s causing the issue — so far, it seems to appear randomly.
This marker is Chrome Shitiness Mitigation mechanism for Ultrawidify. It turns out that as of 2025-01, Chrome does not correctly respect allowTransparency property on certain iframes, and will force white or black background across the entire element. It is unclear what’s causing the issue — so far, it seems to appear randomly.
This marker is Chrome Shitiness Mitigation mechanism for Ultrawidify. It turns out that as of 2025-01, Chrome does not correctly respect allowTransparency property on certain iframes, and will force white or black background across the entire element. It is unclear what’s causing the issue — so far, it seems to appear randomly.
This marker is Chrome Shitiness Mitigation mechanism for Ultrawidify. It turns out that as of 2025-01, Chrome does not correctly respect allowTransparency property on certain iframes, and will force white or black background across the entire element. It is unclear what’s causing the issue — so far, it seems to appear randomly.
