It's funny, bc Sunday is one of those allies that might get targeted more and end up getting that low amount of shield. (It's usually beneficial to put him in the middle slots so you get more energy) I've seen so many people joke about how Sunday is "the new Tingyun" taunt-wise, and most of them also had Aventurine on the team in their screenshots.
I was so confused to why some of my characters' shields were depleting so fast even though Aventurine was just spamming his FUA. Thanks for the insight
That was my first thought too when hearing about the bug, Aven's ability parsing each ally's shield value but instead of returning the actual lowest value it's returning 'undefined' or '0' associated with a memosprite that doesn't exist
But what about fallen characters? If it returns the lowest, then it should've been bugged since release since fallen allies will also return 0 while not being able to gain the extra shield. Isn't it more likely that the 'each valid ally' check was wrong and the code that check for array of fortified wager holders couldn't determine correctly whether a memo-sprite is 'active' or 'fallen', perhaps due to a incorrectly inherited memo-sprite interface that defaults true for isActive checks? This is more likely as not only aventurine is bugged but also a wide array of other characters, plus the long time it is taking the devs to fix it (bug in memo-sprite interface -> have to retest every single memo-sprite interaction)
@@harryhsu7980 I’d imagine that “dead” characters return a different variable entirely so they can be written out of the equation when considering who to give the shield to. But if the default variable for the memosprite is not the same as a “dead character” then thats where the “undefined” or “0” portion comes in. After all, just because a character is at “0”, doesn’t mean they are permanently dead which allows for other passives to take effect once they hit 0(see also: Bailu’s revive and Arlan’s E6). But because memosprites cant be “permanently dead”(as MC snd Agalaea can both resummon them) some programmer decided to leave it at “0” or “undefined”which means Aventurine’s shield keeps giving the un-summoned Memosprite a shield when it doesn’t exist.
@@loststorm-platinium we don't know the inner working of their code, but game development is insanely complex because there are so many moving parts, especially when characters are interacting with each other in way that will directly change their states and values. the solution could just be a simple as setting the isAlive state of the invisible teammates to false, but they couldn't really risk making that hotfix. The apple app store and PlayStation store are REALY strict with their policies it takes at least a week for them to verify and push your update, and IF the hotfix ends up introducing a new bug (likely to Sunday) they'd have to waste another 2-3 weeks sending a hotfix, they'd never risk breaking Sunday because this is HIS patch so if he's broken people will be mad, it's a lot saver to just fix it next patch.
In the newest HSR youtube video they kinda hint towards this being the case, as they say that implementing the new path gave them a lot of issues since it changed so many characters interactions.
And they said, the implementation of this new battle line up took more work, than anticipated (by complaining about working overtime so much, they forgot when is day and when is night). I feel sorry for them for that and also grateful. But also... this bug is too big for not getting fixed through an entire patch (but I think, they figured, in next patch it won't be an issue anymore, so...better to just pay compensation).
@@ashy969 people often say stuff like HYV devs have no excuses bc of the money its games rake in, but behind every successful game are overworked programmers. game devs fr some masochists, it's a career you have to have some mad passion for.
@@nilmerg Agreed, and not just programmers. My sister was an animator for games and TV cartoons, and she does unpaid overtime almost everyday. She has to ask to go home earlier (usually allowed, but sucks that you have to inform your superior just to go home on time) She says 3D modelers and riggers always do unpaid OTs too. In the company she worked in, at least.
@@DilysCheong1998 its very common.. in asian countries for these things but for the US and europe that is all illegal outside very specific circumstances
Luocha and galla are my 2 main sustainers, i didn't get lingsha cuz i deleted hsr for zzz and only came back for sunday, i failed to get every other sustain after luocha's release even including the standard characters I've been using luocha exclusively as my solo sustain in SU game modes trying to catch up to the higher levels i wasn't present for and just other general stuff, I've never noticed anything wrong with luocha's emergency heal can you please elaborate
I used him last week for some side content where you can use trial Luocha and Blade. To me it seemed like it worked as intended & I didn't even need to use his healing skills
My first thought is that Each character has a memosprite slot and since memosprites are also counted as allied aventurine also gives shields to them. However, since there's bound to be empty ally slots aventurine gives a sheild to them that just resets to 0 or undefined since there's nothing in that slot, which means that those slots will always have the lowest shield value. Basically an endless cycle of giving shields to the empty slots>shields resetting to 0>passive occurs in the empty slot since it has the lowest shield value>Being reset to 0 again. This is just how I thought of it.
And non-memosprite allies likely have non-0 values already set for them when the slots are empty or the characters are dead to prevent the bug from when aven first released. edit: as in, the non-memosprite slots.
@@EvaHoshizora those summons aren't coded as actual allies tho, more like detached follow up attacks. memosprites are actually j additional characters.
@@EvaHoshizora the summons we have in the game right now aren’t really real summons. They are considered more closely related to a follow up . When we talk about summon, we’re talking about an additional character that is targetable in someway.
FR. as a day 1 Geppie main turned aven main... even the slightest of damage is enough to cause me panic hahaha I AM SO NOT USED TO TAKING DAMAGE like even just a hundred or so damage makes me feel like I've been hit big time by the enemies and yeah this bug really is bugging me coz I can't even play in auto in peace. Especially when i play conundrum 6 and above which i can comfortably play on auto before, now I have to really time when to use Aven's skill
It is actually not a "little extra" but a whole source of the shields throughout the fight, basically. Usually you barely ever skill with Aven, if the team synergizes with him well. This trace is the sole source of shielding. So, when it broke, skill becomes the only source of shielding, as the shields run out and aren't organically replenished. Which many teams can't really afford SP-wise to keep up consistently. So the team takes damage, a lot of it. That trace was the backbone 🥲
The appropriate amount of apology Jades would be enough to cover those who couldn't complete Apocalyptic Shadow, MoC and Pure Fiction between his breaking and his fixing BECAUSE of this. But I wouldn't be surprised if it's a low amount anyway 😑
Same, I just felt like I had to use his skill way more often lately when before, his FUA was usually enough. Blamed stronger enemies, turns out it was this bug 😂
didn't even feel a thing since i heard about the bug man. people complained about talent bug and i absolutely understood that it's the double shield talent that was bugged (cause who tf cares about the cr talent😂). but idk, i think my aven's shield was too tough that double shield wasn't needed (tough, as in strong enough to tank damages from all 3 monthlies and UD)
I remember finding this bug the hard way when I was in DU 6 and Aventurine was having to use his skill every turn to keep the party alive. Keep in mind, my Aventurine is basically whaled-out at E2/S2 with crazy good relics and maxed out traces. I legit thought "Man, if it's going to be this hard for me, I wonder how the F2P community is feeling," only to watch them screaming in flames as the enemies bodied them. I got a good kick out of this unintentional debuff to everyone's favorite gamba twink.
As a F2P I didn’t really notice cause of how well my characters are built so I usually just need to skill once then let my dps handle it but when I was clearing MoC I was get bodied over and over and had no idea what was happening to my shields
As someone who was a one time spender on nameless honor and has an E6S5 Aven it is annoying in especially auto battle and the ult can't be spammed so one of my team mates (always Sunday somehow) kept dying too often
As an F2P E4S1 haver (deadass did not pull for anyone else after him), god I thought his E4 would make sustain way better after his rerun so it was rlly frustrating finding out 💀
That makes so much more sense, I came back to Star rail recently to prefarm for Madam Herta and while catching up to the story I notice Aventurines shield just weren't performing as good as they used too. I thought it was just Aventurines shield being out Damaged by the new enemies so I just accepted that my Yunli would take some DMG and she could just heal it up. But knowing now that its a bug makes me feel slightly better. Hopefully they will patch it in 3.0 so my Madam Herta isn't dying.
the biggest irony to this bug is that despite all the programmign work they did in making memosprites treated as allies with unique health bars and targetability... in practice they play identical to the summons we already have except now they can die, and they have to be explicity targeted by all forms of single target buffs.. oh and their kits are an entire novella long so-
yeah I was disappointed seeing Aglaea's summon works a lot like Follow up summons, instead of us can actually control it's attacks using skills, etc. just like a fifth character
This is likely going to vary by memosprite, the reason being that this kind of interaction has existed in a previous event that in hindsight seems like a test for summon mechanics. One was mostly based on summoning trashcans for attacks that were more like follow ups. One summoned trashcans on the enemy side instead of yours etc.
its such a disappointment. Star rail has been on its flop era for such a long time now. It is almost like rememberance is jsut a gimmick for them and a way to sell LC, since people wont pull for them if they better ones. And the fact that there is so few rememberance units planned, oh and not a single 4 star or male one. Hoyo is such a flop nowadays, I wish dawei would step down already.
@@Ayush-kc2vxin some teams this targeted shielding really matters Of course if it's fexiao with robin you'll kill all the enemies before you even notice but in not really strong teams and in some situations where Aventurine is not the best sustain (against some bosses) the team actually strongly needs this targeted shield
i can understand the devs perspective like i took a programming class once cause my mom wanted me to try it. i made like a simple game but wanted to add a feature but then everything just stop working properly and i kinda just waited and pray that the teacher can fix it
In code, unfortunately, touching even one thing breaks everything. Once I didn't even touch the code itself, just one comment, next thing I know it's sending error despite the fact that it didn't before(???. Istg sometimes the apps just break themselves
@@asafesseidonsapphire documentation won't save me from the semicolon that is definitely there but the thing marks as not being there for some weird reason, sadly
as someone learning programming as a hobby myself, i cant believe i never thought of the issue linking to sunday! imo this does seem like a easy immediate fix but based on this video, i feel like taking their time on this to observe all the character ability interaction, with aventurine being the biggest factor, could give them a few more ideas for future characters too
@@LuxminosityBoy not even "every now and then" really, just like maybe once at the start of the battle to set everyone to have like 60-70% of their HP covered and then just forget about it (unless the enemy just keep targeting that one ally)
@@manitshah1019 That's the entire point of my comment. The video said "December 3rd, 2023" was Aventurine's most recent banner but that's before Aventurine even came out
I thought that's because, they don't want to give 100 stellar jades, so they keep us waiting until they will fix all crucial bugs at 3.0, to give 600 jades as usual, without any added bonuses
@@nameskit by removing a passive that's already written? Genshin tried that with Neuvillette and they got reported to the chinese government lol To everyone that corrected me, thanks for letting me know. Though even if I'm wrong in the analogy, the outcome would probably be the same
As both a gamer and a programmer this was pretty interesting, and probably a likely scenario. Funnily enough I've been running Aventurine since his original run and didn't really have any issues during 2.7.
There are few things at factor when it comes to whether or not you'd have issues with Aventurine. Lots of players are casual, which means stats aren't always optimized (shield strength not being what it could be). If you have an E1 Aventurine, his shield-uptime is crazy strong, but most Aventurine owners stick with him at E0. Lastly, if you have really strong DPS capable of clearing endgames modes with ease, you might not be experiencing the enemies' attacks quite like the average F2P account.
@shadesofblue8425 he's currently still E0S0 (lost my third 75/25 e_e). But he's in my E0S1 Acheron + Jiaoqiu team so that tracks. It's a annoying bug for sure, and I do feel for people especially those that got him during 2.6.
If like this then every ally need to be better to use linked list of an character class, because probably they will update character property if they have a targetable summon or no, if they have a targetable summon then the linked list reference need to be pushed and add the summoned remembrance stuff to be on the list as a mob object/class or something similar to it
Really neat insight, thank you! It was so shocking to snag his E1 and then go from feeling completely untouchable to struggling against even the older weekly bosses.
Guys remember even if hoyo is aware of the bug and we will likely get stellar jades for it, you can always “complain” (Say how the bug has impacted your enjoyment of the game significantly) using the in game feedback feature (phone -> bug report -> feedback) or email them. I’m crossing my fingers that because this bug has negatively impacted so many, if we are vocal enough about it they will actually give proper compensation for the people who couldn’t compete end game contents because of it.
Firefly E1 is due to tye new Pf, because the new effect allows allies to not skills points, Firefly e1 who doesn't need skill point will revert it to consume skills points, it is probably an error in the code. Himeko fua isn't a bug and is always intend to be this way. It will work as along an ally hits an enemy or enemy summons new enemies or enemies enter the battle in anyway
afaik ff e1 is bugged in pure fiction when u run the buff that makes it so u consume no skill points when grit is active, you end up actually consuming skill points which is quite funny but also it’s kinda a non issue because literally just use the break buff
Here's the bug for firefly's e1: U need to have at least one sp to use her enhanced skill (even tho with e1 she doesn't consume sp in ult mode) Idk what Himeko's bug is... Herta has a bug actually: sometimes her follow-up won't trigger despite the enemies being 50% or lower hp
literally the reason why my apocalyptic shadow is still 11/12 … MoC tomorrow is gonna be fun 😭 I'm still of the opinion they should fix it asap. Your characters are the core aspect of the game, they NEED to work. And it's not like Aventurine is the only one
If you've already cleared within 10 cycles you can do one run that focuses purely on survival even if you use more cycles. Each goal is targeted individually so you don't need to achieve all three in the same run for it to count. 😉Just a heads up if you weren't aware already. If you were, my apologies.
IMO if the memosprite logic is coded like an ally, including taking up a party slot, then the absence of memosprites would not be different from say, having a party with empty slots, i.e. less than 4 characters. You mentioned Aventurine having his shield going to a non-existent ally because it might incorrectly include an empty slot as a 'valid ally'. If I were theory-debugging this, I would then question whether a pre-2.7 Aventurine would have the same problem in a party with less than 4 characters. Would his shield go to the empty 4th slot by treating it as the ally with lowest shield?
As someone who went through the very tedious effort of saving for more than six months collectively to be able to e6s5 as an f2p, I am so mad dude. I appreciate you explaining it so I know exactly what to say when the surveys roll around
If this is actually the case it wouldn't be an easy to fix since it means that they have to code early characters separately from the one with summon mechanics which mean many and many more code to fix jeezzz.
Thanks for explaining it! I rely so much on my Aventurine, and the percictance of the bug was starting to scare me. Now it kinda makes sense, even if it's still annoying. But at least I can rest easy knowing they're not nuking him on purpose and it'll probably go away with 3.0
That does seem like a mild error in the checking, maybe they could just consider a random team mate as the main target of the buff before checking all the team shields and, even if the checks don't change the main target, activate it anyway and give it to the starting target unit. Also, wouldn't be reasonable to just make him ignore Memosprites? I can't think of a situation you would want a Memosprite to be more protected than a character, since you can just re-summon it.
Genuinely hope they take this bug seriously and give a lot of compensation because they haven't even acknowledged it and it's been a thing since 2.7 released
Now that i think about it, Sunday almost had the same issue buffing enemies the same way Aventurine had with the new system. The difference was that the buf was caught BEFORE 2.7's release
I wish that was the case lol, its been quite frustrating to see how much weaker Aven's sustaining capabilities have become just from missing one trace.
My guess is that if a character doesn't have a Memosprite, it's being treated as if there were a Memosprite with 0 HP and which doesn't act, or something like that. The end result is that Aventurine is always trying to target this 'Null Memosprite' since it has 0 Shield.
If they don't fix it next patch it's gonna be because they want to push people to get Lingsha. Which would be very scummy to say the least, but aside from that the bug would maybe get them sued if it is left there for too long. I'm sure they must know the risks, I'd be extremely surprised if these issues are not fixed as soon as 3.0 hits
Just so you know, the bug for quid pro quo and aventurine were already fixed in the beta following its appearance. qpq bug was already fixed in 2.7 beta despite being in both 2.6 beta and live and the aventurine bug has already been fixed in the 3.0 beta. Maybe they were unable to push forward the fixes due to higher ups saying no, seeing as fugue's signature lc was hotfixed about a week before her banner release. And this is happening right after aventurines rerun and right before lingshas rerun.....
Oh my dude ty so much for explaining this bug. I really have no idea what kind of bug is happening that makes my team died faster since 3.0 I hope they really fix this problem cause it's really helpful for me
If like this then every ally need to be better to use linked list of an character class, because probably they will update character property if they have a targetable summon or no, if they have a targetable summon then the linked list reference need to be pushed and add the summoned remembrance stuff to be on the list as a mob object/class or something similar to it
I was questioning if this bug even really existed because I never noticed an issue with my Aventurine since I got him last patch. Now I’m convinced he’ll be literally unstoppable once this is fixed🤷♂️
While this is a plausible explanation on first pass, this omits the fact that fallen characters have similar property to a 'unsummoned' memosprite. That being they have 0 HP, cannot be selected and cannot obtain buffs (such as Fortified wager). If the flawed logic follows from a check that mistakenly took a 'unsummoned' memosprite, it is more than likely that it could've happen with fallen characters pre-2.7. The bug is MORE likely to be in the code that checks whether a unit is valid to obtain the 'Fortified wager' buff, than the shield value check. Just some thoughts.
I'm not a coder but wouldn't the variables for mem downs and unit downs be different? Mem downs won't remove the last star in a moc clear, and probably won't trigger death effects like bailu
man, thanks for this video, my Aventurine was acting strange lately, its shields were weak even when I had the Gepard cone on and the follow ups were barely giving good shields
I couldn't beat the latest boss cuz of the for the longest time. I had to beef up my Jing Yuan and Sunday and still had aventurine in my team since did better but jesus I was wondering why I kept dying in the beginning right when I saw a meme saying he was broken 😭
thing is i wouldn't care if the trace that got bugged was his crit trace, but no it's his SHIELD trace. he's a sustain, his main job is to sustain, his sustaining capability is bugged and it's gonna take them a whole patch to fix (hopefully not more) like hell nah they better give us a great compensation for this
honestly the devs are probably stuck between rock and a hard place with a fix: 1) They make it so it checks ALL allies, including summons. This breaks adventurine since it means he'll end up giving shields to the summons, meaning he ends up sucking for any team that has a summon that needs it to take damage, and also sucks for the summoner since he doesn't give them the shield, ever. 2) They make it so it only checks "player" allies, at which point it sucks for summoners because he won't shield the summons. The bug is probably just pushing them to do more testing to come up with a solution.
It just shows how "summons 2.0" were a stupid idea from the start. If Aven ends up only working properly with a Rmmb char on the team, forever, it will essentially brick him for those who are not interested in playing a Rmmb DPS, and force them to pull another limited sustain cause these days you really need 2.
I can only imagine they set some value related to the memosprites to '0' to avoid a null pointer exception in Sunday's kit, and that the 3.0 architecture will be more robust. It tripping up Aventurine was almost certainly just a missed interaction, or ... quite frankly an understood one that was more trouble than it was worth to handle before the entire update is rolled out. Gods know I've pushed some MVP stuff with similar known 'bugs' in it because we had to account for a future integration that we had no way to reasonably work around in the timeframe we had.
I mean, Hoyo is a multi million dollar company. They are very able to fix things quickly and have proven so multiple times before. So "being lazy" is probably not what's happening... I will place my bets on 3.0 fixing this issue as you said 👍 thx for the clear explanation abt why could've caused the delay!
Unfortunately being a multi-billion dollar company can slow things down. HSR is a lot of code. Code is easier to fix if it's something small and segregated to one character but if it's in the targetting mechanic in general pushing out a hotfix too fast risks breaking a lot of other stuff. Not to mention the communication. The bigger a dev team or company is, the slower it gets and money can't fix that.
@@deletedflame8424doesn't make sense. Why are they placing in 3.0 mem updates in a version that doesn't need them. They have beta and experiment servers for that, so why roll out an update before the actual patch?
Himeko fua bug probably the most annoying one. He fua charge has full 3 charge but only trigger after an ally take action. She was suppose to automatically use fua when the charges is full. It really annoying as himeko is 1.0 character that has no overcap on her fua charges. This bug has been fix before right?
its not a bug, its a feature, if you read her talent it says "if Himeko is fully charged when an ally performs an attack, Himeko immediately performs 1 follow-up attack"
@LucasGomes-ng2go himeko can consistently fua when she break and fully charged without ally attacking. You mean fua without ally attacking is the bug? That kinda weird since there are no overcap on her charges
@zuaer1849 well I don't make the rules, you can read her talent for yourself, it says she'll only do Victory Rush if she has 3 stacks and an ally just attacked
@@LucasGomes-ng2go sorry if i'm sound confrontational. I'm just confused. i'm already know what written on the talent. i always assume it wording problems this whole time. She consistently fua the moment the charge is full. Even breaking and fully charge with another ally can trigger her fua. this is a convenient bug i guess.
we really do need compensation it's hard to clear endgame content with Aventurine being bugged like this for some people. They would most likely have this bug fixed by v3.0 instead of it being on a separate maintenance
lol i'm not the only one who suspected this too, my first thought when I heard you describing the skill & the context of a backend update was that the ally list is probably looking at shield values for a character/summon entity that doesn't exist.
what i'm taking away from this is that sunday held a grudge and cursed aventurine all over again
😂
Best comment ever🤣🤣🤣🤣
It's funny, bc Sunday is one of those allies that might get targeted more and end up getting that low amount of shield. (It's usually beneficial to put him in the middle slots so you get more energy) I've seen so many people joke about how Sunday is "the new Tingyun" taunt-wise, and most of them also had Aventurine on the team in their screenshots.
@@phrinus And the fact that i'm having this exact problem w aventurine bug bc my sunday keeps getting hit and has a low shield all the time 😭🫠
@@phrinusXD he does get slapped around a lot. I figured it was a bug.
"I've recently graduated with a degree in computer science"
My condolences
He will make a homeless tips video soon
my CS career might be cooked so I'm very thankful I can make some money from these videos 🗿
Femboy Arc is going to go so hard😂
How bad is the Job Market actually
@@RedFlaim I'm a year away from graduating (Haven't learned shit) and I'm seriously thinking of setting up the scummiest easy to sell of
I was so confused to why some of my characters' shields were depleting so fast even though Aventurine was just spamming his FUA. Thanks for the insight
right my exact experience too
Yep Sunday Bugged him
same i had to spam his skill like crazy and confused
Fr, felt like I was using a slightly stronger PMC 😅
i mean it only effects single target sheilding, his aoe shields should be the same.
That was my first thought too when hearing about the bug, Aven's ability parsing each ally's shield value but instead of returning the actual lowest value it's returning 'undefined' or '0' associated with a memosprite that doesn't exist
so they just must add a command that states "put the shield on the character with the lowest value [ slots with 0 hp" right...?
But what about fallen characters? If it returns the lowest, then it should've been bugged since release since fallen allies will also return 0 while not being able to gain the extra shield. Isn't it more likely that the 'each valid ally' check was wrong and the code that check for array of fortified wager holders couldn't determine correctly whether a memo-sprite is 'active' or 'fallen', perhaps due to a incorrectly inherited memo-sprite interface that defaults true for isActive checks? This is more likely as not only aventurine is bugged but also a wide array of other characters, plus the long time it is taking the devs to fix it (bug in memo-sprite interface -> have to retest every single memo-sprite interaction)
@@harryhsu7980
I’d imagine that “dead” characters return a different variable entirely so they can be written out of the equation when considering who to give the shield to. But if the default variable for the memosprite is not the same as a “dead character” then thats where the “undefined” or “0” portion comes in. After all, just because a character is at “0”, doesn’t mean they are permanently dead which allows for other passives to take effect once they hit 0(see also: Bailu’s revive and Arlan’s E6). But because memosprites cant be “permanently dead”(as MC snd Agalaea can both resummon them) some programmer decided to leave it at “0” or “undefined”which means Aventurine’s shield keeps giving the un-summoned Memosprite a shield when it doesn’t exist.
@@loststorm-platinium we don't know the inner working of their code, but game development is insanely complex because there are so many moving parts, especially when characters are interacting with each other in way that will directly change their states and values. the solution could just be a simple as setting the isAlive state of the invisible teammates to false, but they couldn't really risk making that hotfix. The apple app store and PlayStation store are REALY strict with their policies it takes at least a week for them to verify and push your update, and IF the hotfix ends up introducing a new bug (likely to Sunday) they'd have to waste another 2-3 weeks sending a hotfix, they'd never risk breaking Sunday because this is HIS patch so if he's broken people will be mad, it's a lot saver to just fix it next patch.
So there's possibility that future sprites (after aglaea and rmc) have health and shield bar
In the newest HSR youtube video they kinda hint towards this being the case, as they say that implementing the new path gave them a lot of issues since it changed so many characters interactions.
And they said, the implementation of this new battle line up took more work, than anticipated (by complaining about working overtime so much, they forgot when is day and when is night). I feel sorry for them for that and also grateful.
But also... this bug is too big for not getting fixed through an entire patch (but I think, they figured, in next patch it won't be an issue anymore, so...better to just pay compensation).
BRUH ITS HOYOCUCK
@@ashy969 people often say stuff like HYV devs have no excuses bc of the money its games rake in, but behind every successful game are overworked programmers. game devs fr some masochists, it's a career you have to have some mad passion for.
@@nilmerg Agreed, and not just programmers. My sister was an animator for games and TV cartoons, and she does unpaid overtime almost everyday. She has to ask to go home earlier (usually allowed, but sucks that you have to inform your superior just to go home on time)
She says 3D modelers and riggers always do unpaid OTs too. In the company she worked in, at least.
@@DilysCheong1998 its very common.. in asian countries for these things but for the US and europe that is all illegal outside very specific circumstances
No wonder my Aventurine has been feeling weak... I thought it was just stronger Opponents. Thanks for the insight 👍
Kinda both
1k likes yay!!!
I need 30 pulls worth apolojades for this
Nahh, free aventurine for everyone
With tribbie jioqiu new match 7th @@hayemdr3474
@@hayemdr3474best I can do is 160 jades and 3 sentences of explanation
@@hayemdr3474 I do want that E2... So it's welcome with me
While 4800 Jades sound a lot...
That's barely anything. Won't guarantee me *THE* Herta.
The bug apparently also happens to Luocha's emergency heal as well.
Luocha and galla are my 2 main sustainers, i didn't get lingsha cuz i deleted hsr for zzz and only came back for sunday, i failed to get every other sustain after luocha's release even including the standard characters
I've been using luocha exclusively as my solo sustain in SU game modes trying to catch up to the higher levels i wasn't present for and just other general stuff, I've never noticed anything wrong with luocha's emergency heal can you please elaborate
Huh, my Luocha's emergency heal was working fine... I think. But if both of my primary sustains were bugged, I'mma be upset.
Given he is my only limited sustain and he works just fine idk what you mean tbh
Last week i failed Moc because my Gallagher Basic atk (E5,max traces) did not heal 🤡
I used him last week for some side content where you can use trial Luocha and Blade. To me it seemed like it worked as intended & I didn't even need to use his healing skills
My first thought is that Each character has a memosprite slot and since memosprites are also counted as allied aventurine also gives shields to them. However, since there's bound to be empty ally slots aventurine gives a sheild to them that just resets to 0 or undefined since there's nothing in that slot, which means that those slots will always have the lowest shield value.
Basically an endless cycle of giving shields to the empty slots>shields resetting to 0>passive occurs in the empty slot since it has the lowest shield value>Being reset to 0 again.
This is just how I thought of it.
And non-memosprite allies likely have non-0 values already set for them when the slots are empty or the characters are dead to prevent the bug from when aven first released.
edit: as in, the non-memosprite slots.
@@tenacity25 If that's true, someone needs to test him with Jing Yuan or Lingsha, since both have summons.
@@EvaHoshizora summons like lightning lord have no hp value as they can't be attacked.
@@EvaHoshizora those summons aren't coded as actual allies tho, more like detached follow up attacks. memosprites are actually j additional characters.
@@EvaHoshizora the summons we have in the game right now aren’t really real summons. They are considered more closely related to a follow up . When we talk about summon, we’re talking about an additional character that is targetable in someway.
Weirdly enough it’s actually pretty noticeable. I never realized how useful that little extra buff is 💪
FR. as a day 1 Geppie main turned aven main... even the slightest of damage is enough to cause me panic hahaha I AM SO NOT USED TO TAKING DAMAGE like even just a hundred or so damage makes me feel like I've been hit big time by the enemies and yeah this bug really is bugging me coz I can't even play in auto in peace. Especially when i play conundrum 6 and above which i can comfortably play on auto before, now I have to really time when to use Aven's skill
It is actually not a "little extra" but a whole source of the shields throughout the fight, basically. Usually you barely ever skill with Aven, if the team synergizes with him well. This trace is the sole source of shielding. So, when it broke, skill becomes the only source of shielding, as the shields run out and aren't organically replenished. Which many teams can't really afford SP-wise to keep up consistently. So the team takes damage, a lot of it. That trace was the backbone 🥲
I noticed it immediately with Yunli 😂
The appropriate amount of apology Jades would be enough to cover those who couldn't complete Apocalyptic Shadow, MoC and Pure Fiction between his breaking and his fixing BECAUSE of this.
But I wouldn't be surprised if it's a low amount anyway 😑
zzz players got 20 pulls for a glitch that wouldn't let them look up their characters skirts, we need at LEAST twenty pulls.
@@sleepyfemboyaku Yeah but that really makes the game unplayable, unlike Aventurine's bug.
@@sleepyfemboyaku What? It was only 300 polychromes for this glitch, other pulls were not for this.
@@sleepyfemboyaku Can't believe this counts as a glitch in the first place... it's not a hentai game, ppl
I mean not so long ago genshin players got a whole 10-pull because a bug in Neuvillete was fixed in a way that actually made him weaker lmao
I didn’t even know this was happening. When I used Aventurine, I thought something was off, but I couldn’t actually tell what it was
FR I thought I built him wrong all of a sudden even though he's capping out on Def%.
Same, I just felt like I had to use his skill way more often lately when before, his FUA was usually enough. Blamed stronger enemies, turns out it was this bug 😂
I had his traces at 8 and I got them to 10 recently because of this lol
didn't even feel a thing since i heard about the bug man. people complained about talent bug and i absolutely understood that it's the double shield talent that was bugged (cause who tf cares about the cr talent😂). but idk, i think my aven's shield was too tough that double shield wasn't needed (tough, as in strong enough to tank damages from all 3 monthlies and UD)
Deadass... I never even noticed, but the insight to programming was cool.
Shows how Broken he is when he's bugged and still works.
@@silverhawkscape2677 he is the honoured one 🗣️
pfp checks out
Me neither, but I never had Aventurine until 2.6. so that's why I didn't noticed
Feeling enlightened. I was so lost as to why Aventurine's shields were being depleted quicker than usual.
I remember finding this bug the hard way when I was in DU 6 and Aventurine was having to use his skill every turn to keep the party alive. Keep in mind, my Aventurine is basically whaled-out at E2/S2 with crazy good relics and maxed out traces. I legit thought "Man, if it's going to be this hard for me, I wonder how the F2P community is feeling," only to watch them screaming in flames as the enemies bodied them. I got a good kick out of this unintentional debuff to everyone's favorite gamba twink.
As a F2P I didn’t really notice cause of how well my characters are built so I usually just need to skill once then let my dps handle it but when I was clearing MoC I was get bodied over and over and had no idea what was happening to my shields
Your past protocol 5... telling us you used aven skill means nothing lmal
As someone who was a one time spender on nameless honor and has an E6S5 Aven it is annoying in especially auto battle and the ult can't be spammed so one of my team mates (always Sunday somehow) kept dying too often
I beat DU 6 with a lvl 70 adventurine E0S0 on my alt account with only 3k defense with no issues. You must’ve had a very bad build in DU
As an F2P E4S1 haver (deadass did not pull for anyone else after him), god I thought his E4 would make sustain way better after his rerun so it was rlly frustrating finding out 💀
That makes so much more sense, I came back to Star rail recently to prefarm for Madam Herta and while catching up to the story I notice Aventurines shield just weren't performing as good as they used too. I thought it was just Aventurines shield being out Damaged by the new enemies so I just accepted that my Yunli would take some DMG and she could just heal it up. But knowing now that its a bug makes me feel slightly better. Hopefully they will patch it in 3.0 so my Madam Herta isn't dying.
I noticed the bug on Yunli too 😂 She Is the best user of Aventurine talent
the biggest irony to this bug is that despite all the programmign work they did in making memosprites treated as allies with unique health bars and targetability... in practice they play identical to the summons we already have except now they can die, and they have to be explicity targeted by all forms of single target buffs.. oh and their kits are an entire novella long so-
yeah I was disappointed seeing Aglaea's summon works a lot like Follow up summons, instead of us can actually control it's attacks using skills, etc. just like a fifth character
This is likely going to vary by memosprite, the reason being that this kind of interaction has existed in a previous event that in hindsight seems like a test for summon mechanics. One was mostly based on summoning trashcans for attacks that were more like follow ups. One summoned trashcans on the enemy side instead of yours etc.
its such a disappointment. Star rail has been on its flop era for such a long time now. It is almost like rememberance is jsut a gimmick for them and a way to sell LC, since people wont pull for them if they better ones.
And the fact that there is so few rememberance units planned, oh and not a single 4 star or male one. Hoyo is such a flop nowadays, I wish dawei would step down already.
@@lostblueboy wtf?? What about Mideus and Phaenon, they have a summon too.
@@polya_bullet Mydei and Phaenon are not Remembrance tho?
YESS APOLOJADES. Always worth suffering through a bug for. It barely affects my team when i use aventurine anyways
It's led to me dying in MOC 😭😭😭
@Juliette4815 sounds like a skill issue 🫥
Hsr 0.5 jades take it or leave it
@@Ayush-kc2vxin some teams this targeted shielding really matters
Of course if it's fexiao with robin you'll kill all the enemies before you even notice but in not really strong teams and in some situations where Aventurine is not the best sustain (against some bosses) the team actually strongly needs this targeted shield
@@weikat569 i don't have Robin 🫥. I use Fexiao with bronya
i can understand the devs perspective like i took a programming class once cause my mom wanted me to try it. i made like a simple game but wanted to add a feature but then everything just stop working properly and i kinda just waited and pray that the teacher can fix it
In code, unfortunately, touching even one thing breaks everything. Once I didn't even touch the code itself, just one comment, next thing I know it's sending error despite the fact that it didn't before(???. Istg sometimes the apps just break themselves
@@tokutske That's why documentation is important.
@@asafesseidonsapphire documentation won't save me from the semicolon that is definitely there but the thing marks as not being there for some weird reason, sadly
@@tokutske its like u think one of the features will jsut change by themself in isolation but then everything breaks. like tf D:
@@tokutske No, apps don't break themselves. Your shitty code does.
as someone learning programming as a hobby myself, i cant believe i never thought of the issue linking to sunday!
imo this does seem like a easy immediate fix but based on this video, i feel like taking their time on this to observe all the character ability interaction, with aventurine being the biggest factor, could give them a few more ideas for future characters too
Aventurine's shield: Bugged
Gepard: "You couldn't live with your own failure, where did that bring you? Back to me."
Aventurine still outshields Gepard, it's just that he now has to use a skillpoint every now and then
Inaccurate, sadly. Aventurine can still generate shields at a constant pace. Better give an energy rope with lots of ERR to Gepard and spam that Skil!
Gepard genuinely survives better
@@LuxminosityBoy not even "every now and then" really, just like maybe once at the start of the battle to set everyone to have like 60-70% of their HP covered and then just forget about it (unless the enemy just keep targeting that one ally)
nah if Aventurine is still bugged in 3.0 I'll go back to Fu Xuan lol
0:50 slight typo on the year. Last year was 2024, Aventurine wasn't yet out in 2023
Blud Penacony wasnt out in 2023
@@manitshah1019blud aventurine came out in 2024
@@manitshah1019Yk that’s what they meant?
@@manitshah1019 That's the entire point of my comment. The video said "December 3rd, 2023" was Aventurine's most recent banner but that's before Aventurine even came out
@@manitshah1019 reading comprehension where
I thought that's because, they don't want to give 100 stellar jades, so they keep us waiting until they will fix all crucial bugs at 3.0, to give 600 jades as usual, without any added bonuses
Naah they always give separate compensation if it's a known issue.
@@wickedviewer2346Imagine this is the first time they don't lol but hope not
I think they just want to nerf aventurine to replace him with a different preservation unit
@@nameskit but this is not the correct way to nerf something
@@nameskit by removing a passive that's already written?
Genshin tried that with Neuvillette and they got reported to the chinese government lol
To everyone that corrected me, thanks for letting me know. Though even if I'm wrong in the analogy, the outcome would probably be the same
5:21 As a person with Aventurine in pretty much any team I will GLADLY take the jades.
As both a gamer and a programmer this was pretty interesting, and probably a likely scenario.
Funnily enough I've been running Aventurine since his original run and didn't really have any issues during 2.7.
There are few things at factor when it comes to whether or not you'd have issues with Aventurine. Lots of players are casual, which means stats aren't always optimized (shield strength not being what it could be). If you have an E1 Aventurine, his shield-uptime is crazy strong, but most Aventurine owners stick with him at E0. Lastly, if you have really strong DPS capable of clearing endgames modes with ease, you might not be experiencing the enemies' attacks quite like the average F2P account.
@shadesofblue8425 he's currently still E0S0 (lost my third 75/25 e_e). But he's in my E0S1 Acheron + Jiaoqiu team so that tracks.
It's a annoying bug for sure, and I do feel for people especially those that got him during 2.6.
If like this then every ally need to be better to use linked list of an character class, because probably they will update character property if they have a targetable summon or no, if they have a targetable summon then the linked list reference need to be pushed and add the summoned remembrance stuff to be on the list as a mob object/class or something similar to it
@@shadesofblue8425 True. That E1 makes a big difference.
You will notice this bug immediately when using Yunli. I switched Aventurine cone to Gepard One to reduce the Number of attacks directed to Yunli xD
Really neat insight, thank you! It was so shocking to snag his E1 and then go from feeling completely untouchable to struggling against even the older weekly bosses.
Make more of these! explanations of why bugs happen are important for the better understanding of how the game functions for the players!
4:27 that feixiao ult tho ToT
Soo the bonus shield went into what basically an empty slot supposed to be the memosprites.
I WANT 10,000 STELLAR JADES FOR THIS HOYO
Thanks for the explanation
Guys remember even if hoyo is aware of the bug and we will likely get stellar jades for it, you can always “complain” (Say how the bug has impacted your enjoyment of the game significantly) using the in game feedback feature (phone -> bug report -> feedback) or email them. I’m crossing my fingers that because this bug has negatively impacted so many, if we are vocal enough about it they will actually give proper compensation for the people who couldn’t compete end game contents because of it.
I also heard that other abilities are bugged
Examples are Loucha's Healing field, Firefly's E1 (Which i highly doubt), and Himeko's FUA
Firefly E1 is due to tye new Pf, because the new effect allows allies to not skills points, Firefly e1 who doesn't need skill point will revert it to consume skills points, it is probably an error in the code.
Himeko fua isn't a bug and is always intend to be this way. It will work as along an ally hits an enemy or enemy summons new enemies or enemies enter the battle in anyway
afaik ff e1 is bugged in pure fiction when u run the buff that makes it so u consume no skill points when grit is active, you end up actually consuming skill points which is quite funny but also it’s kinda a non issue because literally just use the break buff
Here's the bug for firefly's e1:
U need to have at least one sp to use her enhanced skill (even tho with e1 she doesn't consume sp in ult mode)
Idk what Himeko's bug is...
Herta has a bug actually: sometimes her follow-up won't trigger despite the enemies being 50% or lower hp
@Salientspeaker56 ohh
I thought the Def ignore is bugged
New PF really conflicts with old mechanics
I just hope they'll actually fix it and not shadow nerf him
I'll be so angry if they just weaken him because oh well they were just to lazy to fix it
Bug and Hoyo are like man and shadow, always appearing together in ways no one would expect like Aventurine's bug 💀
As long as they give jades .. it's all good
Loved the explanation!!! You did a good job of presenting the info in a way that was easy to understand!
I'm gonna be honest, I didn't even realize there was a problem lol, the man's just that busted
"Being lazy is a possibility" is the most CompSci student answer ever and I totally relate and agree
literally the reason why my apocalyptic shadow is still 11/12 … MoC tomorrow is gonna be fun 😭 I'm still of the opinion they should fix it asap. Your characters are the core aspect of the game, they NEED to work. And it's not like Aventurine is the only one
Same, the amount of times I got close to clearing apocalyptic shadow with full stars but my characters just keep dying
If you've already cleared within 10 cycles you can do one run that focuses purely on survival even if you use more cycles. Each goal is targeted individually so you don't need to achieve all three in the same run for it to count.
😉Just a heads up if you weren't aware already. If you were, my apologies.
congrats on graduating! and thanks for the video, it was very cool to hear how the bug could've come up
At least 30 pulls worth of apology Jades forsure. I gotta imagine this bug ruined someone's MoC runs
Happy graduation! Thanks for giving us some insight with your expertise as a CS grad and as a longtime star rail player
we are expecting 1600 stellar jades
This video hits home real close. Robin has been and will always be the one who has the lowest shield
This is EXACTLY what I was expecting was happening.
This super hurts some DU+8 runs.
genuinely trying to imagine aventurine going "the math ain't mathing, where are the other shields??" and deciding not to calculate it
IMO if the memosprite logic is coded like an ally, including taking up a party slot, then the absence of memosprites would not be different from say, having a party with empty slots, i.e. less than 4 characters.
You mentioned Aventurine having his shield going to a non-existent ally because it might incorrectly include an empty slot as a 'valid ally'. If I were theory-debugging this, I would then question whether a pre-2.7 Aventurine would have the same problem in a party with less than 4 characters. Would his shield go to the empty 4th slot by treating it as the ally with lowest shield?
Oh my God I thought I was losing my mind. It's so brutal how badly it can hurt some tough runs.
y'all's aventurines was underperforming, all of a sudden my aventurine triggers fua more often and his shields stack more than usual 😭
As someone who went through the very tedious effort of saving for more than six months collectively to be able to e6s5 as an f2p, I am so mad dude. I appreciate you explaining it so I know exactly what to say when the surveys roll around
Honestly considering the other glitch has been fixed and this hasn't, it leads me to believe they'll fix this in 3.0
Plot twist he is the emanator of preservation
Patch notes for 3.0 says it fixed now. The prediction was true
But is it fixed now…?
So this is the reason, i really thought the enemies just got buffed like crazy. I hope they fix this soon
oh so that was why i kept dying on some bosses that i used to beat , since i didn't have to worry about dying ...
i’m so glad someone’s talking about this my chars shields literally evaporate randomly 😭
If this is actually the case it wouldn't be an easy to fix since it means that they have to code early characters separately from the one with summon mechanics which mean many and many more code to fix jeezzz.
most things that seem like an easy fix.. often turn out not to be an easy fix...
Thanks for explaining it! I rely so much on my Aventurine, and the percictance of the bug was starting to scare me. Now it kinda makes sense, even if it's still annoying. But at least I can rest easy knowing they're not nuking him on purpose and it'll probably go away with 3.0
That does seem like a mild error in the checking, maybe they could just consider a random team mate as the main target of the buff before checking all the team shields and, even if the checks don't change the main target, activate it anyway and give it to the starting target unit.
Also, wouldn't be reasonable to just make him ignore Memosprites? I can't think of a situation you would want a Memosprite to be more protected than a character, since you can just re-summon it.
Funny story: I found out this game was made in Unity when it crashed and the error window said "Unity"
And 2 weeks later, he's still bugged, istg gepard has a stronger shield rn/j
Genuinely hope they take this bug seriously and give a lot of compensation because they haven't even acknowledged it and it's been a thing since 2.7 released
This definitely explain by i was having issues with him in swarm disaster smhh
Note mine is built his light cone an about 42k defense
Now that i think about it, Sunday almost had the same issue buffing enemies the same way Aventurine had with the new system. The difference was that the buf was caught BEFORE 2.7's release
Imagine the guy who posted that, didn't unlock his last trace lmao
I wish that was the case lol, its been quite frustrating to see how much weaker Aven's sustaining capabilities have become just from missing one trace.
My guess is that if a character doesn't have a Memosprite, it's being treated as if there were a Memosprite with 0 HP and which doesn't act, or something like that.
The end result is that Aventurine is always trying to target this 'Null Memosprite' since it has 0 Shield.
If they don't fix it next patch it's gonna be because they want to push people to get Lingsha. Which would be very scummy to say the least, but aside from that the bug would maybe get them sued if it is left there for too long. I'm sure they must know the risks, I'd be extremely surprised if these issues are not fixed as soon as 3.0 hits
I am NOT spending my tickets on yet ANOTHER healer when I have the best shilder in the game + bailu
ppl spent money on aventurine they'll definitely get sued otherwise
the fact that he still tanks like a beast despite this will only mean that once the bug is fixed he'll just be better than ever
Just so you know, the bug for quid pro quo and aventurine were already fixed in the beta following its appearance. qpq bug was already fixed in 2.7 beta despite being in both 2.6 beta and live and the aventurine bug has already been fixed in the 3.0 beta. Maybe they were unable to push forward the fixes due to higher ups saying no, seeing as fugue's signature lc was hotfixed about a week before her banner release. And this is happening right after aventurines rerun and right before lingshas rerun.....
Wait fr?
Lemme find a vid to see it
Nopeee, the bug is still there, in the 3.0 beta.
I really fucking hope that the bug fucking fixed in 3.0 live, like actually.
I recently finished my first semester as a comp sci major, so this video was pretty informative to me
6:08 noncrit in the last big hit
Oh my dude ty so much for explaining this bug. I really have no idea what kind of bug is happening that makes my team died faster since 3.0
I hope they really fix this problem cause it's really helpful for me
If like this then every ally need to be better to use linked list of an character class, because probably they will update character property if they have a targetable summon or no, if they have a targetable summon then the linked list reference need to be pushed and add the summoned remembrance stuff to be on the list as a mob object/class or something similar to it
I was questioning if this bug even really existed because I never noticed an issue with my Aventurine since I got him last patch. Now I’m convinced he’ll be literally unstoppable once this is fixed🤷♂️
I missed his rerun, damn, more shield give me more shield
your explaination is very clear that even someone who always failed computer science understands!
I never noticed the bug because my characters never ended up KO'd and seeing so many people complaining confused me😭😭
I legit didn't even realize this was a bug considering my aventurines defense is around 5k so i didn't even notice
While this is a plausible explanation on first pass, this omits the fact that fallen characters have similar property to a 'unsummoned' memosprite. That being they have 0 HP, cannot be selected and cannot obtain buffs (such as Fortified wager). If the flawed logic follows from a check that mistakenly took a 'unsummoned' memosprite, it is more than likely that it could've happen with fallen characters pre-2.7. The bug is MORE likely to be in the code that checks whether a unit is valid to obtain the 'Fortified wager' buff, than the shield value check. Just some thoughts.
Tbf , allies never die when you have aventurine in the team so if the bug occurred when there were fallen allies , almost no one would've noticed
I'm not a coder but wouldn't the variables for mem downs and unit downs be different? Mem downs won't remove the last star in a moc clear, and probably won't trigger death effects like bailu
Wow thanks for the insight- I was wondering why my boothill was dying a lot more easily lmao hope they have it fixed/figured out by 3.0
Reminds me of the neuvilette backlash
man, thanks for this video, my Aventurine was acting strange lately, its shields were weak even when I had the Gepard cone on and the follow ups were barely giving good shields
I couldn't beat the latest boss cuz of the for the longest time. I had to beef up my Jing Yuan and Sunday and still had aventurine in my team since did better but jesus I was wondering why I kept dying in the beginning right when I saw a meme saying he was broken 😭
apology jades, forgiven.
anything for the gamba
Real
oh thats why my feixiao dying so much
thing is i wouldn't care if the trace that got bugged was his crit trace, but no it's his SHIELD trace. he's a sustain, his main job is to sustain, his sustaining capability is bugged and it's gonna take them a whole patch to fix (hopefully not more) like hell nah they better give us a great compensation for this
I feel like it’s still there lol
It hasn’t been fixed yet
honestly the devs are probably stuck between rock and a hard place with a fix:
1) They make it so it checks ALL allies, including summons. This breaks adventurine since it means he'll end up giving shields to the summons, meaning he ends up sucking for any team that has a summon that needs it to take damage, and also sucks for the summoner since he doesn't give them the shield, ever.
2) They make it so it only checks "player" allies, at which point it sucks for summoners because he won't shield the summons.
The bug is probably just pushing them to do more testing to come up with a solution.
It just shows how "summons 2.0" were a stupid idea from the start. If Aven ends up only working properly with a Rmmb char on the team, forever, it will essentially brick him for those who are not interested in playing a Rmmb DPS, and force them to pull another limited sustain cause these days you really need 2.
A bug on a 5 star right before the new region, that's being so Neuvillette/Mualani coded
Well this explains why my Aventurines shield has been failing me, thanks for the great vid. (I didnt even noticed the shield not working properly)
Plot twist:
This is a nerf from Hoyoverse to sell new shielders
..what shielders?
No new shielders are coming in like 5 patches right now
It's not and they'd be stupid to pull a Neuvillette ever again
@@BlueSpaceDustmuch less for an equally beloved and used character. Oh absolutely not. XD
@BlueSpaceDust
Ik ik...
It would be funny tho
I can only imagine they set some value related to the memosprites to '0' to avoid a null pointer exception in Sunday's kit, and that the 3.0 architecture will be more robust.
It tripping up Aventurine was almost certainly just a missed interaction, or ... quite frankly an understood one that was more trouble than it was worth to handle before the entire update is rolled out.
Gods know I've pushed some MVP stuff with similar known 'bugs' in it because we had to account for a future integration that we had no way to reasonably work around in the timeframe we had.
I mean, Hoyo is a multi million dollar company. They are very able to fix things quickly and have proven so multiple times before. So "being lazy" is probably not what's happening...
I will place my bets on 3.0 fixing this issue as you said 👍 thx for the clear explanation abt why could've caused the delay!
Unfortunately being a multi-billion dollar company can slow things down. HSR is a lot of code. Code is easier to fix if it's something small and segregated to one character but if it's in the targetting mechanic in general pushing out a hotfix too fast risks breaking a lot of other stuff. Not to mention the communication. The bigger a dev team or company is, the slower it gets and money can't fix that.
@@deletedflame8424doesn't make sense. Why are they placing in 3.0 mem updates in a version that doesn't need them. They have beta and experiment servers for that, so why roll out an update before the actual patch?
So basically spaghetti code that no one dares to try untangle
A mess of their own creations, remembrance path literally has no purpose at all and only makes them weaker with lc restrictions
They always target the OP male characters and implant secret defects into their kits to make the Waifus look good
using him with fast characters has been an absolute nightmare, you're basically playing sustainless with a sub-dps that shields the slow teammates
Himeko fua bug probably the most annoying one. He fua charge has full 3 charge but only trigger after an ally take action. She was suppose to automatically use fua when the charges is full. It really annoying as himeko is 1.0 character that has no overcap on her fua charges. This bug has been fix before right?
its not a bug, its a feature, if you read her talent it says "if Himeko is fully charged when an ally performs an attack, Himeko immediately performs 1 follow-up attack"
@LucasGomes-ng2go himeko can consistently fua when she break and fully charged without ally attacking. You mean fua without ally attacking is the bug? That kinda weird since there are no overcap on her charges
@zuaer1849 well I don't make the rules, you can read her talent for yourself, it says she'll only do Victory Rush if she has 3 stacks and an ally just attacked
@@LucasGomes-ng2go sorry if i'm sound confrontational. I'm just confused. i'm already know what written on the talent. i always assume it wording problems this whole time.
She consistently fua the moment the charge is full. Even breaking and fully charge with another ally can trigger her fua. this is a convenient bug i guess.
we really do need compensation it's hard to clear endgame content with Aventurine being bugged like this for some people. They would most likely have this bug fixed by v3.0 instead of it being on a separate maintenance
Is it hard😅? I didn't have any problem whatsoever
@ for me not really I have the proper characters tailored for it but it is for other people
3:10 WTF i just pictured a visual studio window with the code to perform that action typed out in my brain, college got me F'ed up
lol i'm not the only one who suspected this too, my first thought when I heard you describing the skill & the context of a backend update was that the ally list is probably looking at shield values for a character/summon entity that doesn't exist.