QUOTE (Mordant @ Jul 19 2012, 05:07 PM)
CanRay, I very much enjoyed your work on the Matrix section. It feels very much more like something that I identify with, and is recognizable, while remaining relatively streamlined for play. Condensing numbers is a very good thing, and the programming on the fly fits nicely with making it desirable to be a smart decker rather than simply having skills and a stable of programs and being smart as a brick. There are a couple of points within the chapter that could be clearer, however.
See what I can do.
QUOTE (Mordant @ Jul 19 2012, 05:07 PM)
1) Programming on the fly mentions that you can only improvise one utility of each type per run. Is this meant to be one combat, one masking, etc. or one of each specific utility?
Specific Utility Program, not type.
QUOTE (Mordant @ Jul 19 2012, 05:07 PM)
2) Programming on the fly is not mentioned as taking an action, so I assume that it functions like threadding in that regard, but explicitly without the opportunity to retry, however clarification on this would be appreciated.
Complex Action. I was sure I put that into the list of Matrix Actions... That's the problem when you're over-anal about back-up files, sometimes you save to the back-up by mistake.
QUOTE (Mordant @ Jul 19 2012, 05:07 PM)
3) Since programs cannot be re-improvised, is it possible to load them into Storage s othat you can use another program in the mean time, and then go back to using the improvised code? Or is it one-and-done. Becomes more important because of the seemingly artificial limitation on how often you may improvise.
One-and-done, the code starts falling apart as soon as it's loaded. Think of it as a buggy alpha version, well, actually, it's a buggy pre-alpha version that never gets to alpha to be exact.
Thus the joke: "Error: Program loaded, crash imminent."
This is also to show that it's designed specifically for the system you're currently in, not any other. Also, to prevent Munchkinism.
QUOTE (Mordant @ Jul 19 2012, 05:07 PM)
As has been mentioned, utilities have no costs, and deck upgrades have no costs. Deck upgrading isn't essential to making the game playable, but the other is. Also, I applaud you for adding direct hacking with a program carrier, but it is only ever mentioned in the entry about it, and in certain node types. No gear section entry exists for it for telling us the essence or monetary cost of such a thing. Also, since programming on the fly exists, if there are intended to be any differences from standard programming rules, some mention of that might be good.
I remember specifically asking for it, and seeing it in there. Don't know what happened there, not my chapter, sorry. Not trying to pass the buck, but I did ask.
As for program costs, yeah, my bad.
And, yes, I'm beating myself up over it.
QUOTE (Critias @ Jul 19 2012, 05:43 PM)
I like the cover, but I can empathize with those who have problems with it. (1) I wish they'd included Dodger's ports. (2) I wish they'd had the Dwarf Rigger be either Rabo (their Ork Rigger), or a female (the gal they had later in the series), or just made it Kham, instead of a Rigger at all. (3) I think the lighting effects from Sally's spell are a little overdone. Instead of being dramatic and bold, it just kind of washes color over the whole thing, making the entire cover feel kind of pastel and washed out (if that makes sense). I'm not super-ninja art expert, but I think if it was a little darker, punctuated by a single bright light source, it might look a little sharper.
A lot of folks were asking where Kham was. I joked that he was in the van waiting.