Sure, but that's not possible unless the repair requirements (the actual amounts, not the stupid constant 999,999 demand in the market) are actually in a journal message. And they aren't.Sounds like a job for an EDMC plugin.
Sure, but that's not possible unless the repair requirements (the actual amounts, not the stupid constant 999,999 demand in the market) are actually in a journal message. And they aren't.Sounds like a job for an EDMC plugin.
I was talking about:Sure, but that's not possible unless the repair requirements (the actual amounts, not the stupid constant 999,999 demand in the market) are actually in a journal message. And they aren't.
You get a... we're getting tired of typing updates by hand twice a day ...
Docked
event with "StationState": "UnderRepairs"
. If that is followed by aMarketSell
event you can check if the commodity is of the required type and post that to an endpoint (eg Googledoc). This no manual typing is required. It's not perfect but it's semi automatic. Maybe you can even set up an endpoint where the plugin can request station/commodity data.I was talking about:
You get aDocked
event with"StationState": "UnderRepairs"
. If that is followed by a
MarketSell
event you can check if the commodity is of the required type and post that to an endpoint (eg Googledoc). This no manual typing is required. It's not perfect but it's semi automatic. Maybe you can even set up an endpoint where the plugin can request station/commodity data.
There's a table on this page with them all listed:Does anyone have a list of the "Region" to "Region_Localised" values. I know region "$Codex_RegionName_24;" is "Formorian Frontier" (because that is where I am at the moment) but getting all 41 (if I've counted right) codes would take a little more travelling that I'm comfortable with.
Many thank yous to anyone that can point me in the right direction.
There's a table on this page with them all listed:
Galactic regions
Galactic Regions are astrographical subdivisions of the Milky Way galaxy that were established by Universal Cartographics in December 3304 to aid in navigation, exploration, and the organization of Codex discoveries. There are a total of 42 Galactic Regions.[1] The two most important regions...elite-dangerous.fandom.com
Hi guys an' gals
Need a little info again. I'm trying to build some comparison charts of various modules. I'm hoping there is a spread-sheet (or some other e-document) that I can extract the data from rather than entering it by hand. What I'm looking for is a list of all the modules, their attributes (as given in the Journal documentation section 13.11) and their values un-engineered.
As always many thanks for any help in this.
Dobbo
Many thanks.
A program being 32-bit has little or nothing to do with the maximum values available for the variables it uses. Can you just declare a long or uint instead of an int?Alas, the adage "be careful what you wish for" is upon me!
My SRV, with high beam on returns a Flags value of 2217263368 ... which represents bit 31 (srvHighBeam) and a whole raft of other set bits and is obviously greater than 2,147,483,647 the maximum possible 32bit signed integer.
This has caused me a bit of grief when I come to process this value within TARGET script...which is a 32bit program.
Clicker
If it doesn't work you could workaround it by (pseudo code):What I'm currently doing is opening the status.json file, scanning for "Flags:", then reading in the key value as a string.
TARGET has a built in function called 'ieval(alias s){}' which converts text and returns its integer equivalent.
When I get home tonight, I'll see if TARGET allows/recognises 'long', or 'uint'.
if value < 0:
highbeam = True
value = value + 2147483647
value = value + 1
bitwise and
operation:if value < 0:
highbeam = True
value = value & 2147483647
Well, I just read the TARGET script manual and downloaded and looked at the software. Yeah, there's no long or uint data type. The language is pretty crippled.Hi @Vithigar ,
I'm not super conversant in C or C++ which TARGET Script is (loosely) based on...but I'll give that a try.
What I'm currently doing is opening the status.json file, scanning for "Flags:", then reading in the key value as a string.
TARGET has a built in function called 'ieval(alias s){}' which converts text and returns its integer equivalent.
When I get home tonight, I'll see if TARGET allows/recognises 'long', or 'uint'.
In the meantime, when the SRV has High Beam on, the Flags key value returned is a negative integer.
My work around assumes this is a wrap-around, so I set my internal "srvHiBeam" flag, then carry on processing the remainder, thus setting any other flags I'm tracking.
Clicker
While I'm not opposed to this, if this is the intended behavior then I think it would be very helpful if the manual were updated reflect this.Yes, the best way to get it fixed is to leave as it is as it perfectly reflects the BGS effects and faction contribution.