<!--quoteo(post=177791:date=Jan 3 2007, 10:03 PM:name=morgan terror)--><div class='quotetop'>QUOTE(morgan terror @ Jan 3 2007, 10:03 PM) [snapback]177791[/snapback]</div><div class='quotemain'><!--quotec-->
some problems with your ideas:
you are right about the bit with the storm. however, when you go from the world map to the sea, the directsailmod no longer works. it only works when you don't go to the world map at all. <!--QuoteEnd--></div><!--QuoteEEnd-->
Exactly. Which is why you'd have to find some way to artifically bypass the world map and return yourself to Battle Rocks automatically. I'm not sure if that's possible.
<!--quoteo(post=177791:date=Jan 3 2007, 10:03 PM:name=morgan terror)--><div class='quotetop'>QUOTE(morgan terror @ Jan 3 2007, 10:03 PM) [snapback]177791[/snapback]</div><div class='quotemain'><!--quotec-->
redmond is on the direct opposite side of the carribean when sailing from oxbay.
it takes half a day to sail all the way from redmond to oxbay. i tried adjusting the time speed, but making it correct in comparison to the distance would make sea battles impossible. you wouldn't be able to board a ship, as all neutral ship dissapear after every hour.
<!--QuoteEnd--></div><!--QuoteEEnd-->
I'm not quite sure what you're getting at, I'm afraid...
I'm assuming you're referring to how the DirectSail mod currently works with regard to time / distance travelled. What I'm proposing wasn't a way of implementing the 'correct' distances as seen on the world map, but a smoke-and-mirrors way of creating navigational inaccuracy.
My use of the Battle Rocks sea zone is to replicate the miles and miles of open sea between islands. Every time you leave an island sea zone, you go to Battle Rocks. Depending on where you enter Battle Rocks from, the game uses code to determine what you have to do in order to leave Battle Rocks and get to an island sea zone. This intentionally includes passing through Battle Rocks several times (ie, there's code preventing you simply sailing out of it to a specific destination).
Perhaps the best way to imagine it is a massive great octagonal grid, say 100 x 100. In that grid are placed a set of islands with specific co-ordinates. To sail from one island to another, you have to move correctly from one octagonal square to another until you reach your destination. You could also change direction and head for a different island. It doesn't particularly matter what route you take - direct, or zig-zag, etc. As soon as you get to the correct co-ordinates, you reach that island.
In this grid format, you can't simply set a course of 024 degrees and travel in a straight line to your destination. You might have to go N, N, N, NE, for example. In this gridmap, though, the majority of sea squares are wasted space that would never be sailed in...and, if you know that N, N, N, NE is the route from one island to another, that's what you'd sail. You might vary it by going NE, N, N, N but, ultimately, you're sailing on a grid and you know it.
What my suggestion does is replicate the same situation with the grid and the islands, but only using one blank square. Rather than being directly connected, the blank square is a detached hub that you teleport to, which then tracks your virtual location depending on which edge you leave by and requires you to meet its conditions (ie, a set number of successful exits) before it allows you to teleport to an island square.
The { days } entry was intended as a way of indicating rough distance between your current location and your destination. It doesn't necessarily indicate the exact time of travel required, nor does the unit of time have to be measured in days.
The key part isn't the distance between islands, but the time taken in GAMEhours to sail out of a sea zone. The minimum time taken to complete a journey using the navigation method I'm suggesting would be the GAMEhours taken to travel out of the Battle Rocks sea zone multiplied by the number of times you have to leave the Battle Rocks sea zone. The actual time could be longer if navigational errors come into play.
For arguments' sake, lets say that all of the time speeds are left unchanged so that the game plays as it currently does and that all the travel times used in my following example are completely arbitrary.
Journey: Island 1 to Island 2 (2 sea zones distance required)
---------------------------------------------------------------------
Island 1 - Battle Rocks (5 hours)
Battle Rocks - Battle Rocks exit (10 hours). Player reset in Battle Rocks. (1 zone travelled)
Battle Rocks - Battle Rocks exit (10 hours). Player passes to Island 2 sea zone. (as 2 zones travelled)
Journey time: 25 hours
The above is the example I was working with in the navigation mod and assumes that the player leaves the Battle Rocks zone by the correct exit. Its a short, easy journey.
If you wanted to make it more interesting, you simply increase the number of sea zones of travel required to complete the journey. The chances of error then grow larger, so the actual number of sea zones you need to travel before you successfully complete the journey will also increase.
Provided there are no technical hitches, you *could* use this as way to get the journey time to be realistic, but it'd make long journeys take up to 100 sea zones' worth of travel. That's going to take a horribly long time to sail, and would require greater speeds of time compression...which would, of course, make the sailing dull, pointless and dangerous if you ended up unexpectedly in combat.
" border="0" alt="smile.gif" />
" border="0" alt="icon_mrgreen1.gif" /> Or shall we vote?
" border="0" alt="whistling.gif" /> Surely it must be tested - I took a piece of code from WorldMap SailHo screen <img src="style_emoticons/<#EMO_DIR#>/dunno.gif" style="vertical-align:middle" emoid="
" border="0" alt="dunno.gif" /> 
