BLITZ THE HAMPLIES... WITH YOUR VITSSÅGAR
Morobu sits for a while by the stream-bank, meditating again on ビリヤードボール
, but always keeping an eye on 運がいい
) the Raptorcat. Oddly, the panther, clearly awake, moves neither towards nor away.
After he seems suitably dry, Morobu makes his way, more carefully, towards Lucky
— who still does not move. Only in Japan
, Morobu thinks as he gets close enough to call out.
Morobu stops, bows, and speaks, "あなたとすべての原因に幸 運！
May good fortune befall you and all forces that brought us together!" which is a customary way to greet strangers in the wild.
speaks back. "Thank you, pilgrim — but I fear my fortune has not been so great at all. Rather unmolpish, really."
Morobu now approaches slowly — and sees that Lucky is not alone. There is a small hamply at Lucky's feet! "Oh!"
cries Morobu and jumps back. "— you evil creature! Luring us with your words of poor fortune, but clearly you have been more fortunate than that poor little fluffymolpy!"
"I am quite well in fact," squeaks the hamply — and Morobu is even more surprised, as he thought the little molpy had been caught for breakfast.
"My name is HES
, and I am trying to help Lucky
free from this trap."
balthasar_s wrote: It's all related!
mrob27's browser has a "GLR mode".
Oh yeah, good ol' Global Log Replay mode. That browser was fun to make, and even more fun to use
Seaish congratulations to @MistyCat
jimbobmacdoodle wrote: ... Also enjoying Wait for it., but was sad to miss a large number of frames, including pretty much the entire ending sequence when merging large tiles.
I had a tough time deciding how to deal with that issue. I implemented Wait for it.
when the OTT was on Newpage 1929, and played for about a wip before releasing it to all y'all... but I had been trying to find a good algorithm for displaying the frames for a couple of mips (!) prior to that. Wait for it.
was almost the very first design element of Q04B
from when I first described the 5×7 grid in the early 19th century
The first part of the decision was whether the frames should depend on something like your score, or the number of moves taken, or real (Outside) elapsed time, or something else (the frame changes only when you don't
make a move in the game?). I was also designing the import/export string format, because I knew I wanted the saved game string to be small and easy to reconstruct manually if needed. Since most of those options would require remembering the frame-number separately, lengthening the export string, I ended up choosing the option that does not do so: the Wait for it.
frame is calculated directly from the score and nothing else.
That of course means that you skip lots of frames when you get a big tile (making the score jump up by a big amount). To compensate for that, the formula is sort of like a logarithm function, so when your score is 1,000,000 it takes ten times as many points to get the next frame, as compared to when your score is 100,000. Because the size of the biggest tile is roughly proportional to your score, this means that the most frames you might skip at once is limited to a constant, which turns out to be about 75. That's a lot, particularly when you're near the end of the sequence (which mercifully loops after frame 3087
). Naturally, the formula is set up so that you reach Rosetta when you've nearly reached Rosetta, if you follow me.
The logarithmic function means that it takes a lot more work to get the next frame when you have a higher score: but I had also been testing the Lucky
boost and its augmentations, which automate the process of advancing through the later parts of the game. Anyone who is using Lucky
or its augmentations, is going to miss a lot of frames anyway, so it wouldn't matter if I had taken care to make sure no frames are skipped.
I also realized that a lot of players would be using a strategy like "build towards the bottom edge," where you get well past frame 3087 before creating the Rosetta tile. So those players, though they have to play longer before winning, are rewarded by being able to see the entire rescue of the Forty (with just a few skipped frames here and there).
BlitzGirl wrote: It's tough to herd molpies, especially when they have VITSSÅGAR, JA!
("Sågar" seems to be the plural of "saw" in Swedish, but I'm not certain that's correct.)
It's good enough for me. I've just updated my AUTOMOME
balthasar_s wrote: I tested the multiquote script. Even if I make it work by changing looking for "viewtopic" to "view" it gives "undefined" instead of quoted text. But the mirror is more likely to be used when there is mustard on the OTT, and then quotes dont work anyway.
That was my thinking. But if you'd like me to make some changes to multi-quote
, I'd be glad to — feel free to suggest specific things here (or PM me)
Also why did you test it on newpage -1?
I couldn't remember the URL for the ЯOЯЯIM so I just typed the part I could remember (1190.bicyclesonthemoon
) and allowed autocompleteC
to show me the rest. How did that URL get in my history? Beats me
but I can tell you that the previous OTT-related page I viewed was this post
I had made to the
Sadness discussion. So blame it on the furious doodling.
I kind of like newpage -1, because it's always the latest (at least I think it is). It would be kinda treeish if -2 gave the penultimate newpage, and -3 gave the one before that... but totally pointless too... and really nerdy. For all I know, the fact that /view?np=-1
works at all might be Serendipitous MustardVHF
Ah, found it. On np 1977
I submitted a post before I meant to because I didn't take the time to zoom on the preview/submit buttons. azule didn't know (or had blocked out
) that I have an iPhone, and told me how he avoids doing that on np 1982
. Then it went back and forth a little bit, that's all.
Thanks for looking it up... yes I have that problem too. It's really tough to use the phone for posting. Even zooming in to the buttons (to make it easier to "click" the one you want) seems hard because sometimes instead of zooming it "clicks" a button instead. Very mustardy!
I'll give it a
because it's fixable, (at least most of the time, in theory) by hitting Edit, copying all your BBcode, save it on the Notepad or somewhere, then immediately use the Back button (to Cancel your edit) then use the little red "X" (Delete) button to delete your post.
Anyway — really great live commentary on the M-TzQTI
! I read it aloud for maximum effect
for the link to the SpaceX launch (though they scrubbed it and will try again tomorrip). And no, there were no people in the space car, unless six ORBCOMM OG2 satellites
count as people
AluisioASG wrote: Um, no. Array.prototype.forEach is standard (ES5 I think). Array.forEach is not.
I believe you, and I see that Array.forEach
is some kind of nonstandard shorthand. But the pages I found, like this one
, seem to live in a mythical world where "Array.forEach gets a 'yes' for all browsers except IE8."
and "Array.forEach is now supported by around 70% of desktop browsers."
That should be good enough. I shouldn't have to assume that they are lying
's animation rate was slowed a bit, because the slower browsers were crying for mercy.C
Not to be confused with autocorrect, or with molpy correct. Ch*rp You Molpycorrect!VHF
"Serendipitous Mustard" can be heard on the Ottapalooza
bootleg, a famous live performance by Vital Hotdog Function, from the early days when they still had that Hill People drummer and fans were allowed to build sandcastles in the mosh pit.