Several people have recommended me lately to ask for a permission from Dwarf Fortress authors if I’m going to release the DF Remote app.
I can assure you that it’s been discussed with Toady in the beginning of the development, as well as I’ve made him aware of the upcoming release recently.
What people can do is to remember to support Bay 12 Games if they enjoy playing Dwarf Fortress - using DF Remote or not, and also that Toady should not be bothered with any issues related to DF Remote.
I think I’ve finished development of Dwarf Fortress Remote for iOS for now. Below is the list of things that will most likely be missing from the first release. They may be important for advanced players but anyway I expect there will be bugs and more things I’ve forgotten about, so I will implement remaining features along with bug fixes.
There will be no support for workshop profiles, stockpile-workshop links, hauling side menu, routes creation. Stockpile settings are somewhat incomplete (third level of settings is not available, whatever it is on it). Some other minor things may be missing here and there but they should not affect gameplay that much. Also, embarks larger than 5 embark tiles are not supported, and no creature graphics and multi-level rendering, however these are likely to be fixed in first place.
Now I just need to do more testing and fix some non-gameplay related issues like UI on iPad, proper error messages, automatic check for server updates and so on. Then I will send the application to App Store for review and in the meanwhile will complete work on installation instructions and in-game help (remember, there is/will be short help for each screen, building and other gameplay elements).
Crash reporting feature is broken in Parse.com for a month already according to reports from many people. Status page shows that all services operating fine, engineers are supposedly investigating the problem all this time. Now, how can we be sure that other more critical functionality doesn’t stop working silently one day?
Strictly Necessary Cookies
Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.
If you disable this cookie, we will not be able to save your preferences. This means that every time you visit this website you will need to enable or disable cookies again.