Jump to content

Featured Replies

Posted

Here is a new guide for FMRTE.  It covers the core features such as Mass Edit, Search Filters, Wonder Kid Generator, and more.  If you have any feedback and/or suggestions, post them in here.  There are some areas that need further explanations and clarifications.

 

FMRTE Guide.pdf

 

Update: Added Details (Jadedness, Declared for Nation, etc) from the player profile page as well as small tweaks.

  • 2 years later...
  • 6 months later...

Is there a player editing guide on CA, RCA etc.

I'm finding that when I edit a players stats, his progress then massively dips in other areas.  I'm not sure why that is, i'm assuming i'm not balancing the stats properly.  Is there a rule on how to do it?

2 hours ago, AnonEMouse said:

Is there a player editing guide on CA, RCA etc.

I'm finding that when I edit a players stats, his progress then massively dips in other areas.  I'm not sure why that is, i'm assuming i'm not balancing the stats properly.  Is there a rule on how to do it?

 

You'll probably find your answer here

  • 1 year later...
On 10/28/2024 at 3:54 PM, AnonEMouse said:

Is there a player editing guide on CA, RCA etc.

I'm finding that when I edit a players stats, his progress then massively dips in other areas.  I'm not sure why that is, i'm assuming i'm not balancing the stats properly.  Is there a rule on how to do it?

Ok this is going to be very detailed but I hope you can understand it;

Quick recap of what each value is

  • CA (Current Ability): the actual total ability points the game allocates across attributes.

  • RCA (Recommended Current Ability): a calculated estimate of what the CA should be to support the current visible attributes.

  • PA (Potential Ability): the ceiling. The CA can rise with development but never exceed this.

Think of CA as a budget spent, RCA as a budget required, and PA as a budget limit.


Scenario Breakdown: When CA ≠ RCA


1. CA < RCA (CA lower than RCA)

The player’s “budget” is smaller than what his attributes currently cost. His stats are too good for his actual CA.

If PA is much higher than RCA

The player has room to grow because CA is well below PA. The game will try to fill the gap by increasing CA naturally through training and matches. Since his PA is far above both CA and RCA, he can improve quickly. Attributes will hold steady or rise until CA is close to RCA. Once CA and RCA are aligned, he will stabilize and then continue normal progression toward PA.

Result: steady improvement and fast development if his personality and training are good.

If PA is only slightly higher than RCA

There is limited headroom for CA to grow before reaching PA. CA will rise quickly until it approaches PA, often near RCA, and then slow down. Once he reaches or nearly reaches PA, progress halts and he may plateau. Attributes stabilize around their RCA levels, with only small changes afterward.

Result: quick short-term growth followed by a plateau.

If PA is lower than RCA

The player’s visible attributes are too strong for his potential ceiling. The game will reduce his attributes until RCA is close to PA. In this case, he will lose stats until his overall level fits his potential.

Result: attributes regress to fit PA.


2. CA > RCA (CA higher than RCA)

The player’s “budget” is larger than what his attributes currently cost. He is underpowered for his CA.

If PA is much higher than CA

There is room for growth, but since CA is already higher than RCA, the game sees unused ability. The player’s attributes might rise until RCA matches CA, using up the spare CA. If that does not happen, CA may gradually drop toward RCA instead.

Result: small attribute growth or slight CA decrease until balanced.

If PA is only slightly higher than CA

There is very little room for improvement. Because CA is higher than RCA, the player appears weaker than his ability value suggests. The game will reduce CA over time until it matches RCA. This appears as a gradual loss of attributes.

Result: noticeable regression until balance is restored.

If CA > PA

This combination is invalid because the player’s ability exceeds his potential. The game forces CA down to meet PA. Attributes will decline quickly until CA is less than or equal to PA.

Result: sharp decline until corrected.


3. CA ≈ RCA (within 5–10 points)

This is the ideal situation. The player’s ability matches the cost of his attributes. Training, form, and personality now determine progress. He will improve naturally toward PA or decline with age.

Result: stable, realistic development curve.


Summary Table

Situation

PA relative to RCA

What happens

CA < RCA, PA much higher

Plenty of headroom, fast growth

Rapid improvement

CA < RCA, PA slightly higher

Limited room, quick growth then plateau

Stabilizes

CA < RCA, PA lower

Overpowered, stats decline

Regression

CA > RCA, PA much higher

Spare capacity, attributes rise slightly

Mild growth

CA > RCA, PA slightly higher

Limited space, CA falls toward RCA

Slight regression

CA > PA

Invalid, game forces decline

Rapid regression

CA ≈ RCA

Balanced

Normal behaviour


Practical editing guideline

  1. Always check RCA after editing attributes.

  2. Keep CA within 5–10 points of RCA.

  3. Ensure CA is less than or equal to PA.

  4. If you want the player to develop, make sure PA is higher than CA, but do not let RCA exceed both.

Following these rules prevents rebalancing, strange progress patterns, and sudden drops in attributes.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.