Tremayne said: @FindingHeart8 - sorry to hear you have such bad luck. I think I have opened 4 or 5 PP and gotten 3 mythic all different and no Codie. I also had a back to back mythic pull. So you are probably an aberration and within statistical probability - not that you can used that for much.Hope your luck changes for the better soon.
madwren said: A long time ago, I knew someone whose friend in another coalition who dug into the code and shared that there were indeed different weights. First, there are weights for rarity; then within each rarity tear are different weights. For example, Drowner was weighted at 0.25* the weight of other mythics. That's the only one I remember; however, this was during the Hibernum days, so I have no way of knowing whether it's still true.
Volrak said: The data was compelling.I don't recall Hibernum ever denying it (or confirming it).Nobody knows if it stopped years ago or still occurs.
Borg2403 said: For what it's worth. I just tried my luck and opened 10 Strixhaven boosters Zero myhics, ZERO RARES, just about 30 something commons and 20 something uncommons with like 10 doubles already to boot. Maybe 1, 2 max cards seemed playable.Nice waste of 800 crystals.
FindingHeart8 said:Or I am just super lucky/unlucky. I believed that for the first 4 Codies, but at Codie #5 I began to wonder.
I suspect the core content of Hibernum's programming was just built upon, not significantly altered.
Mburn7 said: Hibernium
FindingHeart8 said:Octagon
Volrak said: (And while we're here.. another area where there was continuity was apparently having a company name which is easy for people to get wrong ) Mburn7 said: Hibernium HibernumFindingHeart8 said:Octagon Oktagon
Volrak said: The chance that 6 consecutive STX mythics opened from normal packs are all the same card is about 1 in 12 million (1/26^5). So it is quite remarkable.
critman said: Volrak said:Oktagon absolutely built on Hibernum's product. They began by delivering more content within the same framework, and over time have made improvements to the framework too, but there's never been any doubt that it's remained the same software base. Yeah but would Oktagon even remember to use bits of Hibernum's code that they don't absolutely need to? We know for a fact that Hibernum included some code to stop the AI targeting it's own creatures with destruction spells, all Oktagon have to do is remember to set a flag, but they can never be bothered to...
Volrak said:Oktagon absolutely built on Hibernum's product. They began by delivering more content within the same framework, and over time have made improvements to the framework too, but there's never been any doubt that it's remained the same software base.
jtwood said: critman said: Volrak said:Oktagon absolutely built on Hibernum's product. They began by delivering more content within the same framework, and over time have made improvements to the framework too, but there's never been any doubt that it's remained the same software base. Yeah but would Oktagon even remember to use bits of Hibernum's code that they don't absolutely need to? We know for a fact that Hibernum included some code to stop the AI targeting it's own creatures with destruction spells, all Oktagon have to do is remember to set a flag, but they can never be bothered to... What's the complaint here? That the AI destroys its own creatures incorrectly?
madwren said: jtwood said: critman said: Volrak said:Oktagon absolutely built on Hibernum's product. They began by delivering more content within the same framework, and over time have made improvements to the framework too, but there's never been any doubt that it's remained the same software base. Yeah but would Oktagon even remember to use bits of Hibernum's code that they don't absolutely need to? We know for a fact that Hibernum included some code to stop the AI targeting it's own creatures with destruction spells, all Oktagon have to do is remember to set a flag, but they can never be bothered to... What's the complaint here? That the AI destroys its own creatures incorrectly? Yes, this has been an ongoing issue for pretty much the length of the game. I've benefited from it, but it also makes me a little sad every time it happens. I've posited that's why Oktagon started making the majority of kill spells say "destroy target opponent's creature" instead of just "target creature", as a workaround.
jtwood said: madwren said: jtwood said: critman said: Volrak said:Oktagon absolutely built on Hibernum's product. They began by delivering more content within the same framework, and over time have made improvements to the framework too, but there's never been any doubt that it's remained the same software base. Yeah but would Oktagon even remember to use bits of Hibernum's code that they don't absolutely need to? We know for a fact that Hibernum included some code to stop the AI targeting it's own creatures with destruction spells, all Oktagon have to do is remember to set a flag, but they can never be bothered to... What's the complaint here? That the AI destroys its own creatures incorrectly? Yes, this has been an ongoing issue for pretty much the length of the game. I've benefited from it, but it also makes me a little sad every time it happens. I've posited that's why Oktagon started making the majority of kill spells say "destroy target opponent's creature" instead of just "target creature", as a workaround. They fixed it a while back. For most untargeted kill spells/abilities, Greg won't target his own creature now. Greg will still occasionally do it, but it's mostly with older cards. Cards produced in the last one+ year haven't had this issue with Greg killing his own creatures. For example, Final Death is played fairly frequently, and I've never seen Greg exile his own creature with it, and he never Deathsprouted his own creature (even though that could have helped sometimes). Some other popular kill spells that I never saw Greg hit himself with: Final Payment, Price of Fame, Deadly Visit... Feel free to let me know if your experience differed.
madwren said: jtwood said: madwren said: jtwood said: critman said: Volrak said:Oktagon absolutely built on Hibernum's product. They began by delivering more content within the same framework, and over time have made improvements to the framework too, but there's never been any doubt that it's remained the same software base. Yeah but would Oktagon even remember to use bits of Hibernum's code that they don't absolutely need to? We know for a fact that Hibernum included some code to stop the AI targeting it's own creatures with destruction spells, all Oktagon have to do is remember to set a flag, but they can never be bothered to... What's the complaint here? That the AI destroys its own creatures incorrectly? Yes, this has been an ongoing issue for pretty much the length of the game. I've benefited from it, but it also makes me a little sad every time it happens. I've posited that's why Oktagon started making the majority of kill spells say "destroy target opponent's creature" instead of just "target creature", as a workaround. They fixed it a while back. For most untargeted kill spells/abilities, Greg won't target his own creature now. Greg will still occasionally do it, but it's mostly with older cards. Cards produced in the last one+ year haven't had this issue with Greg killing his own creatures. For example, Final Death is played fairly frequently, and I've never seen Greg exile his own creature with it, and he never Deathsprouted his own creature (even though that could have helped sometimes). Some other popular kill spells that I never saw Greg hit himself with: Final Payment, Price of Fame, Deadly Visit... Feel free to let me know if your experience differed. I disagree. I've definitely seen Greg drag his creatures to the underworld and bake them into a pie during the current Standard environment--and I mean recently.However, you do bring up an interesting point. I haven't noticed this occurring with exile effects, possibly because exile was brought into the game at a later date (and was possibly coded correctly).