I'm working on a scenario with a time critical element and players would be able to choose between teleport directly to the main encounter POI from a station they starter spawned in or commandeering an SV to travel to the POI (or split the party in an MP game) ... the problem I'm having is that past a short distance the game starts reminding you, every 60 seconds, that "You need a warp drive to travel to a location outside your sector" ... whereas you're actually just heading way out there for 15-20 minutes to reach a POI that's located 10K+ away. Is there any way to suppress this? I've looked in both sectors.yaml and various playfield yamls and can't see anything where you configure that. Forcing a long real-time delay for choosing to take the SV is a goal- I can imagine a warping/landing scavenger hunt across planets in the sector to find the destination but given the static nature of a playfields can't figure out how to turn that into an obstacle other than the first time you play the scenario. Appreciate any thoughts on a workaround or alternate approach, thanks muchly!
How far are you from the playfield coordinates 0 0 0 ? This message should only trigger when you are past roughly 50km from the center of the playfield coordinates 0 0 0 iirc.
Thanks for getting back so quick, fixed placement of the BAO POI is at (currently) -12263 -50531 -11862 which is 55704 units distance ... I set course towards the sunflower and went at 120 for 15-20 minutes to pick the spot. So if I head back 7K or so the message goes away? Ooops ... lost a digit... Pos: [-12263, -50531, -118624] so much further out .. 129,085 units from the origin.
If I cripple the SV down 60% that'll get me there- you can take time scavenging to get to a better max speed but that would be time spent .. I'll throw another pretty please into the feature requests, guessing they're pretty busy right now!! ( thanks again @Pantera )
Yeah that distance from origin will trigger the message keep it under 50km & it shouldn't appear. This distance will remain which is part of the floating origin point calculations & needed to avoid potential issues when distances get really huge (50km from origin is already massive).
