fmcorz / moodle-availability_xp Goto Github PK

Hi,
I'ld be happy to have the possibility to link access restriction by XP or Level with actually spending XP to access an activity.

I would like to give students a mechanism that allows to buy second chances for assignments. An unspent XP account could do the trick. And I like the idea that students can work hard to get another possibility to have a second assignment (in another activity). They might do an extra task or repeat randomized STACK quizzes for practise issues.

Also I think that these points should be local in a course and not global (so you have to practice on this very course instead of farming XP in a course with topics you are already good at).

This idea came to my mind reading the book on specification grading. There was written about giving students tokens to get second chances. However these tokens should be implemented in a LMS and not managed on an extra spread sheet or on paper by teachers.

I came across the credit credit plugins that could be linked to the Level Up! plugin making it possible to earn credits and XP and then spend credits to access activities. But the credits are not local (in a course) but global. (Having local credits would be another possible solution.)

I'm still not totaly sure if it would be better to actually substract the XP directly or have a second account of unspend XP. Spending XP could make your Level drop and someone might not access a helping activity because he does not want to fall back on the leader board or something like that. On the other hand it might encourage students to think twice before investing the points. But that might be the case with the unspend account as well.

Overall I think it would be great being able to invest XP instead of just gathering them and show of. It gives them more value and lets students make their own decisions on what to spend these for. Autonomy is aid to motivate people even further.

Hello,

will this plugin support Moodle 3.3 and 3.5?

Ankit reported that the level was reported as invalid, even though it is not.

Apparently casting the level to in in fillErrors fixes the problem.