Digital Extremes has a habit of ignoring bug reports & burying them when a new major version of the game comes out, so I decided to start keeping an external list of known bugs rather than trying to rely on archives of reported bugs on their forums that never even get looked at (this will eventually be moved to the review of the game when I get it published to my personal site). This will give players the ability to keep track of those bugs when confirmed & if possible, avoid triggering them while playing Warframe.
Confirmed bugs since last patch:
- Duplicates of event Decorations can be wiped when a new year's event starts if not placed.
- One decoration I noticed on this bug was I had 4 Dog Days War Displays (buying the 4th one on accident), I'm certain I had other duplicates also. When the 2026 Dog Days event started, all duplicates I had of these items were wiped with the exception of the Noggle Statue - Yareli And Merulina.
- Using the Randomize All button to edit the appearance of your Archwing or any of it's equipment forces a Warframe view & breaks the intended viewing of equipment.
- The correct viewing can be reset by navigating off of the vehicle tab, then going back to it.
- The Arquebex is incorrectly shown as protruding through the abdomen of the Voidrig when being viewed on the Arsonel screen.
- Decals set through use of the Randomize All button do not remain on the Railjack beyond leaving a relay.
- AoE damage from the Arquebex has not registering on Eidolons since the release of Siris & Orion.
- Rare Cache containers can generate in areas that are not accessible by players (making the rewards unacquirable, even if shot at a distance; trying to land next to the cache resets your position as if you had fallen in a pit) in Corpus Ice Mines in Railjack missions.
- Enemy Crewships can spawn on top of your Railjack (clipping through the interior floor, ceiling & walls), making them impossible to destroy & getting in your way when you try to move around your Railjack (literally capable of getting you stuck in a small corner of your Railjack, unable to move more than a couple feet from where it surrounds you).
- In a mission on 8/30/2026 at about 2:55 AM Mountain Time, I had another player join me & we both had to abandon the mission because the last crewship that needed to be destroyed was the one that was stuck on the Railjack. This should be considered a HIGH PRIORITY fix, as it is game breaking & capable of full mission failure when it happens.
- When running a Railjack Extermination mission, if a player enters a derelict/ice mine before the objective is completed, enemies still in the derelict/ice mine that were not killed may still count towards the killed enemy objective. This can prevent the mission from being completed.
- Something I did attempt to test was to exit the objective area to go back to the derelict/ice mine to kill of the enemies left in that area to see if it would complete the objective task. You can not exit through the standard exit until the killed enemies task is completed, so I was attempting to go back to the entry area to see if I could leave & get to the derelict/ice mine area.
- The other players in the 8/30/2026 run considered the run a bust & forced a return to their Dojo, which resulted in a loss of the mission. Because of this, I was not able to test my theory that the mission could still be completed if I exited out the start point & killed off the remaining enemies in the derelict/ice mine area...
Section last updated 8/30/2026
Previously confirmed since the last major version, not confirmed since the last patch:
- Attempting to pick up carriable items while in void mode as Operator/Drifter is delayed.
- When starting a new mission, you will sometimes get an error stating that you were imporperly disconnected & ask you to rejoin.
- Void Storm Railjack missions sometimes only award 1 Corrupted Holokey (rather than what they are supposed to award).
- Ghoul defectors can keep moving away from you while you are attempting to defuse the collar.
- A player leaving a free roam team when a vote is in progress causes the vote to get bugged & a new bounty can't be started.
- Conductive Blade costs 2 more mod points to slot than any other elemental damage mod with the same damage increase.
- Decorations do not sort correctly when in Decorate mode when attempting to sort by Owned.
- Waypoint makers can get pinned on the UI even after they have expired (they won't move from that spot).
- Void Flood Omnia Fissure missions can bug & not progress to the next round or allow gaining of rewards when rounds are completed.
- Mining hotpoints are not always at an angle that can be visible.
- Matchmaking can stall on the "Please Wait..." screen & require a forced kill of the game; progression not possible.
- Using an Ability melee weapon while having a Glaive equiped can disable your normal weapons when disabling the Ability weapon.
- Re-activating the ability weapon on & off can fix this, but workaround is limited by available energy
- Changing Audioscape to None in Dormizone casues Unknown Error; Killing Game process required afterwards.
Note that these bugs are usually wiped after every new major version of the game, however I do keep a local backup of those bugs so I can go back & confirm whether they are still present in the game. After minor updates, known bugs may get bumped down to the lower section until they are confirmed again or removed if they a confirmed to be fixed.
Other recommended changes that never got a response:
- Ignore list should be a 2-sided block that prevents being teamed up with those users.
- The Ignore list as it is now is a 1-sided ignore that only prevents you from seeing messages made by the person that was added to your ignore list.
- It's an Ignore list, not a Block list, so those users can still get into teams you are in & cause problems during a mission, where you will be specifically targeted if they know you added them to your ignore list (I know this one from experience).
- A 2-sided Ignore would make it so 1 person placing the block would make it so neither user can see comments from the other & ultimately nullify out in-game chat from both users between the 2 of them. The 2-sided Ignore function would save the trouble of having somebody trying to response to somebody's comments that can't see what they are saying because them have them ignored anyway.
- With the current system, what happens is a user will see a user they are attempting to respond to isn't responded to them & they will retaliate by placing them on Ignore so they won't be tempted to respond to them (believing they can't see their responses), even if an initial ignore wasn't even placed (the 2-sided Ignore would just nullify the suspicion of whether they were being ignored on the technical level or the user is just choosing not to respond to them).
- This actually happens fairly regularly in the clans I have been in (both current & in the past). I don't utilize the Ignore function in this case, but I will set a filter so that I will only see comments if they state my name so I can focus on the game & stop getting side-tracked by discussions that it seems clear they would rather ignore my presence in it (or have a technical Ignore in place through the game, which illustrates the problem with 1-sideded ignores).
- The other downside to the Ignore list is it's minimal for the level of toxicity I've run into in Warframe. You only get 100 slots to add users to & anybody who has their account linked between different systems also utilizes additional slots for the same person. I can't even say how many times I've cycled through my ignore list because I run into idlers, AFKers, leechers, griefer, teabaggers & so on fairly regularly (not so much making it public through recorded videos and/or reporting them anymore, but more just adding them to my Ignore list without saying anything & leaving the mission or team).
