namesram (![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
namesram) wrote in ![[community profile]](https://www.dreamwidth.org/img/silk/identity/community.png)
grid_lined_ooc2014-03-14 05:48 pm
namesram) wrote in grid_lined_ooc2014-03-14 05:48 pm
Entry tags:
Event update
Of those who responded to the locked poll about the event, all but one checked the first two options (avalanched by rl/backtagging), while half added "waiting for everyone else". (There was only one vote for "cheese" and "ticky box". I'm surprised at all of you.~)
Given that most people who are currently in the game seem to have a lot of rl and/or threads from last month that they’re still working on resolving, we'll be ending this event early; people can use the next two weeks to backtag, catch up, and play out things that were plotted but they'd had no time for. There’ll still be optional mid-month mini-events posted next week for those seeking something to do. The main thing is to get the pressure off so everyone can finish their backlog of threads comfortably.
A new event will start during the first week of April; Dawn or I will make an IC event-starting post to kick things off. April’s event will be unrelated to this one. The bimonthly character check-in post will also be that week.
After that, unless something changes, the next mod-run Grid-wide event will take place in June, although lesser events and character-driven plots will take place as usual. Since last month's event went really well, and then activity suddenly slowed, Dawn and I have decided to tool the game to its current demographic; after April's event, events will be bimonthly (every two months) instead of monthly. Right now, we're mostly casual players with a lot of rl on our backs. Staying slow for now will allow us all to catch our breath, which seems to be what's needed.
END OF THE EVENT:
The event will end by itself, having taken two days ICly instead of four days. Without warning, every vehicle affected by it will suddenly return to normal (for now).Let's hope they're all in park! If you still want to make an event post, you can until midnight on Saturday night, when I'll post an IC event-end post.
This was not the original plan for resolving the event; it was going to be more character-driven. But with the resolution unknown, it may recur someday when we've revisited its parameters and made it work better.
If any of this is unclear, or if there are any questions, comments are open!
Given that most people who are currently in the game seem to have a lot of rl and/or threads from last month that they’re still working on resolving, we'll be ending this event early; people can use the next two weeks to backtag, catch up, and play out things that were plotted but they'd had no time for. There’ll still be optional mid-month mini-events posted next week for those seeking something to do. The main thing is to get the pressure off so everyone can finish their backlog of threads comfortably.
A new event will start during the first week of April; Dawn or I will make an IC event-starting post to kick things off. April’s event will be unrelated to this one. The bimonthly character check-in post will also be that week.
After that, unless something changes, the next mod-run Grid-wide event will take place in June, although lesser events and character-driven plots will take place as usual. Since last month's event went really well, and then activity suddenly slowed, Dawn and I have decided to tool the game to its current demographic; after April's event, events will be bimonthly (every two months) instead of monthly. Right now, we're mostly casual players with a lot of rl on our backs. Staying slow for now will allow us all to catch our breath, which seems to be what's needed.
END OF THE EVENT:
The event will end by itself, having taken two days ICly instead of four days. Without warning, every vehicle affected by it will suddenly return to normal (for now).
This was not the original plan for resolving the event; it was going to be more character-driven. But with the resolution unknown, it may recur someday when we've revisited its parameters and made it work better.
If any of this is unclear, or if there are any questions, comments are open!