Specialist Arms Forum
Battlefleet Gothic => [BFG] Discussion => Topic started by: afterimagedan on May 09, 2013, 06:29:51 AM
-
Here is the document that the Tyranid committee is submitting here for your approval! Please look through it and ask any questions or make comments here. The committee (not officially elected) was AndrewChristlieb, Bessemer, and myself.
++Tyranid Hive Fleets++ (https://dl.dropboxusercontent.com/u/1596994/BFGR%202/BFGR%20Tyranid%20Hive%20Fleets.pdf)
Please let us know what you think and if you like it, it would be good to be voted on soon. I have personally play-tested it some and I believe Bessemer has as well.
-
:( I sent you the email but never got a reponse. :'(.
Anyway it looks good, :D I was more of not giving so many options but its ok, I may come back to spain in the summer. If soo I will play test as much as I can ;).
I like the fact that you added the leviatan prowder to the vanguard fleet I would even include the carnivores.
just one thing. Now tyranid capital ships can squadron? is what i understand. I like the change but maybe we will have to make sure is not to much ::).
Anyway good work.
-
One minor thing- the Instinctive Behaviour flow chart, 3rd box, lists 60m, not cm. The intention is clear though.
-
The idea about capitols being unable to squadron seems like extra bloat. Their cruisers are so much weaker than the other races it seems designed to hurt their usefulness and you really dont see many cruisers. The fluff behind it makes little sense either as theyre supposedly evolved from smaller forms which squadron together so why would they lose that ability?
60m isnt so bad... ::)
-
Harec, check your messages.
-
One minor thing- the Instinctive Behaviour flow chart, 3rd box, lists 60m, not cm. The intention is clear though.
Fixed. Thanks.
Anyway it looks good, :D I was more of not giving so many options but its ok, I may come back to spain in the summer. If soo I will play test as much as I can ;).
I like the fact that you added the leviatan prowder to the vanguard fleet I would even include the carnivores.
just one thing. Now tyranid capital ships can squadron? is what i understand. I like the change but maybe we will have to make sure is not to much ::).
Anyway good work.
The original rule that doesn't allow for squadroning Tyranid cruisers goes against the Tyranid hive mind lore and swarm mentality. It was also relatively needless.
One reason I think the Carnivore should not be in the Vanguard fleet is that it is supposed to be mainly the smaller scouting and infiltrating ships. Also, the Carnivore fluff seems to indicate that they are mainly in the Hive Fleets and not as much a vanguard type ship.
-
Ok, not tons of feedback. I will put it up for a vote in two days.
-
Just finished reading through it, I think we'll test it here next week, too.
Just two minor points: I'm not sure why is there mention of determining evolution randomly - when is it needed? Did I miss something?
Second thing:
Minor Synapse Node(Ld7, Synapse Range 30cm). . . . . . .+30pts
-Juvenile Hive Ships with a Minor Synapse Node now offer
Synapse with the range of 15cm and may take Hive Mind
ImperativeRe-rolls that may be used for themselves orships/
squadrons intheir synapse range at the following cost:
Hive Mind Imperative(0-2). . . . . . . . . . . . . . . . . . . . . . . . . . . .+15pts
so... 15cm or 30? I'm not sure how to understand this.
Apart from that, great work, guys. Looks like fully playable Nids, at last ;)
-
Iirc you had the option of taking random evolutions for free. Its been a while since we worked on those tho so dont quote me on that!
-
The 15cm is supposed to be 30cm and I forgot to change it! The evolutions originally had a random option but I don't believe it made it free. It may be something beneficial to include for campaign reasons.
-
Fixed the 15cm thing.
-
The random Bio-morphs was added in case you wanted to use it. You paid as normal, it wasn't free. I've used it a few times. Throws some unpredictability into the mix :)
In campaigns, you would roll on the Bio-morph table for refits, according to 2010.
Did we add that?...we suck at proof reading! :'(
-
I could add that in there right from the 2010 faq. That would help clarify the random roll.
-
I think the carnivore maybe should be les expensive, but I will play test it if I can, considering its rules is a little bit weak, not very fast and a close combat especialist. I don't see much synergy on it own abilities.
but >:(what I especialy don't like is the new boarding rules, i prefer the 2dice+1+1 by blast markers rather than just +2. considering this tyranid now are quite worst in close combat and the blast markets rule when you get in contact was really fun.
-
And something I never understod about feeder tentacles,
1,2,3 that number of criticals.
4,5,6 1 point of damage+ a hit a run raid. That is 1 dice or 2?
-
Feeders= 1,2,3 that many hit and run attacks 4,5,6 one auto damage (which has the standard chance to crit) and one hit and run. All hit and runs are 1 die.
What boarding modifiers are you using there?
Nids got choice of 2d6 and ignore blast markers previously. The +2 simplifies that, although I still like +3 to place them above the rest.
-
no no it is +1 and the then blas markers, the diference is that now they don't rtow 2 dice and choose the best, or I cannot find it ;)
-
Feeder tendrils are a bit weird to remember but its an effective way to combine a lance with hit and runs.
As far as boarding goes, I am still most fond of the original boarding rules but I also acknowledge the simplicity of the new ones. Even playing at Adepticon with limited time, I was aware of how much time putting a blast marker for every base contact really takes. That is effectively a +1 for boarding and so replacing it with +1 made it more simple.
The roll 2D6 and pick the highest is nice and makes Tyranids more consistent in boarding but a +1 also makes them consistently better.
The double boarding value needs to be kept because that boosts Tyranid escorts in boarding more than a +1 at times. Keep in mind, if the enemy has higher boarding value, they get plus one. This is more important for encouraging Tyranid escorts to board compared to just giving Tyranids a +1 to boarding.
I am personally willing to go either route. I really like the original boarding rules but I the new ones work too. We can always vote on it.
-
Just a thought on the boarding (why this didn't come up earlier I don't know).
I'm all for the proposed changes, but the following struck me.
Dan, do you remember your earlier proposal? about 'Nids always adding turrets? How about Enemy ships don't add turrets to Boarding value?
The BM from contact was to represent spores attacking the enemy ship IIRC, and the above does the same with less hassle, the enemy's turrets attacking spores on approach, allowing other gribblies to get close attack their target.
This gives Tyranids a boost without going for +3.
Thoughts? Takers?
-
Ouch. Thats a big hit on some ships (BB's CG's some CB's).
-
Hmm, part of me would like to just go back to the original boarding rules, though it is a handful compared to blanked +'s. It is hard to just do away with the blast marker spore rules because there is some strategy to using them. Also, the double boarding value is hard to get rid of because that encourages the tyranid escorts to board and not get left in the dust when the enemy cruiser gets that +1 over you consistently. Also, the 2D6 keep the tyranid boarding pretty consistent without giving them another +1. I don't know, I think we should just not mess with it.
-
A no to that turret idea. ;)
-
A no to that turret idea. ;)
:P :)
Just throwing it out there.
OK so Boarding is the main bone of contention by the looks of it. Would the best way forward be for people to post preferences and go from there?
-
Keep the original.
-
As is, to clarify-
Double boarding value
+2 Racial mod
On the fence on-
+3 Racial. Unprecedented, but if any race gets this, It's Tyranids!
Roll 2D6, pick highest. Makes 'Nids constantly good as Dan points out (or bad if your luck sucks, hand up here :'()
Would prefer forcing your opponents to re-roll their dice. In this case, hordes of tyranids forcing back their opponents.
-
Sorry, I mean the original as in double boarding value, blast marker on B2B, and roll 2D6, pick the highest. I would like to stick with these as the original Armada Tyranids have.
-
If we retain the blastmarker on contact ruling it should be cleaned up a bit to eliminate any confusion about how it works. check out this recent thread http://www.forum.specialist-arms.com/index.php?topic=5388.0
-
Hi guys,
This is a pretty hansome document. A general evolution from the original.
I wish I'd seen it before starting my own Nid fleet list (although I suppose I wasn't influenced). Mine is completely different, as I binned the original and started from scratch(I'll throw it up later when it's ready).
I like the 'age' of the different hive ships but feel that they need better names. Names that sound good without adding hive ship on the end. ;)
Cheers,
RayBHA
-
Thanks Ray! Lots of people worked hard on it. I would love to hear some ideas of names for the hive ships.
Also, where are we with Tyranid boarding? Who wants to return to the original boarding rules? Who wants the +2 and double boarding value? Any other ones? Should we just take a vote on this?
-
Enemy ships treat Tyranid bases as if they were blast markers.
There, fixed.
-
This is a pretty hansome document. A general evolution from the original.
:oA nod from the higher ups! We did something right, then ;)
As for alternate names, they're still going to be HS's regardless of what we call them. i.e. xxx class hive ship. Unless we just want to go battleship/Grand cruiser/cruiser (in "" of course :P).
Anyway, my choices..
Adult- Angrboda
Adolescent- Grendel
Juvenile- Barghest
A vote on boarding may be the way forward. I take it the options would be..
- Armarda version (pending BM placement clarification of course)
- BFGR as per the doc
- Other-please state
-
According to the FAQ 2010, "The ship only counts as having blast markers in base contact if it ends its movement in base contact with a Tyranid vessel" so this will only count if they are in base to base at the end of the turn, not it they move through. With this in mind, I think your rule will work well Sig, I just think we should word it in a way that doesn't obstruct enemies shooting through them.
We could say "Tyranid vessels count as blast markers while in base to base contact with enemy vessels."
Long time no see Sig. Welcome back! :D
-
Bessemer, I'm not against naming the hives, but I think they should be relatively easy to remember names. I fear that those won't be, unfortunately. Maybe something more simple? Maybe we can use names from the old BFG:R nids list that aren't being used anymore?
-
point made, I do like those kind of names tho ;D
From the original doc we have...
Adolescent-Behemoth, Gorgon, Jormungandr (this one's no easier than mine! :P)
Juvenile- Ghorala, Naga, Ymgarl
Anyone else got some? Or do we just save some time and stick with what we've got?
-
I think your on to something there Sig.
Enemy in contact with Tyranid ship=BM on enemy only. This is good it covers the BM boarding issue and the Nid ship would no longer be forced to sit through the enemy shooting phase -1 shield just because they boarded.
Enemy moves and touches a Tyranid ships base. This would work in exactly the same way except that once again the Tyranid player would not have to sit through an enemy shooting phase -1 shield because someone brushed into them (likely on purpose).
Tyranid players moving into contact with an enemy. The opposite becomes true, enemy ships will not suffer a BM just because the nids brushed against them.
Shooting through Nids. This could be an issue but I don't think it would really, if anything it kind of makes sense if the ship is directly in line with yours and the target those spores cant make targeting any better. This would fit in with the escort drones defending the hive ship also.
-
I think your on to something there Sig.
Enemy in contact with Tyranid ship=BM on enemy only. This is good it covers the BM boarding issue and the Nid ship would no longer be forced to sit through the enemy shooting phase -1 shield just because they boarded.
Enemy moves and touches a Tyranid ships base. This would work in exactly the same way except that once again the Tyranid player would not have to sit through an enemy shooting phase -1 shield because someone brushed into them (likely on purpose).
Exactly. I love how this simplifies everything.
Tyranid players moving into contact with an enemy. The opposite becomes true, enemy ships will not suffer a BM just because the nids brushed against them.
Are you talking about if a Tyranid vessel moves through but doesn't end their turn in contact with the vessel? If that is what you mean then totally agree.
Shooting through Nids. This could be an issue but I don't think it would really, if anything it kind of makes sense if the ship is directly in line with yours and the target those spores cant make targeting any better. This would fit in with the escort drones defending the hive ship also.
I can see that too. Honestly, just making the rule that says that Tyranids' bases count as blast markers that never affect Tyranids simplifies things greatly. It takes the place of the old blast marker rules and you don't have to put down a million blast markers during a game. Excellent!
So, let's adopt this rule, keep the double boarding value and the 2D6 pick the highest from the original. Done.
-
As long as we keep Fire criticals for boarding actions, I'm game!
Pretty sure we agreed about that. Just checking! :)
-
I probably forgot to put that in the doc but that was something the committee agreed on: crits caused in boarding will be fore crits. Andrew had a great explanation of this.
-
In terms of boarding I'd opt for the fewest rules as possible.
Having more hits than the average ship type is a nice method, it also gives better critical repair and ramming.
Certain contact weapons that could be used in addition are nice, such as massive claws and feeder tentacles(neither used in the shooting phase). I've toyed with the idea of having these weapons add a modifier for how many points of damage they cause(but this is like doing double damage, so I dumped it).
Re-rolling the boarding dice(or rolling 2 take the highest) is nice and unique, either this or as a standard boarding modifier. I prefer the former
Having Nid ships count as BMs as Sig suggests is good, although always adding the turrets is good as well. I prefer the later but they are both worthy.
I've never liked double boarding and would rather it wasn't involved. ;D
***In my rules I've made it impossible for Tyranid escorts to initiate boarding actions, instead they'll have to rely on feeder tentacles or massive claws for contact kills. The reasoning behind this is that they aren't biofactories like Hiveships(capitalships) and as such will try to avoid doing something they are unsuited to do. But then I don't have an instinctive behaviour chart in my rules.
Cheers,
RayB HA
-
How about this:
Adult = Colossus
Adolescent = Gorgon
Juvenile = Naga
Also, I propose this for tyranid boarding:
-Tyranid bases count as blast markers when in base to base contact.
-Roll 2D6 and take the highest in boarding.
-Tyranids double their boarding value.
Similar yet a little more simple than the original nid boarding rules due to Sig's mega comeback idea.
-
How about this:
Adult = Colossus Go with that...or Big Mama :)
Adolescent = Gorgon Again, good
Juvenile = Naga Prefer Grendel, as Grendel was the spawn of a monster, not the Big Bad if you get what I mean ;)
Also, I propose this for tyranid boarding:
-Tyranid bases count as blast markers when in base to base contact.
-Roll 2D6 and take the highest in boarding.
-Tyranids double their boarding value.
Looks good!
Any more thoughts or alterations, people?
-
These boarding rules look simple enough, good job!
All seems well right now. I'll try to test the fleet soon.
Also, I support Grendel ;)
-
Anything but Grendel? It makes me think of some big fat bloated baby...
-
Heh, Grendel is cool for a Nid ship.
-
Anything but Grendel? It makes me think of some big fat bloated baby...
Exactly! And what else Juvenile Hive ship is?! :D
-
http://en.wikipedia.org/wiki/Sea_monster#Legendary_sea_monsters (http://en.wikipedia.org/wiki/Sea_monster#Legendary_sea_monsters)
I support anything from that list. If you look, Kraken, Leviathan and Jormungandr are all on the list.
I say Cetus or Scylla
-
I was just writing up a reply to support Scylla when I saw you already mentioned it!
-
I was just writing up a reply to support Scylla when I saw you already mentioned it!
I'm also thinking Proteus would be better for the adult hive. Proteus was the "herdsman of the sea beasts."
Since we are going on the sea monster path, how about this:
Proteus = Adult
Scylla = Adolescent
Hydra = Juvenile
-
As Kraken is already used as both a ship and a hive I don't think duplication is a problem. However keeping them as mythical 'monsters' would be good.
Hydra, Leviathan, Naga and Kraken are all sea or lizard/snake related, I'd probably use them in that order.
Cheers,
RayB HA
-
I think we should avoid using the names of the big 3, Behemoth, Kraken, and Leviathan. Other than that, I am on board with Hydra, judging from my list. Naga is fine with me too.
Proteus = Adult
Scylla = Adolescent
Hydra = Juvenile
Anyone else ok with this list? Want to replace Naga out with any of them? Maybe Proteus, Naga, Hydra?
-
Not so sure about Hydra. It would imply multiple heads that can be removed.
If that is what everyone else goes for, it works, but let me suggest Tursas from the Finnish sea monster Iku-Turso. Maybe have fluff be that they were first noticed in hivefleet Jormungandr to explain another norse name.
-
How about Proteus, Charybdis, and Scylla to keep with greek mythology sea monsters.
-
Was actually going to suggest Chyrabdis!
Wow, there's been more discussion on what things should be called than the rules and lists...That a good thing? :-\
-
I would say yes. :) I am perfectly fine with the current titles either way.
-
Sounds good to me.
-
How about Proteus, Charybdis, and Scylla to keep with greek mythology sea monsters.
Well If Hydra is a problem because of multiple heads then Scylla certainly would be ::). Im cool with these tho, they tie together nicely.
-
Ok! Could use some final proof-reading before we finalize this!
-
Ok! Could use some final proof-reading before we finalize this!
I'll try to do that tonight or tuesday night.
New game of thrones might interfere with tonight.
-
Haha! Yeah, there's that.
-
Proofreading complete.
Interesting that spores were changed to shields/turrets. When I get to the ship list, I make some comments on names. Take them or leave them. Just feedback.
Pg 1
Pg 2
1st paragraph, you forgot hive fleet jormungandr.
Pg 3
1st column, last line
"Swarms, flood across The Tyranids' defenceless"- The should not be capatalized.
2nd Column, THE HIVE MIND. "hive fleet" should be capatalized to follow your formatting convention used throughout.
3rd Column, THE HIVE FLEETS. "as the warship-sized bio construct"- construct should be plural.
Retrenched should be entrenched.
What two categories?
Pg 4
1st Column three main classes are mentioned, but then only 2 main classes are discussed: Hive ships and drone ships. Probably need to make it clearer that you are talking about Proteus as a 3rd type (I think you are).
Fluff piece- 3rd line, career should be careen. Last line, limbs and spare should be swaped to say spare limbs.
Pg 5
Why is hive ship not capitalized?
Why is Command in Command check done with a capital C but check a lowercase c?
Pg 6
Second Column, second line. "androll" missing a space. 4th line "theyir" should be "their". 6th line sentence stating with All requires a space between the period and word All.
3rd Column, second to last line "are additional the the" should be "to the".
Pg 7
Pg 8
Pg 9
Pg 10
Proteus Hive Ship, 4th line- Th refore, missed an e.
Pg 11
Charybdis Hive Ship- The big T at the description start is too low. The Prow weapon table extrection duct line seems off. Keep Weapon Launch Glands verticle table lines messed up. Same with Port/Stbd weapons. For the port/stbd weapon Strengths, I would do 2/2 or 1/1 instead of 2+2 or 1+1. The note at the bottom should say "as such" not "hence" In the fluff piece, I would move the big A to the left a little.
I would call the picture "Leviathan Hive Fleet Hive Ship"
Pg 12
Scylla Hive Ships- Port/Stbd weapons launch glands verticle dividing lines messed up.For the port/stbd weapon Strengths, I would do 2/2 or 1/1 instead of 2+2 or 1+1.
Pg 13
Kraken Carnivore- I might call it Kraken Razorfiend to go with the model's name., or something not Kraken, as to not confuse it with the common kraken.. In the description, 5th line, ants should be lowercase. 4th line from the bottom, last word "creature" should be plural.
Pg 14
Leviathan Prowler- seems like a confusing name, seeing as hive ships are commonly referred to as leviathan hive ships, and even are in this pdf. Maybe just a Prowler Drone, or Prowler Kraken. In the description, vanguard should be lowercase as to not confuse it with the Vanguard ship OR use a different word. Though it seems to be a type on Vanguard. Maybe call it a Vanguard Prowler, and the other one a Vanguard Drone since it is an escort.
The fluff piece was already used on pg 8.
Pg 15
Emergent Drone- Keel weapon launch glands verticle dividing lines messed up.
Pg 16
Predator Kraken- I would call it the Kraken Predator, to follow the naming convention of the Kraken Carnivore.
In the description, 'Ramsmiter Kraken' in quotes, but Deathburner is not, either both should or should not be.
Pg 17
Leviathan Vanguard, may just call it Vanguard Drone, especially if you go with Vanguard Prowler for the Leviathan Prowler.
In the description, Hormagaunts are not an infiltration creature. Leapers more commonly known as Deathleapers.
Pg 18
TYRANID HIVE FLEETS
In the 1st paragraph, Sectors should be lowercase.
Put a space between the word Hive and Ships for the "HIVESHIPS" section. Under hiveships, for the Proteus fleet restrictions, 0-6E mergent Drones. Need a space between the 6 and E and remove the space between the E and m.
Captial Ships- remove the space before Capital and put a space between Capital and Ships.
Minor Synapse Nodes- Still refers to juvenile hive ships. Should be Scylla hive ships. Where it does say Scylla Hive Ships, there needs to be a space between Scylla and Hive.
ESCORTS- There is a random letter F after "Hive Ships"
VANGUARD FLEETS- Need a space between VANGUARD and FLEETS.
GESTATING FLEETS- Need a space between GESTATING and FLEETS. 3rd line from the bottom, of should be or and "Gertating" should be Gestating. Last line, range is missing an e on the end. There seems to be no incentive to play a Gestating Fleet.
The Hive Fleet list fails to allow you to just by ordnance like the original tyranids list did, without a carrier. Is that intentional? Seems like it shouldn't be since you mention anti-bodies in the scenarios.
Pg 19
Cruiser Clash rules, should say they may use one BB and 3 CA or one Charybdis Hiveship and 3 scylla or kraken
-
Thanks! I will get to working on this probably tomorrow.
-
To be fair, Plaxor wrote this, not me.
Proofreading complete.
Interesting that spores were changed to shields/turrets. When I get to the ship list, I make some comments on names. Take them or leave them. Just feedback.
Pg 1
Pg 2
1st paragraph, you forgot hive fleet jormungandr.
There are a whole bunch of hive fleets missed. The three listed are the primary three.
Pg 3
1st column, last line
"Swarms, flood across The Tyranids' defenceless"- The should not be capatalized.
2nd Column, THE HIVE MIND. "hive fleet" should be capatalized to follow your formatting convention used throughout.
3rd Column, THE HIVE FLEETS. "as the warship-sized bio construct"- construct should be plural.
Retrenched should be entrenched.
Actually, retrenched it correct.
What two categories?
Not sure.
Pg 4
1st Column three main classes are mentioned, but then only 2 main classes are discussed: Hive ships and drone ships. Probably need to make it clearer that you are talking about Proteus as a 3rd type (I think you are).
I think the text stands for itself. They are talking about the big huge hives that dwarf battleships so that would basically implicate a Proteus without having to name it.
Fluff piece- 3rd line, career should be careen. Last line, limbs and spare should be swaped to say spare limbs.
Pg 5
Why is hive ship not capitalized?
Why is Command in Command check done with a capital C but check a lowercase c?
Pg 6
Second Column, second line. "androll" missing a space. 4th line "theyir" should be "their". 6th line sentence stating with All requires a space between the period and word All.
3rd Column, second to last line "are additional the the" should be "to the".
Pg 7
Pg 8
Pg 9
Pg 10
Proteus Hive Ship, 4th line- Th refore, missed an e.
Pg 11
Charybdis Hive Ship- The big T at the description start is too low. The Prow weapon table extrection duct line seems off. Keep Weapon Launch Glands verticle table lines messed up. Same with Port/Stbd weapons. For the port/stbd weapon Strengths, I would do 2/2 or 1/1 instead of 2+2 or 1+1. The note at the bottom should say "as such" not "hence" In the fluff piece, I would move the big A to the left a little.
I would call the picture "Leviathan Hive Fleet Hive Ship"
Some of the tables look a little weird when zoomed out because it isn't rendered fully. It's because I often have to add a little white strip to write over old stuff when it's not editable. It will work out when I "print" the final PDFs.
Pg 12
Scylla Hive Ships- Port/Stbd weapons launch glands verticle dividing lines messed up.For the port/stbd weapon Strengths, I would do 2/2 or 1/1 instead of 2+2 or 1+1.
Pg 13
Kraken Carnivore- I might call it Kraken Razorfiend to go with the model's name., or something not Kraken, as to not confuse it with the common kraken.. In the description, 5th line, ants should be lowercase. 4th line from the bottom, last word "creature" should be plural.
It's called a Kraken to indicate that is is a Kraken breed. Kraken breeds have the 4+ save and the 6+ armor thing going on and keeping Kraken in the name helps make that clear. Carnivore is something that has been around for a while. I am not against calling it Kraken Razorfiend but I would like to hear some more support for it before it's changed.
Pg 14
Leviathan Prowler- seems like a confusing name, seeing as hive ships are commonly referred to as leviathan hive ships, and even are in this pdf. Maybe just a Prowler Drone, or Prowler Kraken. In the description, vanguard should be lowercase as to not confuse it with the Vanguard ship OR use a different word. Though it seems to be a type on Vanguard. Maybe call it a Vanguard Prowler, and the other one a Vanguard Drone since it is an escort.
The fluff piece was already used on pg 8.
Changed it to different fluff. Tau for once.
Pg 15
Emergent Drone- Keel weapon launch glands verticle dividing lines messed up.
Pg 16
Predator Kraken- I would call it the Kraken Predator, to follow the naming convention of the Kraken Carnivore.
In the description, 'Ramsmiter Kraken' in quotes, but Deathburner is not, either both should or should not be.
People seemed to want to keep it as Predator Kraken so as to feel encouraged to continue to call it a Kraken for short, not Predator. For the Carnivore, the idea was to put it as Kraken Carnivore so that Carnivore would become the short name.
Pg 17
Leviathan Vanguard, may just call it Vanguard Drone, especially if you go with Vanguard Prowler for the Leviathan Prowler.
In the description, Hormagaunts are not an infiltration creature. Leapers more commonly known as Deathleapers.
True, Hormagaunts are only with Synapse creatures. Fixed.
Pg 18
TYRANID HIVE FLEETS
In the 1st paragraph, Sectors should be lowercase.
Put a space between the word Hive and Ships for the "HIVESHIPS" section. Under hiveships, for the Proteus fleet restrictions, 0-6E mergent Drones. Need a space between the 6 and E and remove the space between the E and m.
Captial Ships- remove the space before Capital and put a space between Capital and Ships.
On occasion, my program messes up the spacing. Thanks for spotting these.
Minor Synapse Nodes- Still refers to juvenile hive ships. Should be Scylla hive ships. Where it does say Scylla Hive Ships, there needs to be a space between Scylla and Hive.
ESCORTS- There is a random letter F after "Hive Ships"
Hehe, yep. That looked pretty ridiculous.
VANGUARD FLEETS- Need a space between VANGUARD and FLEETS.
GESTATING FLEETS- Need a space between GESTATING and FLEETS. 3rd line from the bottom, of should be or and "Gertating" should be Gestating. Last line, range is missing an e on the end. There seems to be no incentive to play a Gestating Fleet.
The Hive Fleet list fails to allow you to just by ordnance like the original tyranids list did, without a carrier. Is that intentional? Seems like it shouldn't be since you mention anti-bodies in the scenarios.
The idea was that you don't really need to buy them separately anymore because of the increased carrier options. If you think they should be there, we could have that discussion.
Pg 19
Cruiser Clash rules, should say they may use one BB and 3 CA or one Charybdis Hiveship and 3 scylla or kraken
I simplified by saying you could instead use 1 Charybdis and 3 cruisers or light cruisers instead.
Thanks for the hard work! Please check it over if you have time.
-
If the large one is going to be Kraken Carnivore, then the small one should be Kraken Predator, not Predator Kraken OR vice versa (Large one Carnivore Kraken). Just to keep the same established naming convention. If they are both kraken breed, it doesn't make sense for one to have kraken 1st in the name and the other second in the name.
-
Anyone else feel that way about the names?
-
If it makes them easier to distinguish, then Kraken (small) and Razorfiend (Big) do fit.
Vanguard Prowler and Vanguard drone also fit well. don't have a problem with any as is tho.
Just realised the vote is up, should I move this there instead?
-
OK, so:
Predator Kraken
Razorfiend Kraken
Vanguard Prowler
Vanguard Drone
???
-
Looks good.
Unless other people don't want razorfiend. The only reason I suggested it was model continuity. But at least the naming convention is consistent for the various kraken. If it ends up being carnivore so be it. Though Razorfiend definately has a certain nid quality to it too.
-
Razorfiend is cool with me. It fits the model too.
-
Razorfiend is cool with me. It fits the model too.
Since it is not longer just a cruiser had has to come with the massive claws, it really fits.
-
Hey,
All good if we call this final or do we need a voting round?
(Operating on Dan's permission here).
-
I thought this had been finalized! :o This is what you get for being off the boards for ages :-[ But when you live in the UK and you actually get a summer, you damn well take it!
Pending any objections I say put it up for a final vote.
-
This seemed to have no objections enough for it to fall by the wayside. I say just call this and Inquisition final.
-
I also thought this was finalized already but I was away for some time too ;)
I'd say, let's call it done.
-
Done! :)
-
Hi all, great work on the whole BFG-R concept. Was just play testing my nids and a minor issue came up regarding Escort Drones. What exactly is their load out of "Mycetic spores", are they supposed to be treated as "phage mines" or something else? 20pts/escort and having 2 mines does not feel right. It also had a tendency to flood the table with mines taking into account the minimum amount of Escort drones per hive ship required.
-
It's a misprint! It should read Hull-borers(ie. Boarding torpedoes w/speed 20cm). We suck at proof reading! :-[
-
Thanks for the update Bessemer, another thing that I noticed that might have already been addressed is the Kraken Carnivore and if it can take the no 6 evolution (+1 shield)?
Its on the verge of being cheesy but is still quite possible as the Carnivore is evolving towards becoming a hive ship.
-
No, it cant take them! It does say that Carnivores "Have no shields" in the description, but we did kind of miss making that more clear. Did I mention we sucked at proof-reading...
Actually, the Carnivore is the grown up version of the Predator. These vessels are a breed apart, solely designed for combat, rather than a stage of development to becoming a full-blown Hiveship. Hope that clears it up. :)
How are you getting on with the BFGR 'Nids so far?