Plan Cache:
- Naruto:
- Let him know that we regularly come up with potentially really stupid ideas and run them by people we trust, because that's part of the process of coming up with good ideas. We included you in reviewing the first draft of our idea because we trust you to call us out when the idea's stupid, which it turned out to be.
- Contact Akatsuki and make it look like their idea. (Already in process?)
- Forbidden Lore.
- Talk to Lee
about adoption.
- Teaching KEI members:
- (Overarching goal: Look for overlooked (due to personality traits, the Academy's biases, etc.) promising students to adopt/apprentice.)
- Coordinate with Kagome on teaching Sealing Theory. Don't teach practical sealing unless Kagome approves.
- Suggest teaching Medicine to Noburi.
- Is Naruto a technique hacker? Would he be willing to teach too?
- Apply for guest lectures at the Academy.
- Look into
Orochimaru's, Bakushin's, and Goemon's notes.
- Convene Goketsu Gaming Mondays. Invite Naruto and KEI specifically.
- Scale up Salterns.
- Clear the land we bought.
- Find, rebuild, and re-key Jiraiya's contacts/network.
- Use guerilla civil engineering as cover.
- Make sure to look into the Yakuza.
Past Major Plans:
Building Something New by faflec
Rocks Fell, Everyone Died by faflec
Compounding Disasters (cont.) by MMKII
Compounding Disasters by faflec
Rules of the Plan Cache:
- Get Support. The Plan Cache is for ideas that already have support of a sizeable chunk of the playerbase, not for ideas that someone wants to advocate later. For a benchmark, your idea should have enough support to be in one of the major plans of a cycle if there was room in the plan.
- Short-term. The Plan Cache is for ideas that we intend to implement in the next few updates, or more loosely within the same rough story arc. If you have an idea beyond that temporal scope, I have another post storing those ideas so ask me to put it there instead of cluttering up our short-term storage.
Sometimes when we're making a plan we have a good idea that's
just outside the temporal scope of the update, but we don't want to cut it from the plan because we might forget by the next cycle. This adds unnecessary words that could have been spent fleshing out the rest of the plan, and may outright cost XP in the worst cases.
This plan cache will hold these subsections so they don't fall into the void between planning cycles. Just ping me with the subsection and, unless it's wildly unreasonable, I'll edit it into the post. I'll keep them there for a while until they either make it into a winning plan, fall out of favour, or the context significantly changes. Depending on circumstances, they might end up in my
Side Project Cache, or they might be dropped, and I'll make sure to be transparent about what I'm doing.
I'll do my best to quote this post after every update, so that planmakers can get an easy reminder about what we never quite got to last cycle.
