Scripting requests

An area for discussing new ideas and additions to Oolite.

Moderators: another_commander, winston

User avatar
szaumix
Deadly
Deadly
Posts: 171
Joined: Sun Apr 24, 2022 4:23 am

quick lines of code for parcel and passenger contracts?

Post by szaumix »

I do have a long desired scripting request that feels like it might be a breeze for the js hounds?

I have never been fully satisfied with the parcel and passenger contract prices, and they are my favorite kinds of missions. I've had a look through them a number of times, but my js skills are too poor to find and therefore change them how I think they should be priced.

Basically I want the price to increase much more the more "hot" a passenger or parcel is. That's it, that's the whole request. I have had a look and I don't know which line of code to edit, and even if I found it, I hate (do not really get) js math. Right now there is little (if any?) price bonus for the things that get you assassinated at every witch point. For some reason it only prioritizes based on the *final destination* system, which I find completely irrelevant to the mission.
User avatar
phkb
Impressively Grand Sub-Admiral
Impressively Grand Sub-Admiral
Posts: 4653
Joined: Tue Jan 21, 2014 10:37 pm
Location: Writing more OXPs, because the world needs more OXPs.

Re: Scripting requests

Post by phkb »

Line 370 of the oolite-contracts-passengers.js file reads:

Code: Select all

		passenger.payment += (passenger.risk * 200);
You could make it read something like

Code: Select all

		passenger.payment += (passenger.risk * (passenger.risk >= 2 ? 500 : 200));
Then increase the 500 to whatever suits.

The parcels system is almost identical, but it's on line 359 of oolite-contracts-parcels.js file:

Code: Select all

			parcel.payment += (parcel.risk * 200);
Change that to

Code: Select all

			parcel.payment += (parcel.risk * (parcel.risk >= 2 ? 500 : 200));
Alnivel
Dangerous
Dangerous
Posts: 100
Joined: Fri Jun 10, 2022 7:05 pm

Re: Scripting requests

Post by Alnivel »

Request 1: canAwardEquipment (and maybe even awardEquipment) for "purchase" context
Either new methods for PlayerShip or via a new optional second parameter of existing.

One of the use cases - for custom ship outfitting interfaces: a simple "Recommended for you" page with a list of equipment selected by a script based on the player’s progress/playstyle or a complete replacement of standard F3, with bells and whistles (read - with categories and sorting).


Request 2: Equipment condition script for stations
To allow the station itself to decide what to sell and prices.

"oolite-barred-equipment" requires equipment to have a condition script that supports it, plenty of equipment does not, and even if it would have, you need to enumerate them all.
Setting "equivalent_tech_level" to 0 removes most of the equipment, sure, but then you need to add pseudo-equipment to allow what you need back and it too has pitfalls (like there is no way to check if equipment's conditional script allows you to buy it in this system).


Request 3: Global property/method for accessing the currently running script (or its name)
Use cases - mostly shenanigans with overriding other's methods.


(Rather plist-ing than scripting) Request 4: "script_info_overrides" for ships and equipment
Overriding via "-overrides.plist" replaces value entirely, which is not always what you may want with dictionaries, especially with script_info. Example of use - having something like an Ship Configuration Equipment Weight Overrides.oxz as a managed add-on alongside with own tweaks of script_info in the AddOns folder for other matters.

Order of applying:
1. script_info from "-overrides.plist" replace script_info in shipdata/equipment.plist
2. script_info_overrides from "-overrides.plist" merge with script_info_overrides in shipdata/equipment.plist
3. Merged script_info_overrides applies to script_info
Switeck
---- E L I T E ----
---- E L I T E ----
Posts: 2412
Joined: Mon May 31, 2010 11:11 pm

Scripting request: How did I get here?

Post by Switeck »

Or rather: How did the player's ship get somewhere?

Fortunately, there's built-in scripting features to do this:

this.shipWillEnterWitchspace = function(jump)
{
// where the variable jump returning values of "standard jump", "wormhole", "galactic jump", and "carried"

So...one could code this if-else chain inside that function:

Code: Select all

	if(jump == "wormhole") var JumpType=1
	else if(jump == "galactic") var JumpType=2
	else if(jump == "carried") var JumpType=3
	else var JumpType=0;
...and JumpType would return a value of 0-3 depending on the type of jump.

This also seems to work with:

this.playerStartedJumpCountdown = function (jump)
this.playerWillEnterWitchspace = function(jump)

But there's a problem where I want to use it:

this.shipExitedWitchspace = function(jump)
or
this.playerExitedWitchspace = function(jump)
(jump doesn't work with these!)

...because it's really handy to know what kind of jump was just done, since in the example code above -- its value is LOST when you enter a new system!
Instead you'd need to use a global variable or mission variable (example: missionVariables.murphy_thargoid_drive_driveCounter == 0-5 ), which gets really messy code-wise and bloats savegames:
https://wiki.alioth.net/index.php/Varia ... avaScripts

Also it would be nice to know if the previous jump was a misjump and from what system it started from:

Placing this in the this.playerWillEnterWitchspace function:
PreviousJump = system.ID;

Would return a number from -1 to 255, where -1 is a misjump and 0-255 is the starting system number.
But PreviousJump also needs to be a global or mission variable to work.

So my request is for the core game's scripting:

this.shipExitedWitchspace = function(jump)
this.playerExitedWitchspace = function(jump)

...to return a jump value for type of jump, like these all do:

this.shipWillEnterWitchspace = function(jump)
this.playerStartedJumpCountdown = function (jump)
this.playerWillEnterWitchspace = function(jump)

And for PreviousJump (variable name-choice not being great) to also be something returned by the core game.
User avatar
szaumix
Deadly
Deadly
Posts: 171
Joined: Sun Apr 24, 2022 4:23 am

Re: Scripting requests

Post by szaumix »

*Daily minor request:

I'm running Ngalo's Configuration Populator and I'm looking for some places I can increase trader spawn. I think I just want more traders in my ooniverse, both a more frequent flow in/out if possible AND more spawning initially and overall, maybe 50%-100% more. I want my lanes fuller, I never see them any more since I buffed pirates so hard.

Before I started tinkering and blowing stuff up I figured I'd prod the experts for the line
User avatar
phkb
Impressively Grand Sub-Admiral
Impressively Grand Sub-Admiral
Posts: 4653
Joined: Tue Jan 21, 2014 10:37 pm
Location: Writing more OXPs, because the world needs more OXPs.

Re: Scripting requests

Post by phkb »

Try this:
In the "oolite-populator.js" inside the OXP, there are two different Library settings objects: "this.$LibraryConfig1" and "this.$LibraryConfig2".
Change "this.$LibraryConfig" to look like this:

Code: Select all

	this.$LibraryConfig2 = {
		Name: this.name,
		Display: "System Populator",
		Alive: "$LibraryConfig2",
		SInt: {
			S3: {
				Name: "$groupSizeFactor",
				Def: 1,
				Min: 0,
				Max: 3,
				Desc: "Group size factor for pirate, hunter and assassin packs.",
				Float: true
			},
			S4: {
				Name: "$pirateFrequencyFactor",
				Def: 1,
				Min: 0,
				Max: 2,
				Desc: "Pirate spawn frequency multiplier.",
				Float: true
			},
			S5: {
				Name: "$hunterFrequencyFactor",
				Def: 1,
				Min: 0,
				Max: 2,
				Desc: "Bounty hunter spawn frequency multiplier.",
				Float: true
			},
			S6: {
				Name: "$assassinFrequencyFactor",
				Def: 1,
				Min: 0,
				Max: 2,
				Desc: "Assassin spawn frequency multiplier.",
				Float: true
			},
			S7: {
				Name: "$traderFrequencyFactor",
				Def: 1,
				Min: 0.1,
				Max: 3,
				Desc: "Trader spawn frequency multiplier.",
				Float: true
			},
			Notify: "$saveSettings"
		}
	};
I used "3" for the max, but feel free to adjust as required.
Immediately below this is the point we read Populator settings from missionVariables. Change that code to be:

Code: Select all

	//Read saved settings, if any:
	if (missionVariables.PopulatorSettings)
	{
		var saved = JSON.parse(missionVariables.PopulatorSettings);
		this.$weaponLevelBias = saved.weaponBias;
		this.$skillLevelBias = saved.skillBias;
		this.$skillLevelMaximum = saved.maxSkill;
		this.$groupSizeFactor = saved.groupSize;
		this.$pirateFrequencyFactor = saved.pirateFreq;
		this.$hunterFrequencyFactor = saved.hunterFreq;
		this.$assassinFrequencyFactor = saved.assassinFreq;
		if (saved.hasOwnProperty("traderFreq")) this.$traderFrequencyFactor = saved.traderFreq;
	}
In the "this.$saveSettings" function, change the bit where settings are updated to be:

Code: Select all

		var settings = {
			weaponBias: pop.$weaponLevelBias,
			skillBias: pop.$skillLevelBias,
			maxSkill: pop.$skillLevelMaximum,
			groupSize: pop.$groupSizeFactor,
			pirateFreq: pop.$pirateFrequencyFactor,
			hunterFreq: pop.$hunterFrequencyFactor,
			assassinFreq: pop.$assassinFrequencyFactor,
			traderFreq: pop.$traderFrequencyFactor
		};
That covers all the settings, so you will be able to adjust things via Library.

Now for the actual changes.
In the "this.systemWillPopulate" function, find the part where it's looping through the "locals" array (should be about line 416ff)
Just after the "bad economic match" part add in the following lines (shown below in context)

Code: Select all

		// bad economic match: one every 2 hours if safe
		else
		{
			rate = 60/(120+(trdanger*2));
		}
		
		rate *= this.$traderFrequencyFactor; // MODIFICATION: multiplied by adjustable trader frequency factor

		this.$repopulatorFrequencyIncoming.traderFreighters += rate;
		this.$repopulatorFrequencyOutgoing.traderFreighters += rate;
		freighters += rate;

		second = seconds[i];
		// couriers are non-mirrored
		rate = (20/(10+((14-local.techlevel)*5)))/second.length;
		if (bottleneck)
		{
			couriers *= 1.5; // simulate long-range routes
		}
		rate *= this.$traderFrequencyFactor; // MODIFICATION: multiplied by adjustable trader frequency factor << ADD THIS LINE
		this.$repopulatorFrequencyIncoming.traderCouriers += rate;
		couriers += rate;
		// smugglers are non-mirrored
		rate = (20/(10+(local.techlevel*5)))/second.length;
		rate *= this.$traderFrequencyFactor; // MODIFICATION: multiplied by adjustable trader frequency factor << ADD THIS LINE
		this.$repopulatorFrequencyIncoming.traderSmugglers += rate;
		smugglers += rate;
	}
	// and outgoing rates for smugglers/couriers. Don't need to
	// specify destination since all rates are equal
	rate = 20/(10+((14-system.info.techlevel)*5));
	rate *= this.$traderFrequencyFactor; // MODIFICATION: multiplied by adjustable trader frequency factor << ADD THIS LINE
	this.$repopulatorFrequencyOutgoing.traderCouriers = rate;
	rate = (20/(10+(system.info.techlevel*5)))/locals.length;
	rate *= this.$traderFrequencyFactor; // MODIFICATION: multiplied by adjustable trader frequency factor << ADD THIS LINE
	this.$repopulatorFrequencyOutgoing.traderSmugglers = rate;
And that should give you adjustable trader spawning.
User avatar
szaumix
Deadly
Deadly
Posts: 171
Joined: Sun Apr 24, 2022 4:23 am

Re: Scripting requests

Post by szaumix »

phkb wrote: Thu Sep 21, 2023 2:23 am
Try this:
Tried these but the populator nuked the system, it was like flying through a ghost system. Checked the log and saw that nothing had spawned but asteroids, the buoy, and the galcop. Checked the in game config and got this:

Image
User avatar
phkb
Impressively Grand Sub-Admiral
Impressively Grand Sub-Admiral
Posts: 4653
Joined: Tue Jan 21, 2014 10:37 pm
Location: Writing more OXPs, because the world needs more OXPs.

Re: Scripting requests

Post by phkb »

Ah, yeah, I missed a spot.

On around line 88 you should see something like this:

Code: Select all

        this.$assassinFrequencyFactor = 1;
Add the following line directly underneath:

Code: Select all

        this.$traderFrequencyFactor = 1;
And see how that goes.
User avatar
szaumix
Deadly
Deadly
Posts: 171
Joined: Sun Apr 24, 2022 4:23 am

Re: Scripting requests

Post by szaumix »

phkb wrote: Fri Sep 22, 2023 11:59 am
Ah, yeah, I missed a spot.

On around line 88 you should see something like this:

Code: Select all

        this.$assassinFrequencyFactor = 1;
Add the following line directly underneath:

Code: Select all

        this.$traderFrequencyFactor = 1;
And see how that goes.
Works! Thanks amigo, as always.
Post Reply