Well, I think "Low", "Medium" and "High" is a good start. But "Backup" would also be good in addition, since I suspect there are several people who already have a game and just want it here as backup when it is cheap ;-)
Since the purpose of this is mostly for gifting others, perhaps you could add as final tag "No gifting", or something like this.

Agreed. And I would really appreciate a tag like "watching" for example to use with day-1-releases, pre-orders and in-dev titles that I want to keep an eye on to see how they will turn out and what reviewers say.

Yeah, that's what I was thinking. No gifting is a good one too.

That's what I was thinking 'Curious' might cover, but Watching is good too. Basically just a reminder to yourself that you were interested in it (and a note to anyone else that while you might appreciate it as a gift it's not a priority just something you might like or aren't decided on)


I'll probably go with a mix of the two then and have 'Low', 'Medium', 'High', 'Backup', 'Watching' and 'No Gifting'.

Second question, should the default for a new item be 'Medium' or should I have a separate tag 'Not Set' (both as a reminder to the user they haven't put a priority on and to other people looking on). I'm leaning towards the second as it would be easy to accidentally leave games on 'Medium' and give the impression you were interested in them to people wishing to gift..

Tough one... I'd probably go with "not set", Amazon's default is "Would be nice" which would translate to medium. From my own experience most of my entries I would consider "low", so that would be the most useful default for me, but most people will probably have other needs.

Yeah I think having them show "Not Set" would be best :-)

I believe that the default for a new wishlisted game should be "Not Set" or "[empty]" or "", which should be taken to mean "not to be kept on your server". So, until someone has selected a specific tag, that game is not to be recorded on your server at all.

Similarly, I believe that when you deploy this new feature, all existing wishlisted games should also be "".

Consensus seems to be Not Set, that makes sense and agrees with my own thoughts to so I'll go with that.

Not sure how feasible not storing the data is. Right now I'm just saving all the data to one array / object locally and then syncing it if it's changed since the last time it was updated. I did consider just sending each game individually as it's changed but that would mean a lot more AJAX calls (and there was another reason that slips my mind now).

I suppose if I don't populate the array with 'Not Set' options and instead just treat an empty setting as 'Not Set' and only actually record it if it is changed.. yes, that would actually work.

But as mentioned I will turn off the syncing feature as well for those who don't want their details recorded (if you have a private wishlist for example) but still allow you to tag things for your own use.

The reason I thought not to transfer it to your server is because there are people with hundreds of games on their wishlist (I know one who has more than 1,000), so it seems quite wasteful to keep hundreds of "not set", just for a handful of set ones.

The space is trivial as it's just JSON so it's text, but I can see what you mean. Thinking about it it's more doable than I'd first realised so I probably will go down that route :)

Either way is fine. It's up to you. If you keep it, MaGog will filter it out.

Speaking of which, is there any way you would prefer the data to be stored for you to use?
Right now I'm using both user IDs and game IDs for keys, but I imagine for users at least it might actually be better for you / MaGoG to use the username?
I assume the IDs would be fine for the games (and I probably can't change that as I'll need it sorted by ID keys, though I can add the game names into the data I store if that would help you).

I would prefer user name and game IDs.

That's what I thought.

I've yet to look at the other side yet (showing the details on people's public wishlists) so I'm not sure whether IDs or usernames are particularly needed on that end.
I imagine usernames should be fine in which case I'll just store the data like that.

Have to try get it finished before the new sale does now.. XD

Would it be possible for you to implement a zoom bar that allows users to control the size and amount of boxes on their shelves, similar to the one Steam uses? It would be nice to be able to make our shelves fill the entire width of our displays and to have the option of having more than five boxes per row.

Yes, probably. When I first implementes the Legacy shelf I had to make the boxes bigger so the right amount would fit on the page. I could probably either shrink the box size or increase the container size (I presume this is what you actually want) so there is less space on the sides on larger screens.