Update : Since this morning I get a slightly better response on Parrying but now I cannot complete a five hit combo on attack. In 2nd or 3rd hit my champ starts to do heavy attack !!!! Obviously that's even worst ! Herc - MoJo - CGR had huge issues with 5 hit combos - Human torch was a little bit better but still was throwing heavies for no reason. Samsung Galaxy 21+ Ultra .
I still don't understand what kabam is trying to do to fix the problem. I have no idea about programming, what is a hotfix? Why can't they just go back to previous version?
That's what should be done. Parry, dex, block is all old code that has been in the game for a long time and should not be touched. If it isn't broken don't touch it.
I still don't understand what kabam is trying to do to fix the problem. I have no idea about programming, what is a hotfix? Why can't they just go back to previous version?
A hotfix is a patch to update the game. Not all aspects but just some. You can't roll back a game like this since each new update has new content. There are always changes to the game itself that aren't just new content so it's really not possible for that to happen.
Actually you can if you code with tabs and you can go into it to make any changes. You take the section that has parry, dex, block, AI speeds, etc from a previous code and then you keep that and replace the old code of event quest or side quest with the new code for this month's quest and boom game fixed. Happy players.
Come on finish up your YouTube video on coding or your article on Google and enlighten us. You say that isn't how it works and you say you love to "discuss" so let's hear it expert.
I'm just enjoying you melting down. I'm not a programmer and neither are you. I can confidently say, this game cannot do roll backs.
Also, I don't use the reaction buttons. I wouldn't click disagree and not say anything. I'd rather respond than use a button.
We figured out what the problem is. Every action is a bit delayed. If you parry a bit earlier than usual, it fits. Same goes for dex block and everything else.
I still don't understand what kabam is trying to do to fix the problem. I have no idea about programming, what is a hotfix? Why can't they just go back to previous version?
A hotfix is a patch to update the game. Not all aspects but just some. You can't roll back a game like this since each new update has new content. There are always changes to the game itself that aren't just new content so it's really not possible for that to happen.
Actually you can if you code with tabs and you can go into it to make any changes. You take the section that has parry, dex, block, AI speeds, etc from a previous code and then you keep that and replace the old code of event quest or side quest with the new code for this month's quest and boom game fixed. Happy players.
Come on finish up your YouTube video on coding or your article on Google and enlighten us. You say that isn't how it works and you say you love to "discuss" so let's hear it expert.
I'm just enjoying you melting down. I'm not a programmer and neither are you. I can confidently say, this game cannot do roll backs.
Also, I don't use the reaction buttons. I wouldn't click disagree and not say anything. I'd rather respond than use a button.
I still don't understand what kabam is trying to do to fix the problem. I have no idea about programming, what is a hotfix? Why can't they just go back to previous version?
A hotfix is a patch to update the game. Not all aspects but just some. You can't roll back a game like this since each new update has new content. There are always changes to the game itself that aren't just new content so it's really not possible for that to happen.
Actually you can if you code with tabs and you can go into it to make any changes. You take the section that has parry, dex, block, AI speeds, etc from a previous code and then you keep that and replace the old code of event quest or side quest with the new code for this month's quest and boom game fixed. Happy players.
Come on finish up your YouTube video on coding or your article on Google and enlighten us. You say that isn't how it works and you say you love to "discuss" so let's hear it expert.
I'm just enjoying you melting down. I'm not a programmer and neither are you. I can confidently say, this game cannot do roll backs.
Also, I don't use the reaction buttons. I wouldn't click disagree and not say anything. I'd rather respond than use a button.
Oh actually I am a programmer but I've never messed with my own game engine because that's dumb and cost a lot to maintain. Can't roll back? Really that's why a lot of players went online to find the January APK file just to make the game playable again and still have access to EVERYTHING except the new EQ and side quest.
Installing a previous APK is not the same as rolling back as what you are trying to infer. lol but keep going, this is gold. Kabam would have to remove 33.0 and force everyone to reinstall 33.2.3. Everyone would lose any progress they made in MEQ, SQ and any crystals they opened. Everyone would lose the new content. You can't rollback the game to the previous version without severely interrupting everyone especially those who aren't experiencing these issues. Imagine pulling herc from a 6* today and Kabam takes it away.
I still don't understand what kabam is trying to do to fix the problem. I have no idea about programming, what is a hotfix? Why can't they just go back to previous version?
A hotfix is a patch to update the game. Not all aspects but just some. You can't roll back a game like this since each new update has new content. There are always changes to the game itself that aren't just new content so it's really not possible for that to happen.
Actually you can if you code with tabs and you can go into it to make any changes. You take the section that has parry, dex, block, AI speeds, etc from a previous code and then you keep that and replace the old code of event quest or side quest with the new code for this month's quest and boom game fixed. Happy players.
Come on finish up your YouTube video on coding or your article on Google and enlighten us. You say that isn't how it works and you say you love to "discuss" so let's hear it expert.
I'm just enjoying you melting down. I'm not a programmer and neither are you. I can confidently say, this game cannot do roll backs.
Also, I don't use the reaction buttons. I wouldn't click disagree and not say anything. I'd rather respond than use a button.
I still don't understand what kabam is trying to do to fix the problem. I have no idea about programming, what is a hotfix? Why can't they just go back to previous version?
A hotfix is a patch to update the game. Not all aspects but just some. You can't roll back a game like this since each new update has new content. There are always changes to the game itself that aren't just new content so it's really not possible for that to happen.
Actually you can if you code with tabs and you can go into it to make any changes. You take the section that has parry, dex, block, AI speeds, etc from a previous code and then you keep that and replace the old code of event quest or side quest with the new code for this month's quest and boom game fixed. Happy players.
Come on finish up your YouTube video on coding or your article on Google and enlighten us. You say that isn't how it works and you say you love to "discuss" so let's hear it expert.
I'm just enjoying you melting down. I'm not a programmer and neither are you. I can confidently say, this game cannot do roll backs.
Also, I don't use the reaction buttons. I wouldn't click disagree and not say anything. I'd rather respond than use a button.
Oh actually I am a programmer but I've never messed with my own game engine because that's dumb and cost a lot to maintain. Can't roll back? Really that's why a lot of players went online to find the January APK file just to make the game playable again and still have access to EVERYTHING except the new EQ and side quest.
Elaborate on "your own game engine". What kinds of games does it run? Did you design it from the ground up? Let us bask in your glory of your programming greatness.
Installing a previous APK is not the same as rolling back as what you are trying to infer. lol but keep going, this is gold. Kabam would have to remove 33.0 and force everyone to reinstall 33.2.3. Everyone would lose any progress they made in MEQ, SQ and any crystals they opened. Everyone would lose the new content. You can't rollback the game to the previous version without severely interrupting everyone especially those who aren't experiencing these issues. Imagine pulling herc from a 6* today and Kabam takes it away.
You are mistaken. If you have 2 devices, roll back or don't update one. Start the new EQ on updated device. Log off and log on with the old version. Voila, you can finish that map just fine. But its a pain since you have to do it each time. So there is nothing about the EQ that requires the patch. It's just a check the program runs before showing you the map on the menu.
I still don't understand what kabam is trying to do to fix the problem. I have no idea about programming, what is a hotfix? Why can't they just go back to previous version?
A hotfix is a patch to update the game. Not all aspects but just some. You can't roll back a game like this since each new update has new content. There are always changes to the game itself that aren't just new content so it's really not possible for that to happen.
Actually you can if you code with tabs and you can go into it to make any changes. You take the section that has parry, dex, block, AI speeds, etc from a previous code and then you keep that and replace the old code of event quest or side quest with the new code for this month's quest and boom game fixed. Happy players.
Come on finish up your YouTube video on coding or your article on Google and enlighten us. You say that isn't how it works and you say you love to "discuss" so let's hear it expert.
I'm just enjoying you melting down. I'm not a programmer and neither are you. I can confidently say, this game cannot do roll backs.
Also, I don't use the reaction buttons. I wouldn't click disagree and not say anything. I'd rather respond than use a button.
I still don't understand what kabam is trying to do to fix the problem. I have no idea about programming, what is a hotfix? Why can't they just go back to previous version?
A hotfix is a patch to update the game. Not all aspects but just some. You can't roll back a game like this since each new update has new content. There are always changes to the game itself that aren't just new content so it's really not possible for that to happen.
Actually you can if you code with tabs and you can go into it to make any changes. You take the section that has parry, dex, block, AI speeds, etc from a previous code and then you keep that and replace the old code of event quest or side quest with the new code for this month's quest and boom game fixed. Happy players.
Come on finish up your YouTube video on coding or your article on Google and enlighten us. You say that isn't how it works and you say you love to "discuss" so let's hear it expert.
I'm just enjoying you melting down. I'm not a programmer and neither are you. I can confidently say, this game cannot do roll backs.
Also, I don't use the reaction buttons. I wouldn't click disagree and not say anything. I'd rather respond than use a button.
Oh actually I am a programmer but I've never messed with my own game engine because that's dumb and cost a lot to maintain. Can't roll back? Really that's why a lot of players went online to find the January APK file just to make the game playable again and still have access to EVERYTHING except the new EQ and side quest.
Installing a previous APK is not the same as rolling back. lol but keep going, this is gold.
That's literally what a roll back is. If players have a new update and then install a previous update. That's rolling back to the previous update. You tell everyone they don't know this, or they don't know that, but you literally said in your previous post you don't know anything about it where you said you're not a programmer. So do us all a favor quit talking things you have 0 knowledge about. Your mom's calling you from your basement. Your hot pocket is ready. Go eat.
You are literally ignoring the logistics of what an enforced 'rollback' would do on a global user scale after even 30 minutes of content use with the new update. I believe, that, in essence, is what Demon was referring to. No Hotfix or compensation could unilaterally blanket that kind of a move.
I still don't understand what kabam is trying to do to fix the problem. I have no idea about programming, what is a hotfix? Why can't they just go back to previous version?
A hotfix is a patch to update the game. Not all aspects but just some. You can't roll back a game like this since each new update has new content. There are always changes to the game itself that aren't just new content so it's really not possible for that to happen.
Actually you can if you code with tabs and you can go into it to make any changes. You take the section that has parry, dex, block, AI speeds, etc from a previous code and then you keep that and replace the old code of event quest or side quest with the new code for this month's quest and boom game fixed. Happy players.
That's impossible for three separate reasons any game developer who develops on modern engines would know and could confirm here (if any game developer was brave enough to try).
1. Things like well-timed blocks (the mechanical basis behind the parry mechanic) are not expressed directly in code, at least not in the context being discussed here. There's no "well timed block" code that defines parry timing. Blocks are determined by event timing, and well-timed blocks by very small windows of timing built into the attack animations and collision boxes. A well-timed block is in effect an emergent behavior from the interactions between the character animations and the player inputs. Well-timed blocks are defined to occur when certain circumstances are met in the game, but the specific *timing* of when they happen or when they are allowed to happen is due to how the game data interacts with the way the Unity engine processes and manages time. In other words, if well-timed blocks exist anywhere, they exist in the code of Unity (which the developers can't really mess around with) and in the *data* of the game. Not in the code of the game directly.
2. Most of the player-facing functionality in a game like MCOC is built on abstraction layers. The game itself is built upon Unity, a single game engine that is supplied by a vendor (helpfully enough, called Unity). Constructed upon Unity is a game mechanical layer of Unity extensions that modify the game engine in ways that allow Kabam to customize and extend the behavior of Unity to basically make MCOC - this is how everyone does it. Unity is and is not modular; you cannot just rip it apart and keep some parts and modify other parts in isolation. Firstly the vendor won't let you. And even if they would, Unity is a tightly coupled constellation of code blocks that don't work in isolation. This isn't like a menu-driven ATM where each button causes the machine to do a completely different thing. It is more like an operating system where you can upgrade from Windows 10 to Windows 11, but you can't update your Windows 10 network subsystem to the Windows 11 one. The vendor won't let you, and even if they would it wouldn't likely work correctly. So basically, there's no way to silo MCOC "vertically" into functional towers, because it is actually built horizontally, in layers of lasagna noodles.
You could even go so far as to say that the way players normally think about the game in terms of different "parts" or "sections" is almost completely illusory, because while it might look that way to humans, to the extent that the game is modular at all it is modular in a completely different way that you need to be a developer to notice or understand. Parry is a thing to a player. It is a lot of different tiny things scattered throughout the entire system to the game engine that just coincidentally look like a Parry to the player. It is a prediction of a collision of certain kind of state circumstance after an input within a calculated window defined by a movement and animation sequence which generates an activation trigger within the ability initiation resolution system.
3. Most importantly, games like MCOC are generally developed with just-in-time delivery processes. The engine is constantly being modified. The content is constantly being modified. The content being written today must target the engine that is going to be released in four months, because it needs game engine features that are being added today to support the needs of the content being written today. If they did a tick tock development (where the game engine was modified but the content ignored those changes, then after release the content used new engine features but the engine was frozen), they might never be able to ship new content fast enough to support a games as a service game like MCOC. So when the new game comes out, it is running content that needs it. If you revert the game engine due to a bug, which I've already mentioned must happen all or nothing, you'll break a lot of the new content the game just released. This is impractical for a game that relies upon constantly releasing new content. A game as a service that is buggy is crippled. A game as a service that cannot release content consistently is dead.
How do I know any of this? One: I've been involved off and on with game design and development in some capacity for some time, which includes both studying the field as well as having the rubber meet the road by doing professional contract work for a shipping MMO in the past. Two: I've talked to multiple developers in multiple studios working on multiple games, including during the ramp up phase before shipping and during the support phase after release (which are completely different kinds of game development). Three: I talk to the developers of this game, so I know the things I'm aware of that are common in the games industry in general for the most part apply here as well. So none of these things are guesses. I do not, however, have a Youtube channel on coding. That would probably require me to read Youtube comment sections. Pass.
Oh actually I am a programmer but I've never messed with my own game engine because that's dumb and cost a lot to maintain. Can't roll back? Really that's why a lot of players went online to find the January APK file just to make the game playable again and still have access to EVERYTHING except the new EQ and side quest.
You can in theory roll the entire game client back completely (you cannot do intracode rollbacks as previously discussed). However, the app stores don't give well supported ways to make multiple versions of the same game client available (as far as I'm aware, someone post a link to the reversion recommendations from the vendors for each platform if I'm out of date there), which means if they attempt to do a complete rollback for Android on the Google Play store they will likely need to still get the old version reapproved which takes time (my understanding is it has to do with the mandatory requirements of version tracking) and then everyone who allows normal automatic updates would then get auto reverted and lose access to the new content, even if they were not experiencing any issues. Given the Android issues are not universal, that would be a very drastic step to take.
Also, there's a significant risk here because while it might seem like the only thing lost is access to the new content, that's not always the case. For example, there are times where if you're running the older version past a certain date the game servers block you from even logging in. This is probably a safety lock to prevent bad side effects or corruptions from happening due to the client mismatch.
Friendly suggestion to everyone. Maybe hold off on Legendary SQ until the Hotfix comes out. I just tried it, and Heavies aren't coming that easily without consistent Parry.
Friendly suggestion to everyone. Maybe hold off on Legendary SQ until the Hotfix comes out. I just tried it, and Heavies aren't coming that easily without consistent Parry.
content aside, the big problem here is AQ. We have AQ running with crappy bugged inputs. Nightmarish.
Comments
Also, I don't use the reaction buttons. I wouldn't click disagree and not say anything. I'd rather respond than use a button.
Every action is a bit delayed.
If you parry a bit earlier than usual, it fits. Same goes for dex block and everything else.
1. Things like well-timed blocks (the mechanical basis behind the parry mechanic) are not expressed directly in code, at least not in the context being discussed here. There's no "well timed block" code that defines parry timing. Blocks are determined by event timing, and well-timed blocks by very small windows of timing built into the attack animations and collision boxes. A well-timed block is in effect an emergent behavior from the interactions between the character animations and the player inputs. Well-timed blocks are defined to occur when certain circumstances are met in the game, but the specific *timing* of when they happen or when they are allowed to happen is due to how the game data interacts with the way the Unity engine processes and manages time. In other words, if well-timed blocks exist anywhere, they exist in the code of Unity (which the developers can't really mess around with) and in the *data* of the game. Not in the code of the game directly.
2. Most of the player-facing functionality in a game like MCOC is built on abstraction layers. The game itself is built upon Unity, a single game engine that is supplied by a vendor (helpfully enough, called Unity). Constructed upon Unity is a game mechanical layer of Unity extensions that modify the game engine in ways that allow Kabam to customize and extend the behavior of Unity to basically make MCOC - this is how everyone does it. Unity is and is not modular; you cannot just rip it apart and keep some parts and modify other parts in isolation. Firstly the vendor won't let you. And even if they would, Unity is a tightly coupled constellation of code blocks that don't work in isolation. This isn't like a menu-driven ATM where each button causes the machine to do a completely different thing. It is more like an operating system where you can upgrade from Windows 10 to Windows 11, but you can't update your Windows 10 network subsystem to the Windows 11 one. The vendor won't let you, and even if they would it wouldn't likely work correctly. So basically, there's no way to silo MCOC "vertically" into functional towers, because it is actually built horizontally, in layers of lasagna noodles.
You could even go so far as to say that the way players normally think about the game in terms of different "parts" or "sections" is almost completely illusory, because while it might look that way to humans, to the extent that the game is modular at all it is modular in a completely different way that you need to be a developer to notice or understand. Parry is a thing to a player. It is a lot of different tiny things scattered throughout the entire system to the game engine that just coincidentally look like a Parry to the player. It is a prediction of a collision of certain kind of state circumstance after an input within a calculated window defined by a movement and animation sequence which generates an activation trigger within the ability initiation resolution system.
3. Most importantly, games like MCOC are generally developed with just-in-time delivery processes. The engine is constantly being modified. The content is constantly being modified. The content being written today must target the engine that is going to be released in four months, because it needs game engine features that are being added today to support the needs of the content being written today. If they did a tick tock development (where the game engine was modified but the content ignored those changes, then after release the content used new engine features but the engine was frozen), they might never be able to ship new content fast enough to support a games as a service game like MCOC. So when the new game comes out, it is running content that needs it. If you revert the game engine due to a bug, which I've already mentioned must happen all or nothing, you'll break a lot of the new content the game just released. This is impractical for a game that relies upon constantly releasing new content. A game as a service that is buggy is crippled. A game as a service that cannot release content consistently is dead.
How do I know any of this? One: I've been involved off and on with game design and development in some capacity for some time, which includes both studying the field as well as having the rubber meet the road by doing professional contract work for a shipping MMO in the past. Two: I've talked to multiple developers in multiple studios working on multiple games, including during the ramp up phase before shipping and during the support phase after release (which are completely different kinds of game development). Three: I talk to the developers of this game, so I know the things I'm aware of that are common in the games industry in general for the most part apply here as well. So none of these things are guesses. I do not, however, have a Youtube channel on coding. That would probably require me to read Youtube comment sections. Pass.
Also, there's a significant risk here because while it might seem like the only thing lost is access to the new content, that's not always the case. For example, there are times where if you're running the older version past a certain date the game servers block you from even logging in. This is probably a safety lock to prevent bad side effects or corruptions from happening due to the client mismatch.