The checkers? No.
Then how will it keep the rank updated for the player?
Because there are multiple checkers.
‘Realizes the whole point of your code’ ooooohhhhhh.
1 Like
All right, I get out of school at 4:15, so I can’t test it now. I’ll just mark solution though. thanks!
1 Like
Uhhh…
last time you did that this happened.
But ok!
You know what, I’ll keep it open just in case!
Hey, @Here_to_help? So I fixed the initial issue, but it’s still spitting out a number instead of a name. Also, it won’t even show the overlay for some reason. I think it’s because the rank is not becoming a word and that would lead to suspicions that your code doesn’t work, or maybe something is interfering with everything. I triple checked the block code, and it’s perfectly fine. I honestly don’t know what the problem is this time. I can’t edit it right now, because I’m on an iPad, and I mess up things when I edit my map on iPads, but I still could use some help figuring this out.
I knew keeping this open was a good decision!
Is this what it’s supposed to look like?
To test it, I set them eliminations needed to 3, and I had a notification set up to where if the check fa1led, it would notify me. On the third elimination, it gave me two notifications. One that said it fa1led, and one that gave me a number, not a name like it should. Anything you see wrong?
There should be two properties. Rank and Rank#. I only see Rank in that picture.
…
‘pauses to think over everything’ There were supposed to be two properties???
Did you look at the block code? There’s two properties in there.
You’re right. I will fix that and try again.
1 Like
The “rank” property is a text property, and the “rank#” property is a number property, right?
Yup. That would be correct.
1 Like
I have a knockout manager that updates a counter. The counter updates the property “rank#”. The property then sends a signal on a channel called “Ranking up!” to the checkers. If the check passes, it sends another signal on a channel called “Rank up!”, which is when the block codes for the notification and overlay activate. Then the player get’s their rank based off of the “rank” property. also, this won’t be in the update, but for testing, if the first checker fails it’s check, it sends a signal on a channel to a notification so that way I know if somethings wrong. Is there anything wrong with how I’m doing this?
That’s not how the rank# should work. That would update the rank# every knockout, not every level up. You need the counters to track the amount of knockouts. I thought you already had that part, which is why I didn’t describe it. The checkers then check the knockouts to see if it’s time to level up. The two properties I gave you should only update in the code I gave you.
That’s what I said.
Each knockout wil update the property by use of the counter.
What are your thoughts?
Edit 3: I tweaked your code a little bit. Since there’s 23 ranks that need calculating because bronze 1 doesn’t need calculating, that’s how I tweaked it. You originally only coded it to calculate 22 ranks to calculate, right? Well, now it’s skipping number 2 of every rank now, which is weird. But at least it’s better than before. Before I tweaked it, it notified me for bronze 2, then silver 1, and then gold 15, which shouldn’t be possible! I think it did that before because it added one number each time and it kept multiplying the number of numbers for each rank. I think that’s because you added the part that said, “set rank to: ‘rank’ +1”. Anyways, what are your thoughts @Here_to_help?
So your saying instead of your system showing names its showing numbers?
No, it’s supposed to show numbers, the problem is that it’s not spitting out the numbers I want. It’s supposed to send out things like, bronze 1-3, silver 1-3, and so on. It’s just that it’s skipping 2. It was definitely better than before though.