FABFEB ITEMS
FABFEB ITEMS
HOW TO USE:
All fabfeb items require two steps in application:
Firstly, you have to apply the item(s) to the desired breeding via current bank withdrawals LOG: Rockport Bank LOGs
Secondly, when you will get the cubs from the said breeding, you will have to apply desired effects to the chosen cubs via FabFeb current application LOGs: [LINK]
- Also comment as a reply to the litter comment, the item(s) being used and on which ID, ideally this comment should have the link to the Fabfeb log request as well.
Be sure to follow links, provided beneath for every item on RDS-Manager to see the forms that you will have to fill, when applying items to the Breeding.
LIMIT: 1 per breeding, THIS ITEM AFFECTS THE TOTAL AMOUNT OF FABFEB ITEMS ON THE LITTER!
This item limits the total of Fabfeb items on the litter to a Maximum of 3 (including the BluePrint)! (ie 1 Blueprint + 2 Ruby Hearts, or 1 Blueprint +1 Love Letter + 1 Ruby heart)
THIS ITEM ONLY AFFECTS PHYSICAL ASPECTS OF THE CUB:
Coat types, including sphynx coat
Ear types
Fangs/overgrown fangs
Tail types
Body types*: dwarf/standard (Height)
Sabers (Full/half/double)
* Height rolls: one will be rolled for you when you submit the Item update comment to the relevant Fabfeb LOG for data updates.
Please include at the bottom of your comment that: A height roll is needed.
Please see Physical Trait’s Page for detailed information about Mane type restrictions on Build/Blood/Genders.
- When using a blueprint item to transfer such a mane type onto a Male/female cub that fits the build\blood type issue, a fertility issues roll will be applied with the transfer of the physical trait.
- This also works in reverse, if you would apply a blueprint item that would result in a risky combo being changed to a compatible one, any initial fertility issue that was caused by the now removed issue will also be removed.
- Use of other items/combos (such as MGD/GD) will also cause the above effects if that would be the resulting cub.
What can NOT be guaranteed with this item:
Munchkin build or any other build that is linked to sub-species. (Like heavy classic/komainu/baketora etc)
Shortie/Giant/Toy
Specific heights (this is always RNG'd)
Pattern Density (this is always RNG'd)
Special markings such as savoy crescents
Body mutations, caused only by inbreeding: two heads/many tails and other unhealthy oddities, except for overgrown fangs
LIMIT: 1 per breeding
A Fairly straightforward item that boosts the stat point(s) of a single cub. This item is applied by the member to the cub of their choice once the litter is rolled.
- This item grants +5 stat points to be used on any ONE cub from the litter.
- These stat points may be added to a single stat or split in any way across the cubs stats.
Love Letter:
LIMIT: 1 per breeding
- This item allows a single gene to be removed (does not matter if the gene is hetero/homo expression), this will cancel any modifiers linked to that gene. It will cancel full gene, not a separate allele. So if cub, for example ChCh and you are using LoveLetter for "Ch" it will delete both alleles at the same time.
LOVE LETTER APPLICATION EXAMPLES:
USING A LOVE LETTER FOR “ChCh/nCh”
Cub chosen is:
ee/Aa[rr]/tt[c]/nBrn/nStl/ChCh[p]nJ [0]
Peach Champagne Red brown with belly roan, steel shine, and jaguar pattern [0] (Chocolate tan carrier)
Using the item will cause the cub to become:
ee/Aa[rr]/tt[c]/nBrn/nStl/nJ [0]
Red brown with belly roan, steel shine, and jaguar pattern [0] (Chocolate tan carrier)
*note that the whole gene (ChCh) and modifier [p] - peach, have been completely removed.
FOR USE WITH BASE COAT GENES (EE/AA/Aa/aa[**]TT/TT/tt[**]) this will remove any modifiers on that base coat.
Using a Love letter for “AA/Aa”
Cub chosen is:
ee/Aa[rr]/tt[c]/nBrn/nStl/nJ [0]
Red brown with belly roan, steel shine, and jaguar pattern [0] (Chocolate tan carrier)
Using the item will cause the cub to become:
ee/aa/tt[c]/nBrn/nStl/nJ [0]
Black with belly roan, steel shine and jaguar pattern [0] (Chocolate tan carrier)
*note that, while the gene is “removed” as a base coat, cat will still retain the base genes in their most recessive form: ee/aa/tt, but any modifier attached will be removed. This gene cannot be re-added or have a modifier added (such as via Ruby Heart)
- An Exception to this is Pure Djibb blood (93.75%+) cats.
Using a Love Letter to affect the Tan Base (TT/Tt/tt/nT/nt) will result in Tan being replaced with “nn”. As Tan base does not naturally occur in Djibbs.
PATTERNS:
If Parents are:
Bald x Pattern, Love letter will result in Bald cub
If Parents are:
Pattern x Pattern, the cub affected by Love letter will need to be re-rolled for a new pattern! (This includes density)
To request a Love Letter pattern re-roll for a cub, please do the following:
Submit the Item update comment to the relevant Fabfeb LOG for data updates and a new pattern and density will be rolled for you.
LIMIT: 3* per breeding (*Decreased if Blueprint is also on the litter)
- A ruby heart at its core is an item that guarantees a gene from one parent passes to a cub, should that cub not inherit it from that parent.
- Each Ruby heart MUST be for a different gene/Modifier (meaning each of 3 possible hearts should be assigned\used for different genes, not the alleles of the same one)
- Only one copy of a gene can be inherited from each parent by the cub, regardless of what the item is for. This means that if the cub inherits a gene specific to one parent, it cannot have a Ruby heart used to pass an additional copy of that gene.
GENES THAT MUST BE DOMINANT OR HOMOZYGOUS TO SHOW:
- CAN be made homozygous (and/or dominant) with a Ruby heart!
- Can only be made homozygous (and/or dominant) IF BOTH parents posses the gene(s)
IMPORTANT!
- Dominant White: WW CANNOT be made with Ruby Heart!.
In Hetero form nW, the gene is visible, therefore does not require two copies to show.
EXAMPLE: FIGHTING PEACOCK GENE
fpfp / nfp - Fighting peacock is a recessive gene and needs to be homozygous to be visible (needs two alleles present to be visible).
Example 1:
Parent 1 has fpfp Parent 2 does not have any copy of fP at all
Result:
Cub CANNOT be homozygous for fpfp even with a heart, because only one parent is capable of passing a copy to the cub.
Example: 2
Parent 1 has fpfp Parent 2 has nfP
Result:
Cub can possibly be homozygous for fpfp, a Ruby heart CAN be used to pass nfp to ensure
a homozygous fpfp cub!
RUBY HEART AND CHIMERIC\SOMATIC CATS
Each "side" of the geno is treated independently.
A single RH may only effect/be applied to a single side (and follows all the normal rules of the item).
Keep in mind that this is a gamble. As you can not predict which side of the chimeric geno will get involved in cub's genetics. So placing a ruby heart on chimeric cat you might just loose the item!
RUBY HEART AND DJIBB MASK
A Single cat may not have more than Two Djibb masks (this is natural limit and no item will allow to go over it. Exception is a chimeric cat. But this is not relevant for ruby heart application topic)
All cats have two "mask slots".
A Cat can have up to two masks. Adding another mask to a cat with a mask will give the cat two masks.
If the cat already has two masks, adding a new mask will replace one of those masks with the new mask.
Ruby heart cannot remove/replace a mask unless both "mask slots" are filled.
A cat cannot have two of the Same masks on one geno*. (*on a chimera/somatic it is possible to have the same mask on each geno/side)
RUBY HEART AND MODIFIER MUTATIONS
All the genes in brackets that are attached to common genes, like [p] in Champagne (Peach champagne) [M] in Cream (Cream milk) and others, including base coat modifiers [s],[o],[r] etc are considered as separate genes. They require a separate Ruby heart.
For example, to ensure A allele with [o] modifier, you will need two hearts. And as a result you will get a brown cat that is olive brown carrier.
To ensure Ch[p], you would need two hearts to get a Single peach champagne cat (nCh[p])
EXAMPLE 1: MIXED MODIFIERS
We are looking at mixed modifiers of a brown base.
Using a RH on [-r]: Parent 1 has [rs] Parent 2 has [-r] Cub outcomes: [--]/[-r]/[rr]/[-s]/[rs]
RH can be used to make (in order of above possibilities): [-r]/[rr]/no effect/[rs]/[rr]([-s] is replaced/removed.)
THE COMBO EXCEPTION
MODIFIERS THAT REQUIRES HOST GENES TO BE DOMINANT TO SHOW:
PanPan[max], Pan[max]Pan[j], PanPan[j], BrnBrn[max], BB+
A heart can be used to make Pangare or Belly Roan or Siam Dominant IF you are also using another Heart to pass [j] (pangare only) or [Max] or + as well. This is due to these base genes requiring dominant form in order to display their modifier forms!
If parents are PanPan and PanPan[max] (for example) or BB+ and BB you would need just one Heart to ensure [max] or [+] respectively.
Example 1:
RH used for: nPan + [Maxima] - linked to Pangare
Parents are:
Parent 1 (sire): ee/aa/tt/PanPan[maxima]/nRn/nTi
Parent 2 (Dam): ee/Aa/tt/nPan/nRn/nTi
Cub 1:
ee/Aa/tt/nPan/nRn/nTi
Cub 2:
ee/aa/tt/PanPan/nTi
Cub 1 has inherited a single copy of nPan from one of the parents and Cub 2 has inherited a copy of nPan from Each parent.
For this litter, the following options are available:
Add nPan + [Maxima] to Cub 1 to make it:
- ee/Aa/tt/PanPan[Maxima]/nRn/nTi
OR
Add [Maxima] to Cub 2 to make it:
- ee/aa/tt/PanPan[Maxima]/nTi
However, this still leaves the RH for nPan, this cannot be added to Cub 1 because you cannot make a gene Dominant Unless you are also adding the modifier that needs the dominant host to show. The RH for nPan then cannot be used.
Example 2:
RH used for: nPan + [Maxima] - linked to Pangare
Parents are:
Parent 1 (sire): ee/aa/tt/PanPan[maxima]/nRn/nSl
Parent 2 (Dam): ee/Aa/tt/nBrn/nRn/nSl
Cub 1:
ee/Aa/tt/nPan/nBrn/nRn/nSl
Cub 2:
ee/aa/tt/nRn/nSl
Cub 1 has inherited the single copy of nPan from Parent 1 and Cub 2 has inherited no nPan from Parent 1.
For this litter, the following options are available:
Cub 1:
ee/Aa/tt/nPan/nBrn/nRn/nSl
- Neither nPan or [Maxima] can be added to this cub, as it has already inherited the nPan from the parent that has this gene, and the other parent does not have nPan/cannot pass a copy. The[Maxima] cannot be used because it requires Dominant PanPan to attach to.
Cub 2:
ee/aa/tt/nRn/nSl
- nPan Can be added to Cub 2 to make it:
ee/aa/tt/nPan/nRn/nSl
The[Maxima] cannot be used because it requires Dominant PanPan to attach to.
In this breeding, the [Maxima] is wasted as it is impossible for this pairing to make PanPan cubs.
So why was the [Maxima] allowed to be requested?
It is the responsibility of the member to ensure that the items and gene(s) requested are possible with their chosen pairing.
It is the group's responsibility to ensure that either cat in the breeding has the gene(s) being requested, but are not responsible for checking every litter for possible outcomes.
RUBY HEART AND COLOURED PATTERNS AND GENES
nOf-w, nB-r, nR-Wg, nR-C etc
In such genes colour is considered a part of a gene. So you would need only one Heart to ensure it`s passing. In cases with pattern, colour can not be divided from pattern. It will be inherited as is.
You need to apply this item as any other breeding item.
CHOOSING A PATTERN WHEN APPLYING A RUBY HEART
When you use a heart to control a pattern, if cub was rolled with a density, new pattern applied will be the same density.
If the cub you are applying a pattern to does NOT have a density rolled (ie bald), one will be rolled for you when you submit the Item update comment to the relevant Fabfeb LOG for data updates.
Please include at the bottom of your comment that: A pattern density roll is needed.
RUBY HEART AND MODIFIER "+" GENES
nAs/nAs+, nFe/nFe+, nW/nW+, BB[+]*
There are a few gene in game that Extend or modify their base geno.
While you can find Both Acid Spots (nAs) and Asian acid spots (nAs+) on the same cat, these genes are treated as separate genes.
You would only need a single Ruby Heart for nAs or nAs+
ie: when Requesting such genes:
Ruby Heart for: nAs (Acid Spots)
Ruby Heart for: nAs+ (Asian Acid Spots)
Extended Feathers (nFe+), and Extended/Crazy Partial Dominant White (nW+) are treated as Extended versions of their base genes: Feathers (nFe), and Partial Dominant White (nW)
As Such, when using a Ruby Heart , the Base Gene and Extended " + " are treated separately, and would each need their own Ruby Heart.
You need to apply this item as any other breeding item.
ie: when Requesting such genes:
Ruby Heart for: nFe (Feathers)
Ruby Heart for: + - Linked to Feathers
*Extended Siam (BB[+])
- This one Requires that the Base geno be Dominant to show (See THE COMBO EXCEPTION section above).
The Extended modifier [+] requires its own Ruby Heart to pass.
ie: when Requesting such genes:
Ruby Heart for: [+] - Linked to Siam
(Note however; this can ONLY be added to a cub with "BB" and CANNOT be added to a cub that is nB)
NEW GENES OF 2024
2024 introduced us to some new genes that contain “+/-” in the base geno, meaning these are not treated as modifiers on those genes, and only require a single Ruby heart to pass it.
They are as follow:
[Pm-Pm- / nPm-] : Depigmentation
[Pm+Pm+ / nPm+] : Pigmentation
[GhtGht / nGht :] Ghost
[Ght+Ght+ / nGht+] : Superior Ghost
Please note that Depigmentation and Pigmentation are Separate genes, same goes for Ghost and Superior Ghost.
Just like how Confession, Two Coloured Confession and Restricted Confession are different.
EXAMPLES:
ee/Aa/nn/nPm-/nPm+/nGht+/nGht/nApc
Brown with Depigmentation, Pigmentation, Superior Ghost, Ghost and Apple Cheetah Pattern Density
In this breeding, we want to pass Depigmentation, Pigmentation and Superior Ghost
Ruby Heart Requests would be:
Right Way:
Ruby Heart: nPm - : Depigmentation
Ruby Heart: nPm+ : Pigmentation
Ruby Heart: nGht+ : Superior Ghost
Wrong way:
Ruby Heart: nPm : Depigmentation ← missing the -
Ruby Heart: nPm : Pigmentation ← Missing the +
Ruby Heart: nGht : Superior Ghost ← Missing the +, it is now requesting genetically, Ghost (nGht)
Also Wrong:
Ruby heart: nPm : Depigmentation
Ruby Heart: [-] : Linked to Depigmentation
[nPm-] is ONE gene, so it requires only a single Ruby heart to pass [nPm-]
TRICKY EXAMPLES OF RUBY HEART APPLICATION
While the breeding of shedu cats is very complex, and has a variety of things that can pass, or can spontaneously occur, these examples take into account (for item use) only what is possible BASED ON PARENTS GENES.
Dominant versions of a gene may only be made IF a modifier is also being applied to that cub that requires Dom genes as a host, such as BB[+].
Meaning that, if one parent has X gene and the other parent does Not have X, any copy of X that a cub gets, is considered “inherited by the parent that has X”
Whether this is a full gene, a modifier or a color modifier gene!
Example:
As Siam (BB/nB) is one of the most versatile in modifications, we will use this for our example!
BB/nB, [+], [p], Color modifiers
Parent 1 (Sire): ee/aa/Tt/T-nB/nCr/nCh/nPan/nTi [0]
Parent 2 (Dam): ee/Aa/Ta/BB[+]/nBr/nRn/nC [-2]
Ruby Hearts:
T-nB
[+] - linked to Siam (*note that this is only possible on cubs with at least BB)
nPan
Parent 1 (sire): ee/aa/Tt/T-nB/nCr/nCh/nPan/nTi [0]
Parent 2 (Dam): ee/Aa/Tt/BB[+]/nBr/nRn/nC [-2]
NOW, FOR PURPOSES OF INHERITANCE WITH THESE ITEMS, ONLY WHAT THE PARENTS HAVE IS TAKEN INTO ACCOUNT FOR WHAT ITEMS CAN BE APPLIED TO WHICH CUB(S)
Sire is the only parent that has: T-nB, nPan
Dam is the only one with BB[+]
Shared genes: Both parents can pass: nB (sire can pass T-nB or nB) Dam can pass nB
- Therefore, for inheritance, we do not know which parent supplied the nB so it is treated as coming from the opposite parent, so items may be used.
- However, since only the sire has T-nB, any T-nB is treated as coming from him.
- Any [+] on a BB cub is treated as coming from the dam
Cub 1:
ee/aa/TT/nB/nCr/nRn/nC[-3]
Cub 2:
ee/Aa/tt/T-nB/nCh/nBr/nPan/nTi[-1]
Cub 3:
ee/Aa/TT/R-nB/nBr/nPan/nTi[0]
Cub 4
ee/Aa/Tt/BB/nCr/nCh/nBr/nRn/C[+1]
SO, WE HAVE FOUR CUBS, AND THREE RUBY HEARTS TO ADD:
T-nB
[+] - linked to Siam (*note that this is only possible on cubs with at least BB)
nPan
CUB 1:
this cub inherited nB and no nPan
T-nB , nPan, [+]
- ee/aa/TT/nB/nCr/nRn/nC[-3]
It has the following options:
1) Add nPan to make it:
ee/aa/TT/nB/nCr/nRn/nPan/nC[-3]
2) Replace nB with T-nB to make:
- ee/aa/TT/T-nB/nCr/nRn/nC[-3]
*nPan can also be added if desired
3) use both T-nB and [+] to make:
ee/aa/TT/T-BB[+]/nCr/nRn/nC[-3]
*nPan can also be added if desired
CUB 2:
this cub inherited T-nB and nPan
- ee/Aa/tt/T-nB/nCh/nBr/nPan/nTi[-1]
*Because only the sire has T-nB, cub is treated as inheriting that gene from the sire.
It has the following options:
1) None!
- Cub has inherited T-nB from sire, it cannot inherit this gene again.
- Cub has inherited nPan from sire
- Cub is not BB, and thus cannot have [+]
CUB 3:
this cub inherited nB and nPan
*Note that this cub has randomly rolled a Red modifier on the nB gene!
*Ruby heart modifier will overwrite rolled one! (T- replaces R- ) if used.
ee/Aa/TT/R-nB/nBr/nPan/nTi[0]
It has the following options:
1) add T-nB to make it:
ee/Aa/TT/T-nB/nBr/nPan/nTi[0]
- Cub has inherited nPan from sire
2) Add T-nB and [+] to make it:
ee/Aa/TT/T-BB[+]/nBr/nPan/nTi[0]
- Cub has inherited nPan from sire
CUB 4:
this cub inherited BB from both parents, but not T- from sire, so it can inherit:
T- , [+] , nPan
ee/Aa/Tt/BB/nCr/nCh/nBr/nRn/C[+1]
1) Add the T-nB to make:
ee/Aa/Tt/T-BB/nCr/nCh/nBr/nRn/C[+1]
*nPan can also be added if desired
2) Add the T-nB and [+] to make:
ee/Aa/Tt/T-BB[+]/nCr/nCh/nBr/nRn/C[+1]
*nPan can also be added if desired
3) Add the [+] to make:
ee/Aa/Tt/BB[+]/nCr/nCh/nBr/nRn/C[+1]
*nPan can also be added if desired