Tracking your Counter Resets

[xItzxWeezie]

Re: Tracking your Counter Resets

Tier: Legendary++
Boards cleared: 105
Rare: 70
SR: 12
UR: 3
Epic: 0
Boost: 8
Enhancement: 12

I dont know whether I should be happy or slightly irritated. I can think of worst resets..oh well. The grind continues...

[CedricFP]

Re: Tracking your Counter Resets

Every pick makes a call back to the server, but even if the board was pre-generated, it still would likely do that. Imagine having a way to read the API calls and know the entire setup of the board. You'd be able to select the Rare/SR/UR/Epic/Legend/Star/Boost every time.

That makes sense, yes. I'm of the belief, though, that each card is a 1/25 probability to be a reset, until you get to the last card, which then becomes 1/1.

That would indicate that each pick calls home to RNG the probability. Otherwise, if not the case, each card calls home to RNG the player received, and not whether or not it is a reset. That could also be the case?

If it is the first, then knowing the API to call home makes no difference, as the RNG is hosted server-side, and is based on probability, rather than presets.

My assumption that the probability doesn't increase the more picks on a board you make stems from the fact that heaps of people complain about getting their reset on the 25th card.

[BeegDawg]

Re: Tracking your Counter Resets

Tier: Legendary++
Boards cleared: 105
Rare: 70
SR: 12
UR: 3
Epic: 0
Boost: 8
Enhancement: 12

I dont know whether I should be happy or slightly irritated. I can think of worst resets..oh well. The grind continues...

I received a +40 to Def to Team as my Legendary reset After 249 Board resets. I am very happy with it.

I would have preferred a dupe to go either + or ++.

I won't count during RC.

[eVizions]

Re: Tracking your Counter Resets

That makes sense, yes. I'm of the belief, though, that each card is a 1/25 probability to be a reset, until you get to the last card, which then becomes 1/1.

That would indicate that each pick calls home to RNG the probability. Otherwise, if not the case, each card calls home to RNG the player received, and not whether or not it is a reset. That could also be the case?

If it is the first, then knowing the API to call home makes no difference, as the RNG is hosted server-side, and is based on probability, rather than presets.

My assumption that the probability doesn't increase the more picks on a board you make stems from the fact that heaps of people complain about getting their reset on the 25th card.

That's possible, but I do think it adjusts based on the number of cards remaining. If I were writing it, I would write a function that is called where you provide it with the following: player tier, reset count and cards remaining (and current energy count, but that's not relevant here). Based off of that, it first uses the remaining card count to determine whether you receive a board clearing (1/n) or common/uncommon card ((n-1)/n). If it's common/uncommon card, it next randomly selects one (possibly using the tier... I've noticed that I get more uncommon cards in higher tiers). If it's a clear card, it first checks your reset count, then uses your tier to generate the odds of the card type, then runs your result based on those odds to get the card tier and, finally, randomly selects a card from that tier. From there it stores the info and hands it back to the client. That's 2-3 random generations per call and nothing that is really resource intensive (other than the db call).

I have no idea what their back-end technology stack looks like, but you could easily have a single box capable of running thousands (or even tens of thousands) of these per second.

[Musubi]

Re: Tracking your Counter Resets

Would it be easier to generate an entire list of 25 cards in order whenever you clear a board, using whatever RNG algorithm they have so instead of calculating a card each query, you generate the entire sequence when you finish the previous board and store a list and with each card pick, you are just asking the server what the next card on the list is.


It's more calculations at once, but only has to be done once, but I don't know if that's preferable.

[SwitchOnefooter]

Re: Tracking your Counter Resets

My board resets between my last two epics. Epic+ tier:



Sent from my iPhone using Tapatalk

[Yonder]

Re: Tracking your Counter Resets

Legendary ++

Reset (C Robert Parish) after 890 games = 128 board resets on avg.
Epics: 3

I'd call this a lucky stretch!

[eVizions]

Re: Tracking your Counter Resets

Would it be easier to generate an entire list of 25 cards in order whenever you clear a board, using whatever RNG algorithm they have so instead of calculating a card each query, you generate the entire sequence when you finish the previous board and store a list and with each card pick, you are just asking the server what the next card on the list is.


It's more calculations at once, but only has to be done once, but I don't know if that's preferable.

It's entirely possible. It's a little more process intensive up front and requires more storage to do it this way, but storage is cheap. As you noted, however, you still have the call to see what card was selected (read), which will also need to save the updates (write), so you really aren't gaining much unless you've got the 2 processes (generating a new board vs. selecting a card) running separately. Also, you are potentially creating overhead that is never used (if you are generating 25 cards and the user selects the clear card first, you've essentially generated 24 cards that are never used). It's definitely a viable solution, but I still think the other way is preferable, at least to me.

[CedricFP]

Re: Tracking your Counter Resets

If it were me I wouldn't pre-generate the board simply for cheating prevention. If each pick itself calls home for RNG, then you don't actually have to implement a verification / double-check process.

If you pre-gen the board and load it, in order to prevent cheating (ie memory editing the card selected or w/e), you'd need to have a call-home anyway.

If you're going to call home on each pick anyway, it makes more sense (to me, a layman with NO programming experience)...

[muc.zephyr]

Re: Tracking your Counter Resets

Latest reset stats:

Tier: Leg++
Boards cleared: 55
Rare: 36
SR: 5
UR: 6
Epic: 0
Boost: 3
Enhancement: 4

Tier: Leg++
Boards cleared: 5
Rare: 2
SR: 2
UR: 0
Epic: 0
Boost: 0
Enhancement: 0

have phun,

zephyr

and now:

Tier: Leg++
Boards cleared: 211 (!!!)
Rare: 131
SR: 24
UR: 10
Epic: 5
Boost: 29
Enhancement: 11

have phun,

zephyr

[eVizions]

Re: Tracking your Counter Resets

If it were me I wouldn't pre-generate the board simply for cheating prevention. If each pick itself calls home for RNG, then you don't actually have to implement a verification / double-check process.

If you pre-gen the board and load it, in order to prevent cheating (ie memory editing the card selected or w/e), you'd need to have a call-home anyway.

If you're going to call home on each pick anyway, it makes more sense (to me, a layman with NO programming experience)...

Right, I think that makes the most sense. You can't send the entire board client-side, otherwise you risk something intercepting that and using it to select the clear card every time. And, since you have to make a call after every pick anyway, it may make more sense to just run the pick logic at that time. There are, however, other factors that go into it. You still need certain logic in there to perform validation and prevent cheating. There are certain parameters that need to be passed in to help with the pick generation (tier, number of cards remaining on the board, etc.). You can't expect those to come from client-side, so that has to happen on the server-side, which adds complexity to each call.

Honestly, you could easily find 2 developers that could architect both solutions and make it work efficiently. That's really the beauty of programming. Sometimes, there are multiple ways to solve the same problem.

[Supah]

Re: Tracking your Counter Resets

Wait... If you change your team up, your counter resets? Fml.

[eVizions]

Re: Tracking your Counter Resets

Wait... If you change your team up, your counter resets? Fml.

No, the only time your counter resets is when you get a reset card of the tier that you're currently in

[fipselinho]

Re: Tracking your Counter Resets

FINALLY leg/leg+ reset after 1665 games



So many useless SR and UR... And only 1 epic

[Supah]

Re: Tracking your Counter Resets

Some Legendary+, mostly Legendary++
First reset: ~250 boards, Legendary +18 Reb +18 Playmaking to team
Second reset 3 boards, Legendary +15 All Stats

Lol, kind of wish I had a dupe, but oh well.

Edit: leg++; 39 boards, derozan