The beta launcher for FFXIVMinion is ready for download and testing:
http://patcher.gw2.mmominion.com/Updater...r_beta.rar
The following list contains information about significant changes and additions:
The following functionality is being worked on currently and will be pushed to the beta launcher over the duration of the v1.5 beta (over the next few weeks)
MarkerManager considerations
The MarkerManager uses a new format for marker info files - your old info files will be converted to the new format when loaded for the first time. The old marker data will be renamed *mesh_name*.info.old after the conversion process and located in the navigation folder. This is done as a backup in case any bugs lead to corruption of the new info file. However, if you're paranoid you may want to consider backing up your info files manually - this is a beta and anything can happen. Also, since the info file formats are different the marker files can't be shared between the FFXIXMinion release and beta launchers. You will need separate navigation folders for each launcher (no symbolic links).
Questing considerations
Currently there is no way to query the FFXIX client to determine which quests have already been completed. Thus, the bot stores data on which quests it has completed as it runs a questing profile. Therefore, if you begin a questing profile for which you manually completed the prerequisite quest, the bot will not be able to detect that the prerequisite has been completed and will not run the profile. In order to workaround this problem, a button has been added to the Quest settings "Set Quest". In order to use this button, open the quest journal, select the quest the profile should run (a quest for which you know the prerequisites are already complete) and press the "Set Quest" button. This will select the quest for the bot as the current quest (bypassing the prerequisite check) and the bot will run the selected quest when the "start" button is pressed. When the quest is completed, the bot will add it to the list of completed quests and any quests which rely on it should work, allowing the rest of the profile to run properly.
Also, please remember that the questing code is very new and has not been widely tested - this is why the beta exists. Expect to encounter bugs and unhandled quest actions. When you encounter these, report them in this thread so that we can keep a list of quest types which need to be added. The quest engine itself (the part that runs the profile, selects and run quests, etc) probably also has bugs that will need to be worked out. Please report beta bugs in this thread and this thread only - not in support threads or general discussion. On the same note, do not report non-beta specific bugs in this thread.
http://patcher.gw2.mmominion.com/Updater...r_beta.rar
The following list contains information about significant changes and additions:
- MarkerManager
- See below for important MarkerManager information
- The MarkerManager is a replacement for the GatherManager and MeshManager marker controls
- The GatherManager has been removed completely and the MeshManager no longer contains any functionality for markers
- See Jackie's guide/tutorial for more info: http://mmominion.com/Thread-Tutorial-Marker-Manager
- See below for important MarkerManager information
- Questing
- The first version of questing engine is ready for testing and ace has designed an excellent interface for editing quest profiles (duty profile editing will be implemented as well shortly)
- See below for special information regarding Quest mode
- The following quest types/actions are currently supported:
- Start
- Complete
- Interact
- Kill
- Item Turning
- Select Reward
- World navigation using run/aetheryite teleport
- Start
- The following quest types/actions are NOT currently supported but will be:
- Emotes
- Use specific action on object/entity
- World navigation using airships/boats
- Gear level checks
- Dungeons
- Probably others (tell us which ones)
- Emotes
- See Jackie's tutorial/guide for more information: http://mmominion.com/Thread-Tutorial-Pro...t-Profiles
- You will need to grab the city meshes at: http://mmominion.com/Thread-City-Meshes and put them into your beta launcher /Navigation folder for world navigation to work properly in cities
- The first version of questing engine is ready for testing and ace has designed an excellent interface for editing quest profiles (duty profile editing will be implemented as well shortly)
- Tweaks and Optimizations
- Recently released duty updates (see previous news posts)
- Loot task is now part of main duty code (no addon)
- Ace has moved most of the optimizations/tweaks from his addon to the main code
- PVP fixes (more details to come on this)
- Recently released duty updates (see previous news posts)
The following functionality is being worked on currently and will be pushed to the beta launcher over the duration of the v1.5 beta (over the next few weeks)
- New dynamic settings interface displaying only settings for currently selected mode (yes, we know there are way too many settings entries atm)
- More pvp behavior updates and fixes
- More quest actions handled
- World nav using boats/airships
MarkerManager considerations
The MarkerManager uses a new format for marker info files - your old info files will be converted to the new format when loaded for the first time. The old marker data will be renamed *mesh_name*.info.old after the conversion process and located in the navigation folder. This is done as a backup in case any bugs lead to corruption of the new info file. However, if you're paranoid you may want to consider backing up your info files manually - this is a beta and anything can happen. Also, since the info file formats are different the marker files can't be shared between the FFXIXMinion release and beta launchers. You will need separate navigation folders for each launcher (no symbolic links).
Questing considerations
Currently there is no way to query the FFXIX client to determine which quests have already been completed. Thus, the bot stores data on which quests it has completed as it runs a questing profile. Therefore, if you begin a questing profile for which you manually completed the prerequisite quest, the bot will not be able to detect that the prerequisite has been completed and will not run the profile. In order to workaround this problem, a button has been added to the Quest settings "Set Quest". In order to use this button, open the quest journal, select the quest the profile should run (a quest for which you know the prerequisites are already complete) and press the "Set Quest" button. This will select the quest for the bot as the current quest (bypassing the prerequisite check) and the bot will run the selected quest when the "start" button is pressed. When the quest is completed, the bot will add it to the list of completed quests and any quests which rely on it should work, allowing the rest of the profile to run properly.
Also, please remember that the questing code is very new and has not been widely tested - this is why the beta exists. Expect to encounter bugs and unhandled quest actions. When you encounter these, report them in this thread so that we can keep a list of quest types which need to be added. The quest engine itself (the part that runs the profile, selects and run quests, etc) probably also has bugs that will need to be worked out. Please report beta bugs in this thread and this thread only - not in support threads or general discussion. On the same note, do not report non-beta specific bugs in this thread.