Reply To: Magic and Tech: Initial Development

[limburger 21712xp 1]

@royalpain621 there is no way in heck ‘Courier’ is “easy on the inkt”. I think that is a myth from ancient times.

If there are savings to be had they’re likely when printing at the industrial level and not for us amateurs.
You can save a lot more inkt by only printing when you absolutely need it. This is the digital era after all 😉

Anyways …
I didn’t mean that you should limit orks within that squad. I think it’s much better to have a narrative/historic reason for such a mixed unit to exist. Players will pick whatever works if the point cost doesn’t make it impossible.

It’s usually best answered if there are is racial tension within the setting (classic elves hating dirty orks … ).
I think that as it was used as an example it would be best to keep things simple. Simple units have the added advantage that it makes it easier for players to understand their purpose. Maybe there’s an all-ork unit because these guys tend to be soo much better at close combat, whereas the elves preferred ranged weapons.

I’d suggest starting with a basic “kill everyhting” scenario, introduce the mimimal rules needed and expand bit by bit as you introduce scenarios that require such things as terrain types, reserves and objectives.
The starter sets for Infinity have an interesting set of ‘tutorial’ maps that each introduce an additional feature.
The recent ‘Elder Scrolls’ skirmish game also used a mini campaign format to teach rules & features step by step.

Also note … books that do this tend to be the ‘tutorial’ / ‘quick start’ variants.
The ‘traditional’ format is used by the main rulebook.

In a non-earth setting that had magic I would not expect an UH-60 Black hawk  especially given that the name is tied into Earth history (it is named after an Indian leader according to the Wiki).
Science itself is filled with all sorts of references to the inventors responsible for such things.

Everyone uses Orks and Elves … using your own races makes your game more unique and it prevents getting locked into stereotypes.

//

@davehawes I would advice against using Dropbox (and related services like OneDrive from MS), because they are designed to share documents.
They are not designed with version control in mind (it is a neat extra and not part of the design).

The biggest problem :
There is no real way to determine what the ‘master copy’ is.
I’ve seen people accidentaly delete files because they forgot which machine/account had the original and so dropbox thought it was meant to delete files instead of update …
You don’t want to learn such lessons the hard way.

There may be ways to circumvent that, but it won’t be easy and one wrong configuration could cause a ton of problems when you least expect it.