Switch Theme:

house rules for narrative campaigns  [RSS] Share on facebook Share on Twitter Submit to Reddit
»
Author Message
Advert


Forum adverts like this one are shown to any user who is not logged in. Join us by filling out a tiny 3 field form and you will get your own, free, dakka user account which gives a good range of benefits to you:
  • No adverts like this in the forums anymore.
  • Times and dates in your local timezone.
  • Full tracking of what you have read so you can skip to your first unread post, easily see what has changed since you last logged in, and easily see what is new at a glance.
  • Email notifications for threads you want to watch closely.
  • Being a part of the oldest wargaming community on the net.
If you are already a member then feel free to login now.




Made in be
Dakka Veteran






I am working on a new narrative campaign for my gaming club
We usually have a mix of competitive players, new players, and fluff D&D style players which makes things a bit difficult form time to time...
Some seek out powerful combinations and others want to play fluffy stuff.
I would like to cater to both of them at the same time but favor the fluffy guys more. So really the setting is semi-casual (with competitive undertones)
Last edition we saw Belakor leading skaven in a fortress defense. Fluff explanations as "Grey seer x convinced Archaon to lead his skaven for one battle" etc..
In my opinion fluff is dead if I read stuff like that and I am trying for ways to bring it back without sending the competitive guys packing, and without prohibiting access to powerful models but at the same time limiting the really powerful stuff, but still not killing the spirit of AOS.

So here is a block of rules I am working on, please any advice is welcome:

Don’t be TFG]

To start with I want to explain that this campaign is meant as a semi-casual environment for players that love playing wargames. Although we like games to be competitive, we also like to keep fluff intact and If your idea of a good game is pounding on players with lists that they cannot possibly defend against, or tooling for unbeatable combinations (like spamming, playing net-lists, stuff like neferata + 2 mournguls, or clan skyre engine coven flamer combo etc.) , this campaign might not be for you. Off course if both players decide to bring out the dirt and agree on this beforehand, go ahead, but not on the campaign days or in games where there has not been an agreement of both players beforehand. A deal of common sense in list building is required for this game and the argument “it is allowed” is a cheesy argument that we will not (or no longer) stand for. If you think it will be to dirty, it probably will be to dirty.
So PLEASE, don’t be TFG!

Armielists Campaign.

Rules for matched play as per GHB are in place.

We always use the latest version of a warscroll for a model. This is usually the one found on the GW website, if not available we go to the app or the latest publication we can find.

Only warscrolls with an associated point cost can be used. The same goes for battalions.
All battles are played for a point cost that both players agree on beforehand depending on the battleplan they choose to play. These games can be as big or small as they like. But the fort battle and battles were a commander is present are traditionally big all out battles .

Each player can choose to build his army from one grand alliance with the following restrictions:

A player can choose to use a single race: (ex.Skaven, Aelfs, Duardin, Mortals) and gains access to all models belonging to that race + the models mentioned on one ot the warscrolls of one of the models from that race ( ex Skaven get access to Verminlords, Mortals get access to Daemon princes) He must choose a single hero from this race as his personal incarnation that will play all his battles (This hero may change model but must remain the same character fluff wise ex on horse, not on horse, grey seer with or without screaming bell) This cannot be a model of which you can include only one in your armylist.

Or a player can choose to build a force from a maximum of 4 grand alliance sub factions. In this case the player must play 1 hero from each chosen faction in each game. If this is not possible (like beasts of chaos) he must play 1 unit of that faction in each battle. He must choose one single hero from these factions as his personal incarnation that will play all his battles. (This model can change but must remain the same character ex on horse, not on horse etc) This cannot be a model of which you can include only one in your army list.

This choice is for the entire campaign!

Forgeworld models are not allowed.

Named characters are allowed but you must be able to explain there presence fluff wise. Ex. characters like Archaon, and Nagash etc can be chosen as a faction commander but are unlikely to take orders from another commander or certain other commanders.

Commander

Each faction must choose a commander. This can be any hero and this model must be fully painted and based and displayed during the campaign at the store.

The model must be a suitable (sized) model for the hero in question, and must be WYSIWYG.

Proxies are not allowed for named characters. If you happen to have sculpted the extreme coolest homemade green stuff version of a named character let us know, we might make an exception to this rule

Each faction gains a bonus of 150 pts for battles including there commander.

This model must be from a Grand alliance of one of the players of your faction however he does not need to be from a faction or race from one of the players in the faction. Players gain access to the GA subfaction of the Commander in all the battles where there Commander is present.

The commander must be the army's general when present.

If a commander (model) personally kills another general and you win the battle,you gain a 50 pts bonus to the commander value for the remainder of the campaign.
Battles including the army commander are calculated to be played for 2500 pts (+150 for the side using there commander). For bigger and smaller battles you can make a % mathematical calculation on how many bonus pts the commander should be.


   
Made in us
Clousseau




Cool stuff good luck.
   
Made in us
Stealthy Sanctus Slipping in His Blade





My only advice is don't disallow Forgeworld.

Disallow large monsters from FW, but not the Chaos Dwarves, and smaller beasts (like Wolfrats, Skinwolves etc.).

Otherwise, everything looks fine to me.

PourSpelur wrote:
It's fully within the rules for me to look up your Facebook page, find out your dear Mother Gladys is single, take her on a lovely date, and tell you all the details of our hot, sweaty, animal sex during your psychic phase.
I mean, fifty bucks is on the line.
There's no rule that says I can't.
Hive Fleet Hercual - 6760pts
Hazaak Dynasty - 3400 pts
Seraphon - 4600pts
 
   
Made in us
Clousseau




Yeah I missed that one. Removing forge world would be an instant not interested from me. Granted, I'm not in your campaign anyway so take that for what its worth.
   
Made in be
Dakka Veteran






the forgeworld ban is intended to protect new and unexperienced players from some of the mad stuff around (like casting 18" movement on any model, or some of the dirty monsters like mourngull)

We always have some young players that just bought 2 start collect boxes and play with that and we don't want to scare them away.

Maybe I should change it to Forgeworld is ok, but only if both players agree on it beforehand.

That way I cater both worlds. I don't prohibit, but just say, check who you are playing before you bring the hard and expensive stuff... People who have forgeworld stuff tend to have enough of non-forgeworld to, to comply with this

This message was edited 1 time. Last update was at 2017/02/25 22:07:12


 
   
Made in us
Clousseau




How are you going to protect them from some of the core stuff thats running around thats pretty dirty?

I get what you're saying and you're right those things will scare people away but those same people also have to deal with skyrefire lists, kunnin ruk lists, the storn horn spamming mortal wounds lists, stormcast that dump out shed loads of mortal wounds, etc.

Those things above are pretty dirty too and core to the game.
   
Made in be
Dakka Veteran






 auticus wrote:
How are you going to protect them from some of the core stuff thats running around thats pretty dirty?

I get what you're saying and you're right those things will scare people away but those same people also have to deal with skyrefire lists, kunnin ruk lists, the storn horn spamming mortal wounds lists, stormcast that dump out shed loads of mortal wounds, etc.

Those things above are pretty dirty too and core to the game.


That is what that disclaimer about Don't be TFG is all about. So basically we are asking people not to play that kind of stuff unless both players agree on it beforehand. I try to create an atmosphere of "adapt to your opponents level" kind of thing... But I am still looking for ways to define where the thin line lies between okay competitive play and cheese...
   
Made in us
Clousseau




Understand that too. Its a hard line for some people to cross.

But you could also apply that with forgeworld, since most forgeworld is perfectly fine or even quite frankly underpowered.
   
Made in be
Dakka Veteran






 auticus wrote:
Understand that too. Its a hard line for some people to cross.

But you could also apply that with forgeworld, since most forgeworld is perfectly fine or even quite frankly underpowered.


Yes maybe not a bad idea. The problem in my playing group is that the people that own FW stuff are the powerplayers and they do not own underpowered stuff. So it was more of a double insurance there... But you are right that I should add FW and how to use FW in the disclaimer and not ban it entirely. I was shooting a mosquito with a canon
   
 
Forum Index » Warhammer: Age of Sigmar
Go to: