The Feudal States

[RobsterLeal]

But if anyone knows of a fix and would like to talk this old eeejit through the method and how it is done, I'm always willing to learn

[RobsterLeal]

So there appears to be an unfortunate side effect to the 'no market' oxp. If I had any coding skills whatsoever, i would go look see, but i havent

Even if we can't fix it (which means make the OXPs compatible to each other), we can improve the situation to flag them as incompatible.
With that flag set, OoliteStarter would indicate to users the unfortunate combination. It allows users to take educated decisions.

Indeedy. Is there somewhere I do that? bug reporting area or something similar??

[Wildeblood]

But if anyone knows of a fix and would like to talk this old eeejit through the method and how it is done, I'm always willing to learn

Having looked through it earlier this year, I'll opine that it's not phkb's finest work. Nor his second or third finest. Just delete it and forget about it.

[phkb]

Having looked through it earlier this year, I'll opine that it's not phkb's finest work. Nor his second or third finest.

Yeah, cheers mate.

The problem, as I see it, is that Feudal States is subverting the use of a standard function, in this case, the F8 key. Under certain circumstances, pressing F8 when docked at a Feudal Hunting Lodge or a surface location, will trigger specific mission screens. That's not the fault of "No Market Notification" - that's a poor design choice in Feudal States. The best fix would be to add an F4 entry in Feudal States that would trigger any Feudal-related mission screens.

However, given there is an ongoing operation to update Feudal States, I'll get an update for No Market Notification published that will prevent the no market screen from triggering on Feudal state stations.

[phkb]

No Market notification update should be live in the DM shortly.

[Cholmondely]

That's not the fault of "No Market Notification" - that's a poor design choice in Feudal States.

I have a sneaky feeling that is was not a bad design choice at the time. OXPs for the pre-1.80 versions of Oolite seem regularly to have used the F-screens for other matters. This changed when the vanilla game code allowed access to the docked F4 screen and allowed adding entries there.

F5: Commander's Profile (GUI_SCREEN_STATUS)
F5-F5: Ship's Manifest (GUI_SCREEN_MANIFEST)
F5-F8: APRIL content view
F5-F5-F5: List Visas (WIP Phantorgorth's Visas OXP)
F5-F5-F6: Flight Log OXP
F5-F5-F7: In-flight trophy log (from Trophy Collector)
F5-F5-F8: HyperCargo OXP (compatible with Vortex multibay)
F5-F5-F8: Vortex multibay (compatible with HyperCargo)
F6: Short Range Chart (GUI_SCREEN_SHORT_RANGE_CHART)
F6-F6: Galactic Chart (GUI_SCREEN_LONG_RANGE_CHART)
F6-F6-F5: Long Range Scanner
F6-F6-F5: Galaxy Info
F6-F6-F6: Galactic Hyperdrive OXP
F7: Data On Planet (GUI_SCREEN_SYSTEM_DATA)
F7-F6-F7: Long Range Scanner (WIP GGIndustries OXP)
F8: Commodities Market (GUI_SCREEN_MARKET)
F8-F8: AI Trading Assistant mode change (prior to Oolite 1.82)
F8-F8: Commodity "item" Information (GUI_SCREEN_MARKETINFO) (since Oolite 1.82)

List of landed planet-side key-combinations

F3-F7 Port view (Strangers World: Roolite's PlanetLand)
F4-F7 Port terminal view (Strangers World: Roolite's PlanetLand)
F5-F7 Planet/moon landscape (Strangers World: Roolite's PlanetLand)
F8-F7 City/station view (Strangers World: Roolite's PlanetLand)

The only intuitive one was Wildeblood's F3-F3-F3 for his Galactic Hyperdrive view of the next Galaxy and the possible arrival spots therein.