Discussion Additionnal journal requests

Hi guys,

I'm still working on my AI project and I'm realizing that I stumble upon some limitations with the current journal to make it interesting. Here are a few ideas I have in mind :


Targeting objects
Purpose : Exploration mostly and / or passengers mission. Using it to inform the player while he is travelling to a destination. Usefull when you need to clean the cargo bay of your ASPX while flying to your destination.

TargetedObject
When written: When a body or a station has been targeted
Parameters:
. Name: Name of the body.
· BodyType - See appendix 11.7
· DistanceFromArrivalLS

Example:
{ "timestamp":"2016-06-10T14:32:03Z", "event":"targetedobject", "name”:”Earth”, “bodytype”:”earthlike”, “distantfromarrivalls”:”185659” }

TargetedObjectTravel
When written: When a body or a station has been targeted and hasn't been unlocked since then. Event triggered when the lock is maintained for 10 secs and the ship is at full speed.
Parameters:
. Name: Name of the body.
· BodyType - See appendix 11.7
· DistanceFromArrivalLS

Example:
{ "timestamp":"2016-06-10T14:32:03Z", "event":"targetedobjecttravel", "name”:”Earth”, “bodytype”:”earthlike”, “distantfromarrivalls”:”185659” }

TargetedObjectUpdate
When written: When a body or a station has been targeted and hasn’t been unlocked since then. Event triggered when distance is half the initial value of TargetedObject if the initial distance was at least above 5k LS.
Parameters:
. Name: Name of the body.
· BodyType - See appendix 11.7
· DistanceFromArrivalLS

Example:
{ "timestamp":"2016-06-10T14:32:03Z", "event":"targetedobjectupdate", "name”:”Earth”, “bodytype”:”earthlike”, “distantfromarrivalls”:”92843” }


TargetedObjectClose
When written: When a body or a station has been targeted and hasn’t been unlocked since then. Event triggered when distance is under 1K LS
Parameters:
. Name: Name of the body.
· BodyType - See appendix 11.7
· DistanceFromArrivalLS

Example:
{ "timestamp":"2016-06-10T14:32:03Z", "event":"targetedobjectclose", "name”:”Earth”, “bodytype”:”earthlike”, “distantfromarrival”:”985” }


Exploration and refuel
Purpose : Exploration. Using it to inform the player that he has reach the last system in his route where he can refuel and the amount of fuel remaining in percent. I do love the Fuel Rats, but better be safe than sorry.

FSDRefuelLastChance
When written: If the current system in the plotted route is the last where the player can refuel.
Parameters:
· FuelRemaining: int percentage

Example:
{ "timestamp":"2016-06-10T14:32:03Z", "event":"fsdrefuellastchance", "fuelremaining": 50}


Mining
Purpose : Mining. Using it to inform the player of certain events and statuses while he is mining.

LimpetProbingResult
When written: Fired limpet has landed (or not) on a asteroid.
Parameters:
· Success : true or false
· LimpetLife : Time remaining before destruction in seconds
· Distance : Number of meters between the player and the limpet
· AsteroidComposition: Component of the asteroid by %
· Amount of ressources: low, mid, high

Example:
{ "timestamp":"2016-06-10T14:32:03Z", "event":"limpetprobingresult", "success":true, “limpetlife”:”180”, "distance":"3720", "asteroidcomposition”:{ "Painite": 38, "Gold": 12, "Platinum":15 }, "amount": "low" }


RefineryFull
When written: When a limpet try to deliver goods and the refinery is full.
Parameters:
· RefineryFull : true or false

Example:
{ "timestamp":"2016-06-10T14:32:03Z", "event":"refineryfull", "refineryfull":true}


CargoHatchClosed
When written: When a limpet try to deliver goods and the cargo hatch is closed.
Parameters:
· CargoHatchClosed : true or false

Example:
{ "timestamp":"2016-06-10T14:32:03Z", "event":"cargohatchclosed", "cargohatchclosed":true}


LimpetStock
When written: Every 10 limpet used, the player is notified
Parameters:
· NbLimpets : Number of limpet remaning in cargo.

Example:
{ "timestamp":"2016-06-10T14:32:03Z", "event":"limpetstock", "nblimpet":”70” }
{ "timestamp":"2016-06-10T14:35:03Z", "event":"limpetstock", "nblimpet":”60” }
{ "timestamp":"2016-06-10T14:42:03Z", "event":"limpetstock", "nblimpet":”50” }


Combat, Radar and targets
Purpose : Using it to inform the player of incoming targets and signatures in combat or in other situations

NewTarget
When written: When a new target pops on the radar (could be usefull when you mine and need an information when you're focused on your roids)
Parameters:
· Type: ship, other or unknow

Example:
{ "timestamp":"2016-06-10T14:32:03Z", "event":"newtarget", "type": ship}


ThreatsAlert
When written: When at least 3 ships become enemies in less than 5 seconds (usefull when a wing turns against you)
Parameters:
· Number of Threats: int

Example:
{ "timestamp":"2016-06-10T14:32:03Z", "event":"threatsalert", "numberofthreats": 4}


ModuleDamage
When written: When a module lose 10% of total health.
Parameters:
· ModuleName - See appendix 1.2
· HealthPercentage : Number of hitpoints remaining in %

Example:
{ "timestamp":"2016-06-10T14:32:03Z", "event":"moduledamage", "modulename":”thrusters”, “healthpercentage”:”0.50” }


Tell me what you think about these suggestions,
Have a great day commanders and FDev team.
 
Back
Top Bottom