Metrienne
New Member
- Joined
- Jul 2, 2013
- Messages
- 27
Hello,
I noticed a bit of discussion regarding the potential of botting within flashpoints. I've done some testing on the side and this is the result. Unfortunately I don't plan on making more of this nature for reasons I'll elaborate towards the end. At its current state, if you are not interested in constant supervising then you should not use this profile. This is currently in beta and will most likely have issues, especially during the generator step and when restarting. Please report any issues!
Anyway, this profile I made will attempt to conduct The Battle of Ilum flashpoint up until the last boss. This is a proof of concept showing the limitations of what Buddy Wing can and can't do with flashpoints.
I recommend doing this with a level 55 character. Battle of Ilum story mode drops Classic commendations and Black Hole gear.
Instructions:
You must first obtain the mission that grants entry to the flashpoint. This is accomplished at Ilum. Start the profile once inside. The profile has location-based checks that should continue where you left off should you have to restart the profile.
Yet to be tested:
Additional comments:
The issue with botting within flashpoints is that Buddy Wing does not consider the flashpoint mission itself (not the one picked up outside) as a trackable quest. As such, this profile is relying on XYZ coordinates or other conditions to determine where you're at and ultimately what to do next. Normally profile writers would use QuestID (and their steps) as a means to keep track of what to tell Buddy Wing to do.
In addition, not having a trackable quest makes some mission steps difficult to accomplish. For example, at one point in Battle of Ilum we have to destroy three Force Field Generators using three Control Panels to reach the next step. A step like this normally calls for "UseObject," which will tell Buddy Wing to try until the step or task is complete. But because we have no trackable quest, we have to resort to "Interact" which is a one-time best effort attempt. If it doesn't work, Buddy Wing assumes it's been done and moves on anyway (which is not good in this case). Destroying the supply boxes to get to the bonus boss is hard to do for this same reason.
Finally, any mob or boss fight featuring any mechanic other a simple fight can potentially break Buddy Wing. For example, Darth Serevin, the end boss, has a mechanic where he disappears and reappears periodically throughout the encounter. It is at that time that Buddy Wing may fail to resume fighting.
I noticed a bit of discussion regarding the potential of botting within flashpoints. I've done some testing on the side and this is the result. Unfortunately I don't plan on making more of this nature for reasons I'll elaborate towards the end. At its current state, if you are not interested in constant supervising then you should not use this profile. This is currently in beta and will most likely have issues, especially during the generator step and when restarting. Please report any issues!
Anyway, this profile I made will attempt to conduct The Battle of Ilum flashpoint up until the last boss. This is a proof of concept showing the limitations of what Buddy Wing can and can't do with flashpoints.
I recommend doing this with a level 55 character. Battle of Ilum story mode drops Classic commendations and Black Hole gear.
Instructions:
You must first obtain the mission that grants entry to the flashpoint. This is accomplished at Ilum. Start the profile once inside. The profile has location-based checks that should continue where you left off should you have to restart the profile.
Yet to be tested:
With a Republic character- In hard mode
- In a group
- Adding instructions walking into the flashpoint
Additional comments:
The issue with botting within flashpoints is that Buddy Wing does not consider the flashpoint mission itself (not the one picked up outside) as a trackable quest. As such, this profile is relying on XYZ coordinates or other conditions to determine where you're at and ultimately what to do next. Normally profile writers would use QuestID (and their steps) as a means to keep track of what to tell Buddy Wing to do.
In addition, not having a trackable quest makes some mission steps difficult to accomplish. For example, at one point in Battle of Ilum we have to destroy three Force Field Generators using three Control Panels to reach the next step. A step like this normally calls for "UseObject," which will tell Buddy Wing to try until the step or task is complete. But because we have no trackable quest, we have to resort to "Interact" which is a one-time best effort attempt. If it doesn't work, Buddy Wing assumes it's been done and moves on anyway (which is not good in this case). Destroying the supply boxes to get to the bonus boss is hard to do for this same reason.
Finally, any mob or boss fight featuring any mechanic other a simple fight can potentially break Buddy Wing. For example, Darth Serevin, the end boss, has a mechanic where he disappears and reappears periodically throughout the encounter. It is at that time that Buddy Wing may fail to resume fighting.
