It makes a lot of difference to some people if you know what that means. Huge problem in the US.
L O LBungie may be trolling with Xur now:
http://www.reddit.com/r/DestinyTheGame/comments/2yu2cm/misc_bungies_xur_changesno_land_beyond_troll/
I tried to data-mine today and bungie has implemented a lot of changes. Instead of Xur having one single constant IP on one port, he now has multiple. If you join a tower instance and you're the only one there, Xur will have 16 different IP address. If you join and its 8 other people, Xur will have 9 different ones. Only one of the possible IP's you connect to will share the packet information you need. The others will include self-input data like controller movement, date & time, and other player constants.
To combat this I used zone alarm on each IP separately until I isolated the one that sends the packets for weapons. This took considerably longer than I thought because each unique IP only sends packets for a 45 second window and then they stop for 100ms, and then restart. This made it hard to decipher the hex code and decide if there were any patterns.
Finally, once I managed to isolate the IP, find the pattern, and looped it. Every 22 packets started with the same 8b Hex. Bungie had literally broadcasted every thing as a No Land Beyond. This is what I found(obviously a troll), but yeah:
No Land Beyond 999 Attack Kinectic Damage
No Land Beyond 488 Defense Warlock Chest Piece
No Land Beyond 366 Defense Hunter Gauntlets
No Land Beyond 447 Defense Titan Helmet
TLR
Bungie has employed 8 servers from their network, and 8 from Activision. They've employed a fail safe on 15/16. They constantly shuffle ports and IP's that lead to nothing. The one IP that does lead to anything has the name No Land Beyond for every weapon, armor, and upgrade.
That's fine with me.Two questions:
1) What time would you assholes like to hit up VoG? I'm thinking in about 1.5 hours.
2) I'm bringing my NLB for practice.
Note: second item was not actually a question.
Ya huhHalf 10 is fine with me. Also shove your NLB.
uh huh
I would like to thank the guy who figured out how the first guy was able to take a peek at Cur's future wares. Thanks a bunch, Sir No Fun Allowed! If you hadn't posted how he did it, Bungie would have taken a couple more weeks to patch it!Bungie may be trolling with Xur now:
http://www.reddit.com/r/DestinyTheGame/comments/2yu2cm/misc_bungies_xur_changesno_land_beyond_troll/
I tried to data-mine today and bungie has implemented a lot of changes. Instead of Xur having one single constant IP on one port, he now has multiple. If you join a tower instance and you're the only one there, Xur will have 16 different IP address. If you join and its 8 other people, Xur will have 9 different ones. Only one of the possible IP's you connect to will share the packet information you need. The others will include self-input data like controller movement, date & time, and other player constants.
To combat this I used zone alarm on each IP separately until I isolated the one that sends the packets for weapons. This took considerably longer than I thought because each unique IP only sends packets for a 45 second window and then they stop for 100ms, and then restart. This made it hard to decipher the hex code and decide if there were any patterns.
Finally, once I managed to isolate the IP, find the pattern, and looped it. Every 22 packets started with the same 8b Hex. Bungie had literally broadcasted every thing as a No Land Beyond. This is what I found(obviously a troll), but yeah:
No Land Beyond 999 Attack Kinectic Damage
No Land Beyond 488 Defense Warlock Chest Piece
No Land Beyond 366 Defense Hunter Gauntlets
No Land Beyond 447 Defense Titan Helmet
TLR
Bungie has employed 8 servers from their network, and 8 from Activision. They've employed a fail safe on 15/16. They constantly shuffle ports and IP's that lead to nothing. The one IP that does lead to anything has the name No Land Beyond for every weapon, armor, and upgrade.
Bungie may be trolling with Xur now:
http://www.reddit.com/r/DestinyTheGame/comments/2yu2cm/misc_bungies_xur_changesno_land_beyond_troll/
I tried to data-mine today and bungie has implemented a lot of changes. Instead of Xur having one single constant IP on one port, he now has multiple. If you join a tower instance and you're the only one there, Xur will have 16 different IP address. If you join and its 8 other people, Xur will have 9 different ones. Only one of the possible IP's you connect to will share the packet information you need. The others will include self-input data like controller movement, date & time, and other player constants.
To combat this I used zone alarm on each IP separately until I isolated the one that sends the packets for weapons. This took considerably longer than I thought because each unique IP only sends packets for a 45 second window and then they stop for 100ms, and then restart. This made it hard to decipher the hex code and decide if there were any patterns.
Finally, once I managed to isolate the IP, find the pattern, and looped it. Every 22 packets started with the same 8b Hex. Bungie had literally broadcasted every thing as a No Land Beyond. This is what I found(obviously a troll), but yeah:
No Land Beyond 999 Attack Kinectic Damage
No Land Beyond 488 Defense Warlock Chest Piece
No Land Beyond 366 Defense Hunter Gauntlets
No Land Beyond 447 Defense Titan Helmet
TLR
Bungie has employed 8 servers from their network, and 8 from Activision. They've employed a fail safe on 15/16. They constantly shuffle ports and IP's that lead to nothing. The one IP that does lead to anything has the name No Land Beyond for every weapon, armor, and upgrade.
No Land Beyond 999 Attack Kinectic Damage
No Land Beyond 488 Defense Warlock Chest Piece
No Land Beyond 366 Defense Hunter Gauntlets
No Land Beyond 447 Defense Titan Helmet
Bungie may be trolling with Xur now:
http://www.reddit.com/r/DestinyTheGame/comments/2yu2cm/misc_bungies_xur_changesno_land_beyond_troll/
I tried to data-mine today and bungie has implemented a lot of changes. Instead of Xur having one single constant IP on one port, he now has multiple. If you join a tower instance and you're the only one there, Xur will have 16 different IP address. If you join and its 8 other people, Xur will have 9 different ones. Only one of the possible IP's you connect to will share the packet information you need. The others will include self-input data like controller movement, date & time, and other player constants.
To combat this I used zone alarm on each IP separately until I isolated the one that sends the packets for weapons. This took considerably longer than I thought because each unique IP only sends packets for a 45 second window and then they stop for 100ms, and then restart. This made it hard to decipher the hex code and decide if there were any patterns.
Finally, once I managed to isolate the IP, find the pattern, and looped it. Every 22 packets started with the same 8b Hex. Bungie had literally broadcasted every thing as a No Land Beyond. This is what I found(obviously a troll), but yeah:
No Land Beyond 999 Attack Kinectic Damage
No Land Beyond 488 Defense Warlock Chest Piece
No Land Beyond 366 Defense Hunter Gauntlets
No Land Beyond 447 Defense Titan Helmet
TLR
Bungie has employed 8 servers from their network, and 8 from Activision. They've employed a fail safe on 15/16. They constantly shuffle ports and IP's that lead to nothing. The one IP that does lead to anything has the name No Land Beyond for every weapon, armor, and upgrade.
Hawkmoon! Nice Ocho!
Bungie may be trolling with Xur now:
http://www.reddit.com/r/DestinyTheGame/comments/2yu2cm/misc_bungies_xur_changesno_land_beyond_troll/
I tried to data-mine today and bungie has implemented a lot of changes. Instead of Xur having one single constant IP on one port, he now has multiple. If you join a tower instance and you're the only one there, Xur will have 16 different IP address. If you join and its 8 other people, Xur will have 9 different ones. Only one of the possible IP's you connect to will share the packet information you need. The others will include self-input data like controller movement, date & time, and other player constants.
To combat this I used zone alarm on each IP separately until I isolated the one that sends the packets for weapons. This took considerably longer than I thought because each unique IP only sends packets for a 45 second window and then they stop for 100ms, and then restart. This made it hard to decipher the hex code and decide if there were any patterns.
Finally, once I managed to isolate the IP, find the pattern, and looped it. Every 22 packets started with the same 8b Hex. Bungie had literally broadcasted every thing as a No Land Beyond. This is what I found(obviously a troll), but yeah:
No Land Beyond 999 Attack Kinectic Damage
No Land Beyond 488 Defense Warlock Chest Piece
No Land Beyond 366 Defense Hunter Gauntlets
No Land Beyond 447 Defense Titan Helmet
TLR
Bungie has employed 8 servers from their network, and 8 from Activision. They've employed a fail safe on 15/16. They constantly shuffle ports and IP's that lead to nothing. The one IP that does lead to anything has the name No Land Beyond for every weapon, armor, and upgrade.
No everyone thinks that the prediction on Reddit was changed and Bungie's patch 1.1.1.1 was a stealth fix to prevent megamanexe and the other player from being able to predict Xur. And I hope that is correct personally.
I would like to thank the guy who figured out how the first guy was able to take a peek at Cur's future wares. Thanks a bunch, Sir No Fun Allowed! If you hadn't posted how he did it, Bungie would have taken a couple more weeks to patch it!
well played Bungie, well played
*slow clap*
Hawkmoon! Nice Ocho!
I disagree It got me even more excited for Xur if it was items I wanted to get. Otherwise I am just ready for Xur to let me down every week.Destroying the surprise of Xur is actually really bad for the whole set up of Destiny.
Bungie may be trolling with Xur now:
http://www.reddit.com/r/DestinyTheGame/comments/2yu2cm/misc_bungies_xur_changesno_land_beyond_troll/
I tried to data-mine today and bungie has implemented a lot of changes. Instead of Xur having one single constant IP on one port, he now has multiple. If you join a tower instance and you're the only one there, Xur will have 16 different IP address. If you join and its 8 other people, Xur will have 9 different ones. Only one of the possible IP's you connect to will share the packet information you need. The others will include self-input data like controller movement, date & time, and other player constants.
To combat this I used zone alarm on each IP separately until I isolated the one that sends the packets for weapons. This took considerably longer than I thought because each unique IP only sends packets for a 45 second window and then they stop for 100ms, and then restart. This made it hard to decipher the hex code and decide if there were any patterns.
Finally, once I managed to isolate the IP, find the pattern, and looped it. Every 22 packets started with the same 8b Hex. Bungie had literally broadcasted every thing as a No Land Beyond. This is what I found(obviously a troll), but yeah:
No Land Beyond 999 Attack Kinectic Damage
No Land Beyond 488 Defense Warlock Chest Piece
No Land Beyond 366 Defense Hunter Gauntlets
No Land Beyond 447 Defense Titan Helmet
TLR
Bungie has employed 8 servers from their network, and 8 from Activision. They've employed a fail safe on 15/16. They constantly shuffle ports and IP's that lead to nothing. The one IP that does lead to anything has the name No Land Beyond for every weapon, armor, and upgrade.
Destiny won Best game on the BAFTA awards !
Oh crap! Time to head over to the thread and read the responses.Destiny won Best game on the BAFTA awards !
Destiny won Best game on the BAFTA awards !
I'm just going to leave this here:
Nah Bungie would have patched it in the same time. I would like to thank that guy too. I'm really glad this got patched.
Destroying the surprise of Xur is actually really bad for the whole set up of Destiny.
Huh?
Oh crap! Time to head over to the thread and read the responses.
Although I do think it doesn't deserve it.
Destiny won Best game on the BAFTA awards !
Destroying the surprise of Xur is actually really bad for the whole set up of Destiny.
Please tell me you're joking
Pretty funny fix.Nah Bungie would have patched it in the same time. I would like to thank that guy too. I'm really glad this got patched.
That is utterly hilarious. Bravo, Bungie.
Good call, Deku.
Bungie sure are quick to patch out some harmless thing while VoG and CE are still a broken mess. Though they did say they are working on fixing VoG...SIX MONTHS LATER!!!
got nechrocasm, so excited to use it
Um, I think the link is broken.Pretty funny fix.
Another stealth patch conspiracy theory.
The patch addressed deeper exploits tied to the animation glitch.
popcorn check
soda check
go to gaming side
double check
The surprise has already been ruined to a degree. We know he'll never sell Gjallarhorn now.
Seems it did win. Dunno how I feel about that. On the one hand, I think the game is bloody brilliant and very fun, and does co-op PvE as good as anything I've played. On the other it also has some massive flaws and is still very much a (slowly improving) work in progress. I haven't played the competition but it sure does seem like an outlier of a pick.
Bungie may be trolling with Xur now:
http://www.reddit.com/r/DestinyTheGame/comments/2yu2cm/misc_bungies_xur_changesno_land_beyond_troll/
I tried to data-mine today and bungie has implemented a lot of changes. Instead of Xur having one single constant IP on one port, he now has multiple. If you join a tower instance and you're the only one there, Xur will have 16 different IP address. If you join and its 8 other people, Xur will have 9 different ones. Only one of the possible IP's you connect to will share the packet information you need. The others will include self-input data like controller movement, date & time, and other player constants.
To combat this I used zone alarm on each IP separately until I isolated the one that sends the packets for weapons. This took considerably longer than I thought because each unique IP only sends packets for a 45 second window and then they stop for 100ms, and then restart. This made it hard to decipher the hex code and decide if there were any patterns.
Finally, once I managed to isolate the IP, find the pattern, and looped it. Every 22 packets started with the same 8b Hex. Bungie had literally broadcasted every thing as a No Land Beyond. This is what I found(obviously a troll), but yeah:
No Land Beyond 999 Attack Kinectic Damage
No Land Beyond 488 Defense Warlock Chest Piece
No Land Beyond 366 Defense Hunter Gauntlets
No Land Beyond 447 Defense Titan Helmet
TLR
Bungie has employed 8 servers from their network, and 8 from Activision. They've employed a fail safe on 15/16. They constantly shuffle ports and IP's that lead to nothing. The one IP that does lead to anything has the name No Land Beyond for every weapon, armor, and upgrade.
Is anyone else looking to get the raid with a clan trophy? I can't seem to convince any of my friends to join a clan just for a raid
Knowing Xur in advance really isn't harmless though from Bungie's game design perspective. They want you to be checking on Destiny on Friday or Saturday to see if Xur has anything you need. The predictions prevent that and are a much bigger problem for the game as a whole than raid bugs... although I also would prefer if they first fixed the raid bugs.
Xur seems pretty irrelevant at this point after finding out he won't carry gally because bungie intentionally altered his wares.
Yeah, I like Destiny, I've poured dozens of hours of my time into it, but goddamn, it should not be getting anywhere near any GOTY awards. There were just quite a few games out last year where were just flat out better.