{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
8/24/2022 4:57:53 PM
1
Making a case that it wasn’t intentional is defending him. Are you really that dense? It’s not a bug, it is bad programming that trolls can take advantage of. A bug is something unintentional. This is just not preventing a possibly malicious act due to not programming in protections against it.
English
-
Do you think it’s intended that if a player gets kicked while holding the ball that it would vanish with no way to get it back isn’t a bug? Many you really need to maybe like clear your head or something because that’s the wildest claim you’ve made yet. Like you’re even more making me confident that the dude didn’t leave on purpose with now compromised your logic is.
-
It would be a bug if they had that mechanic in place and it didn’t work. Not having that in place at all is not a bug. It’s simply poor planning for not having it in place. Maybe you should stop and think about what is considered a bug vs poor programming and planning for scenarios like that.
-
The orb being able to vanish at all is the bug. It isn’t intended for you to need a replacement because it’s not supposed to be able to vanish. So it’s a bug that it doesn’t drop if the person with the orb DCs. Are you trying to make the absolutely brain dead claim that the orb is supposed to be able to vanish and not drop if the person holding it DCs?
-
They never intended for the orb to drop if someone goes to orbit or DC’s with it, so no, it’s not a bug. That’s the issue, Bungie didn’t have the forethought to program that in. It’s a bad feature resulting from lack of planning and programming.
-
The orb drops if you get killed, so clearly it is intended to drop. Meaning that if someone DCs while carrying the orb they were intended to drop it. This isn’t really any different then the IB bug where people holding the spark wouldn’t drop it if killed to close to the rift. If it’s intended to drop when you die it’s intended to drop if your guardian in any way should be dropping it.
-
No, those are two different mechanics. Dying you are still in the activity. Leaving, well, you’re not. We have years of examples where Bungie didn’t plan that out, so again, it’s not a bug. It’s a missing feature. It *should* drop if you DC or anything else similar, but it doesn’t, so they never intended for it to do so. If they did, then it would be a bug. You really are trying hard to show how little you understand about these things. It’s purely poor planning on Bungies part.
-
They aren’t different features. If you go from being in a place holding an object and then either go to a different state or location it’s unintended for you to not drop what you were carrying. Spark or orb. It is a bug for an item like an orb to not drop if a player carrying it changes from a status where they are meant to be carrying it. Like the idea that any key item is planned to be able to vanish is just ridiculous. If you’re holding the orb and die you drop it. It’s no different to if you DC. You’ve gone from a state where you were holding the orb to a status where it should have been dropped because you are no longer there. That’s a bug.
-
It isn’t a different mechanic though when it comes to objects. If you change from the holding state to any other the objective is meant to drop. That’s true from death or DCing. The only difference is what happens to your player model. And even if you are thinking even slightly a bug is when something unintended happens in a game. So a key item being able to vanish is a bug.
-
No, it’s not. The mechanic is if then. If you die, then the orb drops. If you DC, it does not. It’s not based on whether you’re able to hold a relic. It’s coded differently based on the state of your character, not just to simply drop the orb. So again, poor planning and not a bug.
-
You do understand that you are supposed to drop it. The coding error is the bug. Why under any logic would they not want a player to drop a key item if the DC? You do get that bugs are an error and code, don’t you? That a bug fix is fixing the code. It’s meant to identify a DC the same as a death in relation to orbs. So if a person DCs and it doesn’t drop then there’s an error in the code. Aka a bug.
-
It’s not that they *want* it to work the way it does. They didn’t intentionally code it to work the way it does. It’s that they *didn’t* plan for DC’s, so it’s on them to actually code the behavior *we* expect as reasonable. Do you really not comprehend that?
-
Do you not comprehend that if code isn’t working the intended way it’s because of a bug. The orb isn’t intended to be able to vanish so if some conditions can cause it to vanish that is a bug because it’s not intended.
-
Do you not comprehend that if they didn’t specifically code it to drop the orb when someone DC’s, it’s not a bug? It’s simply lack of planning for that scenario, which they have not planned for many times before. We have evidence of this, so it is not a bug. Is that really too difficult for you to understand? They only coded it to drop the orb when you die. There is nothing coded to drop the orb when you DC. That’s exactly the problem. They are two different scenarios. One planned for. One not planned for. You can’t call it a bug if the game is working exactly how they coded it.
-
How it is so hard for you to understand that if the code says it should be dropped by a player and DCing is being read as a different redaction and the orb is being deleted then that’s a bug. It’s only not a bug if it the code gives perimeters for the orb to be deleted and not drop, which its not supposed to. So it’s a bug. The orb being able to be deleted is a bug. The fact that DCs cause it is the source of the bug.
-
Code does what the writer tells it to do. They DID NOT plan for DC’s, so no code was written to drop the orb when DC’d. That is 1000% not a bug and just poor planning. Do you not understand that the code won’t default to different behavior if you don’t tell it to? It does what the writer tells it to. If it doesn’t, then it’s a bug. Not doing something from a completely different set of parameters is not a bug. It’s a really basic concept that you seem too dense to comprehend. Two different scenarios completely in terms of coding, which simply comes down to one was planned for and coded correctly, and one was not. That it. Nothing else. I’m really done now, because you appear to be too stupid to comprehend this very basic concept of coding.
-
That’s incorrect. If the code is reading a DC incorrectly, as it is in this case, then that’s a bug. The DC isn’t being read as it should causing the game to not know what to do with the orb and deleting it. But the code has no line telling the game to delete the orb, only to drop it. So if they line of code isn’t being properly triggered to drop the orb then it’s a bug. It’s a Dc being misread by the code and not reacting as intended. Any time a code acts in a way not intended that is a bug.
-
It’s not that they *want* it to work the way it does. They didn’t intentionally code it to work the way it does. It’s that they *didn’t* plan for DC’s, so it’s on them to actually code the behavior *we* expect as reasonable. Do you really not comprehend that?
