BASIC 10liners 2017 - Results

Congrats! The sound of OPLL is lovely. I think the multi-statement source code is easy to see because it's unnecessary to scroll.

Thanks, indeed I think the same... Some of the rules were quite odd to me, but maybe there are some reasons I did not get since I've not used all those BASIC dialects.

Ditto

edit- current 'hi'score is 8, had a chance to improve on that, but wasn't paying attention.. Damn!
edit(2) Got 7 now! Though the score seem to be incorrect, because I believe only got 1 or 2 pairs wrong?

edit(3) Again, score of 7, only 1 pair wrong.. (spoiler: there seems to be quite a big chance matching glyphs end up next to each other?)
It seems the score is the sum of all pairs flipped, not only the non-matching?

edit(4) Sorry for busting your balls here.. Clicking a matching pair again apparently adds to the number of correct pairs, when that reaches 6 you cleared the round.. (Though the rules don't say anything regarding the necessity of the game being free of bugs I believe.. )

Well... when you have 4x3 grid they really can't get very far from each other if you think about it. If you look at the source you'll see that I'm not favoring any specific spots, they are selected by MSX-BASIC random number generator that is initialized from time you have used on start of each game... Although this method is not scientifically accurate real random generator and modern operating systems do better, it practically does the job well and is "de facto" standard way to generate random numbers on MSX.

Edit: Well ok, yeah... Because you can place the glyph only to free place, the previously placed glyphs may indeed cause them to be placed closer to each other... but how much the randomness is affected also depends of luck, so I don't think this is anyway statistically very relevant...

Yes... as a tip of the operation it says "Total" and with this I mean indeed "total number of pairs flipped".

Indeed I realized that you can play wrong, but I trusted that people know the rules of "find the pair game" and therefore with little luck I may even get away with it without anyone noticing. :P Unfortunately I could not find small enough check routine to fit in to these 10 lines. ._,

Ah, true... At some point I changed the logic to move few characters from line to another, but it seems that old info was left in to the readme... Well... I must say that I didn't expect this complete testing (Someone actually reads a readme of a "find a pair game" ?) as it is not really that interesting as a game, but anyway always nice to get feedback.

I must say that when you have this tight space limitation you just have to make some quite painful decisions in functionality and polishing... Maybe the subject of the game was not the best, but I'm quite a happy it survived in the competition so well.

NYYRIKKI... I was looking to your basic code and i am really impressed by this. How can it be so small and so cool! I have a lot to learn to achieve this.. Crazy!