May - last edited May by EA_Barry
Product: Apex Legends
Please specify your platform model. PC
AMD or Nvidia Model Number 1080ti
Enter RAM memory size in GB 16
What is your gamertag/PSN ID/EA Account name? Quazm0
Please provide your squad mates' gamertag/PSN ID/EA Account name if possible.
Which Legend were you playing (if applicable)?
Which Legends were your squad mates using (if applicable)?
Where did the issue occur? In a match
Which part of the map or menu were you in? If you don't remember the exact name, please describe the area or what you were trying to do in the menu. everywhere
What were you doing when the issue occurred? E.g. respawning a squad mate at a beacon, using an ability, a squad mate left the game. reloading autoexec.cfg ingame with [Removed - Admin.] command
Did your squad mates also experience the issue? Yes
How many matches had you played in a row before the issue occurred? -
When did this happen? (dd.mm.yy hh:mm) -
How often does the bug occur? Every time (100%)
How severe is your issue? Major impacts to gameplay
What happens when the bug occurs? -
What should be happening instead? -
Steps: How can we find the bug ourselves? [Removed - Admin.]
[Removed - Admin.]
The fact that this exploit still hasn't been fixed makes me doubt the capabilities of Respawn's programmers. It's game breaking and its continued existence is absurd! If your programmers can't replace the few lines of code that reference particle_remove_all within an hour, then you need better programmers. It is absolutely mind blowing this exploit is still possible when the fix would be so relatively easy. Is it so hard for you to search that string in your code-base and modify it? Is your code so poor that variable references get obfuscated to the point you can't find them?
I'm having a really hard time thinking of any scenario where this fix would take more than 15 minutes, and you've had MONTHS to fix it. Hell, give me the affected source files and I'll do it for you!
Trying to be a fan of your game is so &$**#$ infuriating!!
Your post was edited to remove the details of this exploit.
We ask for your understanding as to why this was done.
Easier to remove a post than to make a simple fix to the game. Classic.
I can't believe adding this config option to the list of already filtered out config options, like dev_console, novid, etc is so apparently bottom of the list for you, that it's been in game for months. You say you're all about fighting cheaters, yet leave an engine level exploit sitting right there to use freely. It's extremely disheartening and makes no sense at all.