Xbox One bug? -Nope (Destiny)

by INSANEdrive, ಥ_ಥ | f(ಠ‿↼)z | ᕕ( ᐛ )ᕗ| ¯\_(ツ)_/¯, Wednesday, September 10, 2014, 13:03 (3524 days ago) @ Avateur

To clarify, Unreal told me he hit 790 on 360 and it unlocked. Maybe he hit 777 first and got a second one that bumped him over it? Either way, I'm glad Levi said that they have ways of fixing this if it is a bug.

I got this last night. Can confirm.

locked

2061 views

Complete thread:

RSS Feed of thread

Busted Achievement? - Avateur, 2014-09-10, 12:04
- Busted Achievement? - uberfoop, 2014-09-10, 12:07
  - Busted Achievement? - Avateur, 2014-09-10, 12:09
    - Busted Achievement? - uberfoop, 2014-09-10, 12:12
    - Busted Achievement? - Cody Miller, 2014-09-10, 12:15
      - Busted Achievement? - Avateur, 2014-09-10, 12:20
        
        Busted Achievement? - Leviathan, 2014-09-10, 12:22
        
        Unlocked it on 360. Not sure how you're having issues. - UnrealCh13f, 2014-09-10, 12:48
        
        Xbox One bug? - Avateur, 2014-09-10, 12:51
        
        Xbox One bug? -Nope - INSANEdrive, 2014-09-10, 13:03
        
        Xbox One bug? - TTL Demag0gue, 2014-09-10, 13:12
        
        Xbox One bug? - Avateur, 2014-09-10, 13:46
        
        Xbox One bug? - Xenos, 2014-09-10, 13:48
        
        Xbox One bug? - Avateur, 2014-09-10, 14:01
        
        Xbox One bug? - Schedonnardus, 2014-09-10, 13:49
- Un-Busted Achievement - Avateur, 2014-09-10, 15:53
  - Yay! - Leviathan, 2014-09-10, 18:17

DBO Forums

Xbox One bug? -Nope (Destiny)