Even if you don't implement changes it's good to know that you're keeping your options in mind when looking at the publishing schedule ahead.:) To throw in my $.02, I love Starfinder's increased focus on hardcovers over more frequent softcover material like the player companions. But we're not going to,' so many things look unconsidered and monolithic from the outside, despite us reviewing and reconsidering and analyzing on a regular basis. However looking at things and discussing them often can't overcome the factors that caused the original decision to get made, and there's no point in constantly declaring 'We thought about changing something. Very little is done here without some thought (and often a meeting or two) going into it. (Softbacks tend to be more standardized sizes, though we also periodically investigate if those make sense at their current size). We can, of course, make books SMALLER, but no one ever seems to advocate for that. And while we try to build in slack, we NEED that for when some disaster strikes, like play testing discovering a whole subsystem is broken in a very specific way very late in the process. So even if everyone agrees six months before a release date that it's be better if a book was 64 pages longer, the schedule just can't accommodate that without pushing back everything, including products in unrelated lines that have subscribers ex-ecting monthly (or bi-monthly, or quarterly) products. And those dates can't be before the previous books are done, and cannot push back when alter things on the schedule happen 9and there's never just one book going through the pipeline). When scheduling the workflow, we need start and end dates not just for writing, but development, editing, art and map orders, layout, and so on. But what can't change on a dime is things like how big a book is. Usually we're somewhere between those two extremes. But that would be in addition to those lesser options, not in place of. Tectorman wrote: And I'm not saying they wouldn't also be exercising those better options. It's like Bruce Wayne's line about Superman in BvS if there's even a 0.00000001% chance of those factors contributing to stranding them away from help, simple prudence demands that they treat it as a 100% certainty. And remember, an SF ship is only 1d6 days away from Absalom Station IF they have a working Drift drive and IF they have working thrusters for once they get into Drift space and IF they don't get a random encounter along the way. Remember, this is my attempt to provide a rationale for why the ships would be bigger while the crews would be smaller, by saying that the space is taken up by, for example, not the ship's water reclamator and atmospheric reconstitutor, but the fifty water reclamators and seventy atmospheric reconstitutors per person, with spare parts enough to make another few hundred of each (also, per person).

Just that if that's how shields are supposed to work here, recognize that that isn't the traditional depiction and come right out and say that's what it's supposed to look like.Д«ut that would be in addition to those lesser options, not in place of. And I have no problems with that being the conceptual paradigm they're using. So while shields as an intermediary layer between the hull and the armor isn't a TRADITIONAL depiction of how shields work, it's one that is at least within the realm of physical possibility (and it's actually one I've used in writing). The issue with traditional shields is that there's no known mechanism to 'bound' a force field in the way that traditional shields are shown (a 'hard' bubble of force that acts as a second layer of armor). There's nothing actually inherently wrong with that conception. Tectorman wrote.Crosses fingers for an extra page, paragraph, sidebar, or something that gives a satisfactory answer to why shields and armor work they way they do i.e., why your shields don't take damage until after your armor has already failed to do its job despite shields being traditionally envisioned as OUTSIDE and IN FRONT OF the armor. Well done (like a vesk steak) 1 to 5 of 6.

Starfinder armory pdf free download