(Please do not post in the comments section to report bugs)
Before posting a comment... please read the entire addon description below - especially the Frequently Asked Questions section!
For best results, get your friends and guild mates to install Nauticus.
--- What is Nauticus?
Nauticus tracks the precise arrival & departure schedules of boats and Zeppelins around Azeroth and displays them on the Mini-Map and 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 duelling rogues or shamies who want you to take a seat while they crit you... 'for fun'...
To track a transport requires that you, or someone else running the addon, has taken the route sometime earlier. Nauticus uses hidden addon-to-addon communications to synchronise and share up-to-date schedules between players automatically.
Important: This addon works best the more players on your realm also using the addon. So get your friends and guild mates to install Nauticus - the more the merrier! Even if you don't use transports because you're only ever in Outland, you can help store and transmit up-to-date data to everyone that needs it. Nauticus performs well in the background and you can disable the map icons for zero interference.
--- Main Features
Plots all (16) Horde, Alliance and neutral transports on the World Map in real time
Displays the most relevant transports on the Mini-Map, based on your current zone
Map icons rotate to show their actual direction at any point in time
Shows arrival or departure schedule for each platform when you mouse-over any map icon
Discovers schedule by travelling a route in either direction
Calculates future schedules, based on precisely measured round-trip cycles
Automatically share schedules with other users of the addon on your realm
Differential delayed updates keep communication bandwidth low even with many users (O(1))
Ranks quality of data based on number of reboots and swaps, always picking the best
Remember schedule data even after computer reboot (see FAQ for caveat)
Select any transport for viewing in any LibDataBroker (LDB) display addon.†
Shows the next arrival or departure event in the button text.
Button icon changes colour to indicate status (yellow = docked, red = about to depart, green = in transit)
Auto-selects nearest transport when standing at a platform (optional)
Alt-click button to manually set audio alarm to warn you before next departure
Less spam: Filter ship crew talk and Zeppelin Master yells from your chat window (optional)
† If you're new to Broker plugins, they're a bit like FuBar plugins but displayed how you want. Try StatBlockCore, Button Bin or Fortress for display addons and see here for more plugins. Titan has LDB support built-in. FuBar requires the lightweight bridge addon Broker2FuBar (not to be confused with FuBar2Broker, which does the opposite).
Usage
Find out the status of a transport via World Map/Mini-Map or via an LDB button display.
For options, type /nauticus or /naut in the command line.
--- TO DO
Auto pop-up tooltip and/or sound arrival/departure alarm (i.e. Zeppelin horn or boats bell) when at platform
Nauticus is always in continual development. You should 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. You'll be notified 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 schedules?
A player with the addon needs to travel on the boat/Zeppelin/turtle before the schedules come up. This could be you or someone else who may have taken the transport earlier. The most recent schedules are synchronised between other players running the addon, so after a short while the data will most likely be available to you before you take any transport. Get as many of your friends and guild mates to install Nauticus - the more the merrier.
Q. How does Nauticus get the schedules?
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 schedules at any point in time.
Q. How accurate is it?
Round-trip cycles have been calculated to one microsecond (six decimal places) over a 1-2 week period. This is significantly better resolution than provided by the API, which only measures in milliseconds (three decimal places). 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.
Q. Why are some of my schedules wrong?
Rarely, schedules can become corrupted due to changes in your computer's system clock that may occur between WoW sessions/reboots. This can also be caused by dodgy CMOS batteries and some over-clocked systems. Otherwise, Nauticus can normally keep track of schedules between reboots. Additionally, while realm servers appear to keep very precise clocks for running the transports and to generate their positions, from time to time they may re-synchronise these clocks, sending the data slightly out of wack. Nauticus should quickly fix the schedules, as it will gather more recent and better quality data from other users or from your own travels.
Q. Doesn't weekly maintenance ruin the schedules?
It doesn't! We can only assume how Blizzard calculates transport schedules and their positions but it's probably based on the realm server's system clock, which is likely synchronised with a centralised ntp time server at each data centre. You can verify this by visiting another realm (at least, in the same geographical location - e.g. EU, US Eastern) to observe exactly the same schedules. This is another way to obtain accurate schedule data - from other realms. If there is one, an epoch is presently unknown - if any maths wiz can manage to reverse engineer it (simultaneous equations?), do let me know!
Q. Why does Nauticus have to use a chat channel?
Blizzard's SendAddonMessage() API is effectively limited to guild and raid addon communication, which is insufficient to get data spread furtherest across your realm. For maximum availability and accuracy of schedules, we need to use a chat channel. You shouldn't be concerned if you have the channel slot spare - we're extra careful not to mess up channel numbers.
Q. Where did the GUI disappear to?
The red window was removed in favour of map icons with tooltips. It became difficulty to maintain the rather clunky code necessary to provide this functionality and consumed more resources than desirable. Plus it didn't cater for other languages very well due to its fixed size. Native FuBar support was removed in favour of LibDataBroker (Broker/LDB) displays. Broker allows you to choose your method of displaying plugins. The lightweight bridge addon Broker2FuBar returns the old FuBar functionality, as well as allowing you to put it as a Mini-Map button (even if you don't use FuBar).
Q. Can you add the Deeprun Tram?
Unfortunately no, since it's treated as an instance and we can't properly track player coords within instances.
---
Nauticus is a complete rewrite of ZeppelinMaster which was originally conceived by Sammysnake. He runs a DKP hosting service @ dkphosting.net.
Change Log - Nauticus
v3.2.0
- add new zeppelin route - The Zephyr for patch 3.2
- fix: don't trigger coords when in vehicle
- remove some legacy saved var handling
- update deDE and ruRU
v3.1.4
- fix: mini-map icon rotations when rotate minimap not set
v3.1.3
- fix: don't error if encounter invalid comms decoding
- fix: put LibDBIcon-1.0 in no-lib-strip section of .toc
- anchor map icon tooltips to mouse cursor
- append string hash value to known transport data in comms
- kill tabs in .pkgmeta
- fix OptionalDeps and put back X-Embeds
v3.1.0
- fix: replace MiniMapCompassRing with GetPlayerFacing()
- re-package for GetPlayerFacing() fixes in latest Astrolabe
v3.0.9
- fix: occasional bad/inaccurate comms data being exchanged
- fix: error clicking ldb button if all transports filtered from list
v3.0.8
- fix: issue when detecting if dropdown is shown (caused by patch 3.0.8)
- new version notification shown in tooltip instead of chat
- update frFR, esES
- remove mini-map overlay (again)
- mini-map button now shown by default
v3.0.6
- span lengthy comms over multiple messages if necessary
- ignore comms messages that are too long
- fix: possible error if player coords are invalid immediately after login
- fix: possible bug if global var 'version' exists
- minor localisation updates/tidy-up
- compress comms number data (not backwards compatible)
v3.0.5
- bump internal version number (i'm a nubcake)
v3.0.4
- port to Ace3, add in Blizzard interface options
- add new vessel icons for WotLK and re-do others for consistency
- replace bloaty Dewdrop with UIDropDownMenu
- add individual options to toggle both world and mini map icons
- fix: possible data corruption when clock drift is detected as wrong
- fix: nil argument to fmod in DrawMapIcons() due to the above bug
- fix: nil value in ShowTooltip() if old route selected
- fix: flickering world map icons in Carbon$hite
- fix: icon not showing in some ldb displays (e.g. statblockcore)
- fix: case for some libs paths in .toc
- extend new routes on mini-map into orgrimmar and undercity
- change default world map icon size to 125%
- add minimap button (default state is hidden)
- add option to show only faction-friendly map icons
- add emote's to crew chat filter
- temp text delay increased to 2-3s
- remove key modifiers for unlocking tooltip frame, to fix partial draw issue
- change the show map icon settings to profile-based instead of per char
- parent icons to WorldMapButton and test its visibility to fix some map mods
- give mini map icons a global name to allow certain mods to skip re-parenting
- add world map overlay to Astrolabe's list of map frames to watch out for
- set proper level for tooltip frame
- properly hide the map icons in all cases
- optimise the texture rotation and handling
- put version number in ldb title contexts
- use spanish locale for esMX
v3.0.3
- FIX: Northspear, Cloudkisser and Captured Zeppelin routes
- FIX: issue where triggering could occur after login/reload (d'oh)
- completed German and Chinese localisations (thanks LarryCurse and Juha!)
- add Titan as OptDep so we can hook CloseRightClickMenu properly
- some code cleanup and optimisations, remove lots of debug stuff
- add Harrowmeiser to chat filter
v3.0.2 r91
- completed Russian and French translations (thanks Zuz666 and thelys!)
- couple of zone name fixes for German and Spanish locales
v3.0.2
- remove unused localisations and add some missing strings; options, ship and npc names
- more complete German translation (thanks LarryCurse)
- complete traditional & simplified Chinese translation (thanks Juha)
- add initial Russion localisation (thanks Zuz666)
v3.0.1
- FIX: chat frame breakage (white window and all chat filtered)
- add WotLK routes (Valgarde boat and Westguard Zep not working yet)
- change 'The Bravery' route from Menethil to Stormwind
- recalibrated all old world routes
- FIX for Titan v4+ (now uses LDB...)
- replace TabletLib with custom LibSimpleFrame (much less bloated tooltip lib)
- replace FuBar/Titan plugin code with LibDataBroker (LDB)
- remove legacy GUI (red window)
- removed CHAT_MSG_ADDON (guild/raid) and custom channel
- removed data reset option (abused and unnecessary)
- add Sky-Captain Cableclamp + Navigator Fairweather to crew chat filter
- rename 'goblin' to 'crew' (chat filter), rename 'Ra' to 'Rat' abbreviation
- colour routes in right-click dropdown menu based on faction
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!
No, I'm not holding down any modifiers when I mouse over it. I don't have any trouble with the tooltip staying and not going away. It will sometimes stick, but a quick mouseover again, and it goes away. But the "ghost" of the tooltip is always there when the Nauticus module is active for StatBlock. Anything that appears in that area of my screen in unclickable.
Interesting. I've seen the half-drawn tooltip before, but only during development when I haven't properly 'locked' it. Otherwise I'm unable to reproduce it in normal circumstance.
However, by any chance could you be using the Alt key while moving the mouse over the button? This is a sure-fire way to reproduce it, but I need to know if this is what's happening to you.
If so, I can remove the key-modifier code - which temporarily unlocks the tooltip - from the library (which is modified for my purposes anyway) and fix the problem that way...
One small problem I'm having though with the LDB plug-in. I'm using StatBlockCore for my LDB plug-ins (not sure if that matters), and the tooltip will sometimes get stuck in the show position (sometimes the full tooltip, sometimes just an empty black box). And, where the tooltip pops up, a "dead space" is always there in my UI. Any window that opens up under this "dead space" will become unable to be interacted with. No mouse-over functions no clicking nothing. I noticed it when i changed the layout of Baggins, and the top few item slots (the ones under where the Nauticus tooltip usually shows up) became unclickable for me. I thought it was a Baggins problem at 1st, until I noticed that the same thing occurs with Talented. After disabling the LDB plugin for Nauticus, it all started working fine.
Small inconvenience, but thought I'd let you know.
Well I don't understand why don't you give one a try? Many addon these days are providing LDB plugins (and not just the dedicated Broker plugins). You're simply missing out.
What's more, the lightweight Broker2FuBar plugin is essentially the SAME as the old FuBarPlugin-2/3.0 library that was included (without option) with previous versions. It provided the mini-map button in the event that FuBar isn't loaded - purely incidental.
The only difference is the code is detached and gives the user the option of including it (since you may not need it if you have Titan, or another LDB addon).
Oh well. You're free to try the alpha version on WowAce.com if you want the mini-map icon that badly...
The minimap icon was provided by the FuBar plugin system, I got rid of that to support LDB - which allows the end user to choose their own display (Titan, FuBar or any other).
You can get the minimap icon back using Broker2FuBar (even if you don't have FuBar) or use an LDB display addon such as StatBlockCore, Button Bin, Fortress etc..
I've already added a lightweight minimap option for the next version. However, I recommend using a proper LDB display since a minimap button obviously isn't capable of showing the schedule time in its tiny space.
The minimap icon isn't showing up for me, tried fiddling with the options, so I have no way to display arrival/departure times currently, thought you should know.
If you delete your WTF folder, you'll also lose all the timers - so don't do that. Otherwise, you should check your world map for any of the vessels (the world map and the mini-map icons is the primary interface for this addon).
I've not had any problems with Broker2FuBar, check that you don't have another kind of LDB display addon doing the same thing? B2F has options under Interface > Addons btw, that you could check.
Or you could try Fortress or ButtonBin. They all work together (multiple at once). Once you have the button, right-click it to check if you have any data - green, red or yellow (coloured by faction for known data) or grey for none.
My problem with Broker2FuBar is that, for a few of my addons, it puts them on the FuBar twice.
Oh, and my problem is not that it is just not showing up on the FuBar. Nauticus isn't showing up AT ALL. I've deleted the folder, cleared the saved variables, and nothing seems to get it working...
Originally posted by Tungsten Spleen I have the same problem. I can find the preferences for Nauticus under the Fubar right-click menu... and I can make changes, but no display on the bar... I'm using the latest Nauticus and Fubar 3.5
Otherwise, you should check your world map for any of the vessels (the world map and the mini-map icons is the primary interface for this addon).