Some Ideas about Job System

[nickalc]

Here's my ideas.



Assassinate jobs must be changed!!! I'm going to assasinate, why the heck would I wanna come up close, give bullshits, and then get AMBUSHED?

Start the battle away from the target, distance determined by stealth value + 5 (or maybe 6); target's bobyguards should be randomly around; bodyguards move around or stay still randomly every turn, and won't attack until I open fire or the stealth was detected (so NPCs should have stealth attribute as well).


BTW, if forced into battle, like a failed checked encounter, enemies should act first in the first turn regardless the initiatives.
But if I choose to fight willingly in an encounter, it should be determined by the initiatives.
All the killing jobs, assassinate, capture or raid, I should start first regardless the initiatives.

Faction Reputation Based
jobs
Rank 0 (negative to 0 Reputation): Current system, take it or leave it (and come back later to get new job)

Rank 1 (0-20): Every visit gives a random list of 3 Rank 0 jobs (pool size 50) and 2 Rank 1 (pool size 40) jobs

Rank 2 (21-50): A random list of 5 Rank 1 jobs and 3 Rank 2 jobs (pool size 30)

Rank 3 (50-100): A random list of 7 Rank 2 jobs and 4 Rank 3 jobs (pools size 20)

Rank 4 (100-200): A random list of 9 Rank 3 jobs and 5 Rank 4 jobs (pools size 20)


Must complete certain amount of lower rank job to move up, maybe 50 - 40 - 30 - 20.

Instead of 1 XP for all, different rank different XP. Character attribute building should be re-mathed as well.

Different job different rank, a Rank 4 hacker might be Rank 0 killer.



NPCs or NPC squads should also be ranked to fit in the killing jobs.


If you can come up a title system... Some mystery jobs for certain titles on top of rank, yields extra credits, reputation, and heats.
Let's say,
90% of hitting a target for the last 100 shots earns a 'Sharpshooter' title; lose it automatically when hitting rate drops;
90% of previous 50 jobs are delivery type, 'Errand Boy/Girl;' lose it automatically;
fight in every encounter possible and kill everyone in battle in the last 20 encounters;
...
Also, some permenant title for extraordinary accomplishments, such as, complete 1000 killing/hacking/courier/negotiation/threaten jobs, play 1000 hours, plant virus in all Matrix nodes in one hacking session (gotta be extremely lucky), ...

[fallen]

nickalc - I don't understand the "Every visit gives a random list of 3 Rank 0 jobs (pool size 50) and 2 Rank 1 (pool size 40) jobs" notation at all. Can you explain clearly?

[nickalc]

I believe the sizes of job pool for different rank should be different, the higher the rank, the less the jobs.
A lot of people/organizations can pay $100 for running errands in close regions, but it would cost more to deliver to faraway or more dangerous ones. A lot of people can pay $200 to revenge a nobody, but only a selected few can afford to pay for the assassinate of the gang boss, and there aren't many around anyway.
That's why I assume the job pool for Rank 0 has a size of 50, Rank 1 has 40, etc.

Maybe it would be better off if I use alphabets than numbers, Rank A, B, C, D, and E.
Every visit or revisit randomly offer me 3 (minus the amount of jobs I took already) out of the current Rank E job pool which consists of 50 jobs, and 2 (minus number taken) out of the current Rank D job pool which consist of 40 jobs.

Otherwise, offer 3 Rank E and 2 Rank D jobs; not happy, delete, leave; revisit, some new ones.
That's similar to the Age of Pirates, but instead one commission at a time, get more from the current pool.
I like the AoP way that commissions can be depleted. Works should be limited and valuable; say one Rank E job is generated per 12 hours, one Rank D job per day, one Rank C per 2 days, etc.


Then I assume a high level person wouldn't wanna do low level jobs. So, only jobs of his level and one level below is offered.
Right now, I think we should have more than 5 ranks, maybe 10 would be better, Rank SSS, SS, S, A, B, C, D, E, F, and G.

[fallen]

Interesting concept. At the moment, the Connectors are only willing to offer a single job. However, we're are working toward a pool concept, but it is lower priority than many of the other job to-do items. I will take your concepts into mind as we get to the pooling implementation!