Rudolph's presents plugin

[m2marsh]

Nov 30, 2017 7:55:36 GMT -8 Peter said:

You basically have one week from the 25th to open them. Once the new year hits, they become sealed again. Any presents not opened once the new year hits will just remain sealed on the profile until the 25th again.

Perfect!  So I can turn the game off after Jan. 1.  Exactly what I was asking, though I had a hard time phrasing it!

[Peter]

Am thinking of making a small change to the code sometime this week. So look for a possible update.

Am probably going to include an option for you to set specific staff members to have unlimited tokens. This way, sending presents to many members will be a little easier for staff. Right now you only earn additional tokens when posting.

[m2marsh]

Nov 30, 2017 8:02:55 GMT -8 Peter said:

Am thinking of making a small change to the code sometime this week. So look for a possible update.

Am probably going to include an option for you to set specific staff members to have unlimited tokens. This way, sending presents to many members will be a little easier for staff. Right now you only earn additional tokens when posting.

That would be awesome.  I'd also like to suggest that everyone starts out with more than 10 free tokens.  Like maybe 25 or more.  Heck, I'd like to have 50.  It is just so hard to earn new tokens, even if you post a lot.  

I'm sure it would be harder to change the code to make it easier to earn tokens.  But that would be a great alternative to increasing the initial Token pile.

But yeah, if you gave staff unlimited tokens, we could quickly recover from the data loss.

[Peter]

Not sure on my reason for not allowing the amount of starting tokens to be customisable. I'll look into that.

[m2marsh]

You may have been thinking this game is a great way to encourage posting. And if you made it easy, no one would have to post a lot. I LIKE that part of it. But I found a worse case where I had to make 8 posts and then only earned 1 token! That is requiring too much posting IMO. But most of the time you get something after 3 or less posts. But I rarely get more than 2 tokens at a time. I saw by reading that the odds are really bad to get more than 2 or so at a time. Most I got (in 200 gifts sent) was 6 tokens at once.

I'd just loosen it up in general, or make it customizable to some extent.

Super cool that you are thinking about playing with the code!

[Peter]

Yeah, the idea of the plugin was to encourage people to post to get more tokens. I do agree, the chance rate is pretty low, so let's see if we can improve that.

Due to limited time, I won't be able to change too much.

- Unlimited tokens is done for selected staff.
- Starting token amount can now be changed.

I've increased the odds for getting tokens now. I will likely make this customisable in the future.

- 80% chance for 1 token
- 70% chance for 2 tokens
- 60% chance for 3 tokens
- 50% chance for 4 tokens
- 40% chance for 5 tokens
- 10% chance for 8 tokens
- 1% chance for 15 tokens

That should be much better now, compared to what they were before...

- 40% chance for 1 token
- 15% chance for 2 tokens
- 3% chance for 4 tokens
- 0.5% chance for 6 tokens
- 0.1% chance for 10 tokens

How are those odds now?

Edit:

Also just in case you aren't aware.  You can only earn tokens if you have none.  This stops people stockpiling tokens.

[m2marsh]

Awesome! So all I have to do is reinstall the latest version? Is it out there yet? This is so nice of you Peter. It will help us immediately to recover from the data loss.matej, you can disregard my request for a rollback of the key. I don't even know if that was possible anyway. Thank you proboards for your work on this issue for us and all the other forums having plug-in issues.

[m2marsh]

Craig, it is OK with me if you move all the posts from this thread to Peter's thread about this game in the Plugin Library area of Support.


support.proboards.com/thread/605815/rudolphs-presents?page=2&scrollTo=7071436

[Peter]

Nov 30, 2017 8:54:46 GMT -8 m2marsh said:

Awesome! So all I have to do is reinstall the latest version? Is it out there yet? This is so nice of you Peter. It will help us immediately to recover from the data loss.matej , you can disregard my request for a rollback of the key. I don't even know if that was possible anyway. Thank you proboards for your work on this issue for us and all the other forums having plug-in issues.

I'll post in my support thread once it's updated.  I will likely finish it tomorrow at some point then submit it to the library. 

[m2marsh]

Nov 30, 2017 12:01:41 GMT -8 Peter said:

Nov 30, 2017 8:54:46 GMT -8 m2marsh said:

Awesome! So all I have to do is reinstall the latest version? Is it out there yet? This is so nice of you Peter. It will help us immediately to recover from the data loss.matej , you can disregard my request for a rollback of the key. I don't even know if that was possible anyway. Thank you proboards for your work on this issue for us and all the other forums having plug-in issues.

I'll post in my support thread once it's updated.  I will likely finish it tomorrow at some point then submit it to the library. 

Hooray!  I can install without losing the key data that is already there now, right?  Seems like there is usually an option to not override the key.

[Matej]

Nov 30, 2017 7:35:13 GMT -8 Peter said:

Yeah, only 3 presents in that data.

The issue the last few days with the keys that ProBoards has hopefully fixed shouldn't have caused any data loss at all. From my understanding, it was simply a key type issue (meaning super user keys temporarily had an identity crisis). User and Super User keys are pretty much the same apart from the permission side of things.

Did you clear your key data / remove the plugin when the issue was happening?

I'll tag Matej for an official response (or any staff seeing this, I didn't want to tag spam) on the key data, but I'm pretty sure no data would have been lost.

You're spot on with the cause. The super user key thought it was just a user key there due to the changes we are doing for v6.

No data would have been lost as part of it, as it just meant that writing/reading the key was not possible in certain situations. The unfortunate part is that with some settings, the data might have been overridden when a plugin was not able to read the original data, assumed a default state, and then later stored this "new" data.

It was definitely an oversight on our side for that and I take personal responsibility for it and will ensure that it does not happen again.

On the bright side, some of the benefits of the changes will soon also become part of v5, depending on when we actually complete the process. Maybe plugin keys will be accessible from templates directly, not just via JavaScript, who knows...


(Disclaimer: the above is still subject to testing and might not actually make it to the final code, so take it with a grain of salt for now until we can share more)

[Chris]

Nov 30, 2017 17:00:22 GMT -8 Matej said:

Maybe plugin keys will be accessible from templates directly, not just via JavaScript, who knows...


(Disclaimer: the above is still subject to testing and might not actually make it to the final code, so take it with a grain of salt for now until we can share more)