Glaive The colors won’t get randomized again! You’ll keep the same drift. <3 For the new coat, Aberration (which became available at the Altar of Spring once the last spirit was quelled this morning), glitch added in the option to utilize our old color code much like Crystal Catalyst. You can toggle between them in the Manage Pet page! :D
Posted 04/23/20
|
|
I did not notice! That’s so cool! 8D I only noticed the lighted beacons. *u* I have questions. Sorry if this is too early since the event is not technically over. I’m just madly curious. Did the community just happen to leave the north spirit for last by getting the others quelled, or was that pre-scripted? Was the difficulty of the words scaled to make the winter spirit harder to quell? Would the other spirits have had lists we did not see because they were quelled before the others?
Posted 04/23/20
|
|
raus It was not pre-scripted! We had 5 extra words for all of them and then as the spirits went down and we knew which ones would be left, we added more to the word lists from there (we were also constantly re-evaluating how many words needed to be added for each defeat since they were going down pretty quickly). Glitch also had the background coded up to work with whichever order the spirits were defeated! For awhile we were sure that summer was going to be the last one standing. We loved that winter was the last one since it worked well with the lore of the event. :‘D
Posted 04/23/20
|
|
Thanks for the confirmation Myla! I love the colors mine got so I’d be really upset if I messed it up on my end. It’s also interesting to see how the word lists are being updated. Because the word lists for summer and winter were neck-to-neck (they were at 4/5 for the last word at one point if I’m remembering correctly) I was wondering what would have happened if two people sent the last required word for both remaining spirits at the same time.
Posted 04/23/20
|
|
Sorry if I missed it somewhere, but I had a question. Will there be an event forum section or thread? I know sometimes we have a “Give a Word, Get a Word” kind of threads, but I hadn’t seen one yet (and didn’t want to make a duplicate or place it in the wrong section of forum). So was just curious :)
Posted 04/23/20
|
|
Thanks Myla! It’s so cool to see that. I was surprised to see how fast they went down, but wondered like Glaive did what would happen if they both got quelled at the same time.
Posted 04/23/20
|
|
I think they would have had to have gone down the exact same second for it to be an issue, which seemed unlikely unless two people were working in coordination. Even then I think it would have been difficult to do it at the same moment. glitch would need to confirm though. It was a thought that passed through my head too, LOL. Hiiro I think those are usually started by community members! Feel free to start one up in the jibber jabber forum. 8)
Posted 04/23/20
|
|
Myla
Posted 04/23/20, edited 04/23/20
|
|
raus Myla Regarding exact-same-time, that’s a great question! So, it would have been a little trickier than both going down in exactly the same second. It would need to be a lot closer in time than that, so realistically both words would need to come from you (it’d be impossible to coordinate with multiple computers over the internet). So, if you had enough letters for both of their last words at the same time, and then engineered things to ensure they got sent at exactly the same time (there’s tools to help orchestrate this), and if you get lucky with network conditions (from my experimentation on Mycena Cave a while back, two requests sent at the exact same time have a ~20% chance of colliding), then things get interesting if you don’t deal with the possibility explicitly in your code. This is actually a pretty common problem on a lot of websites and services — common enough to have a fun sounding name: they’re called TOCTOU vulnerabilities (pronounced “tock two”, short for Time Of Check To Time Of Use). For example, Starbucks lets you transfer gift card balances from one card to another, and not too long ago it was possible to use this trick to basically get infinite Starbucks money. You start with $5 on card A. Send two requests to transfer $5 from card A to card B at the same time. If they got processed at the same time, then the processing would go as follows:
Repeat this process with a bunch of empty cards, and each one you transfer to you double your money. Note: this is very illegal. The fix for this kind of issue is pretty simple: ensure that (important parts of) your requests are handled atomically. Typically for websites this means implementing things with something called “transactions”. And, in case you’re wondering, yes, once upon a time it was possible to send double your nugget or gem balance to someone else on Mycena Cave, though we found and fixed that before anyone else did :) So… back to your original question, what would have happened if you had sent the words at exactly the same time and gotten lucky? Not a lot. But had we failed to make sending words transactional, the following would have happened:
Posted 04/23/20, edited 04/23/20
|
|
Deliball
Posted 04/24/20
|
|
Heads up that we’ve just noticed that we aren’t able to send words back to at least a couple of players. No one has reported this as an issue, but if you’ve been sending out words and not getting anything back, that could be why. ;o; Glitch is going to look into it when he gets a chance, but it’d be helpful to know if anyone else has run into this!
Posted 04/28/20
|
|