Thread:Adnoam/@comment-83.216.95.180-20170823172809/@comment-83.216.95.103-20170829121228

I agree about item storylets. My personal thoughts/preferences would be that each storylet (whatever its source or properties) should have its own page.

I am mindful of the update burden so I'll mention what I am thinking at the moment but I am aware that it might not be practical or feasible without bots, just want to set it out. And then I'll try to come back to this and think about the practicality angle too.

1. Storylet template should have a "Source" parameter. This can be "Pinned" (or "Normal" or something) or "Redirect". Pinned would be the default so that there is no necessity to update the vast majority of existing storylets. If it's Pinned then it can do the usual testing for the location with Universal as the default. If it's Redirect then it won't do this testing but instead it will have the field for where it's been redirected from instead of putting it into the Unlock field like in here for example (the Universal category here is meaningless, for example). Then Redirect can also be used with items. You simply put the relevant item into the Redirect parameter. On very rare occasions a card can be both Pinned and Redirect so maybe we could have Source and Source2 or something.

2. Personally, I would not conflate the Autofire template and Category:Autofire. I appreciate that it doesn't matter what Storynexus backend does for the purpose of the wiki but they mean mechanically completely different things. For Category:Autofire, I would also add a parameter to the Storylet, Card and Autofire templates. I'd call it Urgency but we can call Autofire if you prefer. It would be Normal by default so, again, no need to update the vast majority of storylets, but if it's set to Must then it adds Category:Autofire. Currently this group of cards is sufficiently small (only 23) that I'd be happy to do so manually once the templates are updated. I think doing it as a parameter has several advantages. Firstly, it's a property that's shared across several templates. Secondly, it makes updating easier and more modular. Ironically, I just got a reply from Cash about Light Fingers 11 and he now confirms that the storylet in question should be autofire but *not* must urgency. Clearly for them it's just a flag they tick and untick and so it would be useful to be able to respond to such changes without changing the entire template. Thirdly, there is actually a third urgency level - high. It's not used very much but there are in fact some cards with it in the game - for example, the complications (it means that you always have to draw this card if it's not in your hand but you don't have to play it unlike must urgency).

3. If we can extend the Autofire template to include multiple options then why is it a separate template at all? I was looking through the history of templates and apparently it was created because the Card templare was somehow not usable for some reason. If it's not a problem to have a template without any options then shouldn't we just be using Card and Storylet templates for everything and simply have a parameter flag and a category to identify those without any branches?