---
Nauticus tracks the precise location of boats and Zeppelins around Azeroth and displays them on the Mini-Map & World Map in real-time.
Look up arrival & departure schedules for any transport and know exactly when you need to be there. Less time waiting on platforms, more time at the AH or mailbox, less time duelling rogues or shammys who want you to take a seat while they crit you... 'for fun'...
To track a transport requires that you (or someone else running this addon) have taken the route sometime earlier.
Nauticus uses hidden addon-addon communications to synchronise and share up-to-date schedule information between players automatically.
For usage options, type /nauticus or /naut in the command line.
If you don't use FuBar (e.g. you use Titan instead), you can right-click
the Mini-Map button and 'Hide plugin' to get rid of it.
Uses the Ace2 framework (soon Ace3 when it becomes stable).
--- UPGRADING
If you're upgrading from previous Nauticus versions, please make sure to DELETE the old folders before extracting; Nauticus, FuBar_NauticusFu, TitanNauticus and MapLibrary. MapLibrary is no longer used and FuBar & Titan plugins are now integrated. You only need the one folder.
If you're upgrading from ZeppelinMaster, please DELETE the old folders; ZepShipMaster, FuBar_ZepMasterFu and TitanZeppelinMaster, before extracting this package.
--- TO DO
- auto pop-up tooltip and/or sound arrival/departure alarm (i.e. Zep horn or boat bell) when at platform
- new compact UI window, listing schedules for all transports in the zone, highlighting closest platform when standing still and nearby
Note: Nauticus is in continual development [13th Jan 2008]. You should
always try to keep your version up-to-date - not least because the addon
interacts with other users and they rely on good quality data from you.
The addon will notify you upon login when there's a new version
available - after other users are seen using a later version. For this
reason, please DON'T redistribute or include in a compilation pack!
--- Frequently Asked Questions
Q. I just installed Nauticus, why don't I see any timers?
A player with the addon will need to travel on the boat or Zeppelin before the timers come up. This could be you or someone else who may have taken the transport earlier - that day, or days ago.
The most recent timers are synchronised between other players who run the addon, so after a short while the data will most likely be available to you before you take any transport. So get your guild mates and friends to install Nauticus too, the more the merrier.
Q. Why are some of my timers wrong?
In rare conditions, timers can become corrupt due to big changes in your own system clock that may occur between WoW sessions/reboots. This can be caused by dodgy CMOS batteries and some over-clocked systems.
Also, while the realm servers appear to keep very precise clocks for running the transports - to generate their positions etc. - from time to time they may re-synchronise these clocks, sending the data out of wack slightly. (Note: I can only assume this, since I've only seen it happen once or twice, but I do know that transports are in sync across all realms in a particular geographical location - i.e EU, US Eastern).
Nauticus should quickly fix these timers, as it will gather more recent and better quality data from other users or from your own travels.
Q. How does Nauticus get the times?
There are no Blizzard-provided API methods to directly determine the transport schedule. Thus we do it indirectly by getting player coords and comparing them to a known set of coords along the route.
When the player triggers these coords, we know the cycle and can subsequently work out future cycles at any point in time.
Q. How accurate is it?
Round-trip times have been calculated to one millionth of a second (six decimal places) over a 4/5 day period, although in reality, accuracy is probably around ten thousandth or hundred thousandths of a second.
This is significantly better resolution than provided by the API, which only measures in milliseconds (three decimal places). So baring slight adjustments in Blizzard's clocks etc., 99.9% of the time there should be no observable drift of more than a second or two.
You should urge as many of your guild mates and friends to run the addon as possible - even if just in the background - even if they don't use transports because they're only ever in Outland. They can help store and transmit up-to-date timing data to everyone that needs it.
Q. Why does Nauticus have to use a chat channel?
Because Blizzard's SendAddonMessage() API alone - which was really designed and is effectively limited for guild and raid addon comms - is insufficient to get the times spread further across your server. This ultimately affects availability and accuracy of the times.
You shouldn't be concerned if you have the channel slot spare - we're extra careful not to mess up channel numbers. If you experience issues, please see http://www.wowwiki.com/Fix_Chat_Channels first.
Q. Can you add the Deeprun Tram?
Unfortunately not, since it's treated like an instance and we can't track player coords within an instance.
---
Nauticus is a rewrite of ZeppelinMaster which was authored and conceived by Sammysnake - he runs a DKP hosting service online, please support his work @ dkphosting.net. Dedicated to hosting for guilds in such games as WoW, Everquest, Everquest II and Dark Age of Camelot.
---
Version History
v2.4.1
- IMPROVED data accuracy; prioritise quality on boots < swaps < since
- NEW: auto select transport option when standing near platform
- FIX: world map icons staying when trying to hide them
- show multiple transports in tooltip for all map icons under mouse
- slightly tweaked round-trip-times again (15 day period)
- added all options to Titan/FuBar right-click menu
- remove some irrelevant FuBar options from slash command
- more complete French translation (thanks thelys/yann!)
- esES updated (thanks StiviS!)
v2.4.0
- UPDATE: all routes recalibrated for patch 2.4, finally
- FIX: Titan button update for newer v3.20+ (backward compatible)
- FIX: updated embedded Astrolabe lib; no more lockups during zoning
- warn that cycle data reset is for emergency usage only!
Originally posted by tinyu any chance of a wotlk beta... assuming you got a key that is.
Yup, working on it now. There's an error-free version on WAU/wowace svn if you wanna have it running (and get alerted when new versions come along) but the new routes need to be added and the old ones updated due to the movement of continents. Will put up a beta branch when that's done, soon.
Apologies for the delay in getting this update for 2.4 out, lots of RL stuff got in the way, and this calibration stuff does take time - sitting on boats etc. and watching them go round and round and round...
Expect another small update in a few days to improve the microsecond accuracy of the round-trip-times of the two NE boats at Auberdine (Blizzard tweaked them in the patch since they were colliding with each other ).
At least two of the routes will need to be recalibrated for patch 2.4 and I have a further accuracy improvement to make to the code. I will get straight onto it as soon as EU realms are updated...
Ahh... Actually those options are already available via FuBar. Show/list transports for a) faction only and b) zone only. The only other option available via the UI option button (looks like a speech bubble) is related to whether or not to show the UI window on zone change. Which will be deprecated along with it. So neither are needed if you've got FuBar.
But yep, the command line options (also available through Rock) will soon be available via FuBar. And then Ace3 Config depending on when that's finalised...
I don't have access to the game atm, but as you alluded to, there are options (iirc somewhat important ones) available in the GUI that are not available through FuBar. If you added these options to FuBar, then yes, there would be no need for the GUI, and thus my request would be unnecessary.
Originally posted by echobravo I'm surprised this hasn't been requested yet, but I have a simple request. Can you please add the ability to display the Nauticus GUI from Fubar?
Why would you want to use the main UI red window when you have FuBar? And map icons?
They're supposed to be alternatives - i.e. use one or the other. In fact, I had planned to remove what is essentially, a fairly crude/legacy interface, from the code entirely. I guess I'd just like to know, why do you use it and how?
Now that FuBar is fully integrated into the core, I'll inject the rest of the options - including the legacy UI ones - into the bar menu. But I do eventually want to get rid of the old UI.
I guess this should happen after I add detection of nearest platform for selecting and auto-display of interested transport...
The version I just uploaded contains several minor fixes and tweaks. Accuracy of all round-trip-times is basically finalised and pretty damn good. It should drift no more than 0.1 seconds over a 2 week period.
Importantly, we now default back to a world chat channel for data sync (you *can* manually change it to the guild comms API via slash command but it is NOT recommended!). This is necessary to get the data spread furthest. Don't mess unless you absolutely have to.
Patch 2.3-compatible release uploaded, finally. IMPORTANT: Due to significant route changes, sync comms backward compatibility is not supported. So get your friends and guildies to update too! (Remember, Nauticus is on WAU also.)
Nope, I've spent a long time on those boats and zeps recently to know those goblin yells are pretty much useless. (The alliance boats don't have anybody that yells either). They're often many seconds out, repeatedly spammed or sometimes completely wrong (part of the reason why Nauticus has a chat filter!).
Nauticus triggers the routes with almost millisecond precision so I'm quite happy with how it's working right now...
I haven't travelled all the routes yet, but at least the zeppelins have goblins that 'announce' their arrival at a platform.
Could you use these announcements to time the routes instead of coordinates? I'm not sure if this would be more efficient, but it seems simpler and less prone to false positives.