Well this one apparently caused issues with Co-op.
Ok that can be done after they patch out the problematic code/scripting and reintroduce it so there is no conflicting issues under the hood.
Well this one apparently caused issues with Co-op.
Ok that can be done after they patch out the problematic code/scripting and reintroduce it so there is no conflicting issues under the hood.
then chance it and not remove it.
in Co-op there can chance the tank gun so that only 1 player can pick it up and if you play in a 4 player Co-op that the other 3 players cant pick up the tank gun.
thats better then remove it and destroy the gun compleet.
when we have Co-op things become crazy on a diffrend new high level for the campaign then we have see so far with it.
since from the PC platform players are using modâs more for the campaign to chance things here and there.
so i think the tank gun is still going to be staying in the campaign mode but then in a mod version.
Allegedly they did lol, which is why I said:
This âall or nothingâ mentality is indicative of someone who has never worked with code before. Even a rudimental understanding from a simplistic hands on tutorial experience with basic programming is enough to understand how bugs are difficult to incorporate and even identify in some cases.
The issue with mods is that mods can only exist mutually if another player is running the same version of the game as the host. (Gmodis a good example of how this works and doesnât work).
Modded lobbies usually depend heavily on the existing gameâs code to allow things to function within the gameâs coding/scripting parameters (CoD/Halo modded lobbies 360).
Iâm not saying it canât be done, but thereâs a likely probability that once this interaction is removed it would take a reworked version to enable again, which would mean that co-op players would have to be running that same version of the game.
Thereis no good reason to reduce the pistols damage even if there was future DLC
Celebration! Theyâre putting it back in! Now if only we could get the melee nerf reverted.
Iâm sorry but there was so much backlash to the tank gun being removed and 343 went ahead with it anyways only to now backtrack.
They continue to miss the mark and fall short. In a desperate attempt to win players back they decide to bring the tank gun back. The ship has sailed for me and I hope others move onto other games. Infinite is not worth your time or money.
its nice to know that the tank gun is staying or has return and i hope 343i has learn from it that this type buggs is not doing anything harm in the campaign mode at all.
and also that if something like that is happing again there fix it fast and not wait monthâs for it to do it since then you get some problems that people are not happy about it.
Or they removed it in its original glitch state (which given the limited info we had seemed to cause issues with co-op) and are adding it back in within a fixed intended state that doesnât cause issues.
A definitive positive for the player for sure, but pretty myopic celebrating it as a victory against 343i/adding the original âbuggedâ version back into the title.
TLDR: theyâre most likely not adding the original âtank glitchâ back in, theyâre adding a feature that allows you to use a tank cannon in a similar fashion to the âtank glitchâ but in a manner which is intended and doesnât cause issues.
old âtank glitchâ bug =/ new âtank glitchâ feature
Goes back to points I made in the past, if the glitch was such a burning issue it should have been addressed back in December. It wasnât and it was left out there for 6 months. It was removed and now is re added in some fashion.
Goes back to other points I have made, the decision making launch and post release of this game has been a mess. We as a community suffer because of the decisions made with Infinite, and the fact that the tank gun was even added back shows that 343 knew they made a mistake.
Or that the plan was to reintroduce it in some fashion that wasnât the result of conflicting code.
Itâs speculation at best what the motivation is, what possibly suggests that 343i realized the err of their ways in patching out a glitch and this is an atonement for ticking off the community?
This toxic confirmation bias narrative that pulls a âgotchaâ over some weird one-way rivalry going on between members of the community and 343i really needs to stop. The real way the community wouldâve suffered was when Co-op dropped and the âtank glitchâ wouldâve crashed the experience upon pickup leading to more backlash.
Whether the tank gun would or would not have caused issues in co op is irrelevant at this point. Weâre not getting co op anytime soon. At best maybe August and thatâs a big maybe.
If you want to talk about toxicity look no further than how this game has been launched and has been handled post release. People have a right to be angry and frustrated. It goes back to the decision making (or lack thereof) from 343. If I thought that things were going in the right direction I would give 343 credit where credit is due.
The tank gun being added back is a good thing but like I have stated I think itâs being done for the wrong reason. The point I have made is this should have been dealt with months ago, then it was removed and added back right away. You can formulate your own opinion but that tells me 343 made a knee jerk reaction and backtracked to correct it regardless of the reason.
How is it âirrelevantâ? Speculative at worst maybe based on the information source regarding its initial removal, but itâs incredibly relevant because it provides potential insight into why the glitch was removed in the first place.
Just because you and I canât see the process first hand or the repercussions doesnât make it âirrelevantâ, by definition it is entirely ârelevantâ. It doesnât fit your narrative and therefore you donât want to acknowledge it, itâs as simple as that.
Not in disagreement there. The bugs/glitches/issues, stagnant content flow, slow change rollout should be a reason that players expect more from a franchise that has treated them quite well in the past.
That doesnât mean that every little blip on the expectation radar needs to treated like DEFCON 1/Winter Contingency.
Thereâs not one thing that you can point to that 343i got right in Infinite?
The return to form art style, considerably scaled back from intrinsic-hyper-mobility of Halo 5, and the (reported) preemptive removal of gamebreaking glitches to then be reintegrated as non-gamebreaking features are pretty solid directions to take.
âYou thinkâ
This is based on what exactly? The fact itâs being added back in after backlash of its removal?
Ignoring the reported issues it caused leading to the news of the reintroduction suggesting that the reported issues may in fact have been rectified in some fashion that merits its reintroduction?
Should have? Or the way you wouldâve done it?
Again Iâm not in disagreement over the snailâs pace manner of rolling out needed changes for this title. But are you somehow saying the backlash wouldâve been mitigated in some fashion based on how the community reacts to even the smallest inconvenience?
Again based on the reports about the removal of the glitch so close to its implementation, it most likely has to do with Co-opâs introduction in season 2 whereas it wasnât on the radar during season 1.
This is speculation on my part (Iâll actually acknowledge it) but it might imply that internal builds of the game are tied heavily to the live version of the game.
BASED
ON
WHAT
I was kind of hoping it would be added back but has a skull and Iâll explain as a skull you could give it some unique features for example if you fire a plasma based weapon with that skull active the explosion upon impact would be plasma if you fired the shock pistol or shock rifle with that skull active it would have an EMP area of effect upon impact if you fired it the Needler with that skull active upon impact there be a pink explosion and it would scatter needles everywhere and then they would explode and then human weapons would just be standard however I did have an idea for the bulldog instead of it firing a tank round when that skull is active it would have a beefier sound and each pallet from its scattershot would have the concussive force and damage of a tank round
Luckily 343 has announced that they are adding it back in! Check out the last post of the upcoming update that is pinned in the forums! LETS GOOOOOO
the problems you get with Co-Op with can easy be fix for it like i have told you all what there can do by limit to 1 player to use or let it be use after you compleet the story line missions.
and like i told before on this thread all.
not all the glitchâs and bugs need to be fix always.
some off then make the game more fun if you have then without it.
like some gameâs have like i told before.
back in the xbox 360 dayâs the Cod MW2 got also some glitchâs that make it more fun in the multiplayer then without then.
and a lot off other gameâs that have glitchâs or bugs make it the game more fun to play.
there is a diffrend between glitchâs and bugs that make the game more fun to play.
and then you have glitchâs and bugs that make it less fun and destroy it more like spawn problems, or in halo infinite campaign more like that enemy AIâs get stuck in the sky barrier or ground barrier alive when your mission is to clean the place to compleet it with the cowbel skull and boom skull on that are things there need to fix and are less fun.
the tank gun is a glitch that makeâs it more fun and giveâs no problem at all.
Again this is stemming from the lack of knowledge about how bugs work. Itâs relatively difficult to construct a workaround on code that isnât being constrained by existing parameters.
Itâs like trying to build a fence around chickens that are already running around freely.
And like itâs been reported, this was not one of those glitches.
the point is more that 343i reason was with the tank gun fix is something to do against the speedrunners when we all know that the tank gun has notting to do with the speedruns at all.
if 343i really wane do something against the speedrunners there need to add more kill barrierâs in the missions spot so that you cant go outside off the mission map at all since thats the main thing there need to fix since it has notting to do at all with the tank gun.
and still to fix something like that after what was it now 3/4 monthâs after launch is to long and then you get more that people are against it.
if it was fix after 1 month of the launch from the game then it was no big deal at all but 3/4 monthâs is a diffrend story.
Where was the reasoning for this stated? Whatâs your base reasoning? Link me a url where this was the intended reasoning behind the âtank glitchâ being patched out.
I know that was the assumption I was going with, but there has been further reason to suggest that this wasnât actually the case.
Itâs presumptuous to assume this when we donât know if the âtank gunâ will restrict challenges/achievements.
Even more baselessly presumptuous when you take into account the report that suggests it was causing issues in co-op testsâŚ.
The last thing we need is more kill barriers if thereâs too many there be no point in having the grappling hook
i mean not to have kill barriers on a lot off placeâs but if you glitch out off the mission map like the House of Reckoning mission there glitcht more out off the map and skip the 2 wave roomâs and the Jega 'Rdomnai boss fight and do it so that there not have to fight against Escharum also.
if you look on youtube how the speedrunners are doing it then you see it that there glitching out off the map and walk more on the ceiling outside off the mission map.
if 343i wane make it harder for speedruners then is something like adding kill barriers outside the mission map like in the mission House of Reckoning that there cant skip it by glitching outside the map.