Changelog
v1.0 (4th of October, 2012)
- Original release of plugin
v1.0.1 (5th of October, 2012)
- (Bug Fix) The plugin now loads the contents of the configuration file when the plugin is enabled and at the start of a new game.
v1.0.2 (5th of October, 2012)
- Leader death - PlartyLeaderPro now reloads the profile, instead of creating a new game - Bio72301 made a good point, that you don't really want to waste that nephalem stack)
- Follower death - wait times reduced during the death moment, therefore it should click on the rez button in quick time.
v1.0.3 (8th of October, 2012)
-
Leader Death - this has been added to the comms system, so that the leader will now rez properly
-
Demonbuddy Start/Stop button - leader now TPs to town and reloads the profile, if the bot is stopped and restarted during a run
-
Party formation - this can now be done either from menus or in-game, without the system crashing
-
Crashing & transition of followers between games - this has now been solved, and should not occur due to anything the plugin does (care of code from the Join Me plugin)
-
Follower combat/looting - followers are no longer stuck to the leader's butt. They will loot everything. They will also fight properly, but not as a team, yet.... (near future objective)
-
CombatBot profile - included in the zip are a number of CombatBot profiles, each for a specific act and difficulty (Act I, II, III, IV - Normal, Nightmare, Hell, Inferno). This will stop the crashing of the system if the follower goes to the menus before it should (helpful input by CooleRnax).
v1.0.4 (10th of October, 2012)
-
Config window DONE button - this now creates the database and its folder. It should have done this originally! bad, bad me!
-
Out Of Range of Leader - if the leader comes back into range, the follower will stop trying to get back to town. This is dependent on how far it has got in the TP attempt.
v1.0.5 (12th of October, 2012)
-
Party Creation - an error has been fixed that caused the formation of the party to sometimes fail (flag was being set to true indicating that the follower had successfully acquired its party ID, when it had actually failed to do so).
v1.0.5 European Numbering (15th of October, 2012)
-
TP - "I've Lost the Leader" on start - Problem found to be due to some countries using commas instead of periods in floats. I have included a European version of the plugin for countries that have this numbering convention.
v1.0.6 (23rd of October, 2012)
-
Multi-Region Numbering Convention - Now using a # to separate the coordinates. Initially I had a comma, which obviously caused problems for countries that use commas to separate decimals and integers. Then I used minus symbols, but that resulted it minus valued coordinates being converted to positive. Now I am using the # symbol
v1.0.7 (24th of October, 2012)
-
Config Windows - A check is made on the existence of the path and folder before the user is allowed to leave the config windows (PartyLeaderPro checks on path existence, PartyDudePro check on folder existence)
v1.0.8 (25th of October, 2012)
-
Boss Encounters and TP'ing - The Town Portal has now been disabled for the follower, when in a Boss area
v1.0.9 (29th of October, 2012)
-
Follower Death - not rezzing - The follower is now prevented from checking for lost leader if they are dead. If the follower was dead when they went out of range of the leader, the follower ended up getting stuck as the code ended up in a perpetual loop.
Pre-release changes/additions:
1.0.8.3 - added Crystal Colonnade and Leroric's Passage to Boss Encounter code
1.0.8.4 - OnBotStart and OnEnabled now initialises all the variables, thus allowing the bots to be stopped and restarted during a run without having to reform the party.
v1.0.10 (1st of November, 2012)
-
Bot or Manual Control of Leader - User can now choose either bot control or human control of the leader from the config window (New PartyLeaderPro Config Window).
Pre-release changes/additions:
1.0.9.1 - Dude#State access removed
Leroic's Passage and Cain's House added to Boss Encounter code
1.0.9.2 - Party Formation made more stable - possible risk (small chance) of party formation reported as being complete when it was not, now fixed.
1.0.9.3 - Leader no longer attempts to TP to town when bot is started.
OnBotStart and OnBotStop added to PartyDudePro, so followers will now initialise variables when the bot starts up, even during a run (geared towards human control of the leader).
v2.0.0 (3rd of November, 2012) **** POSSIBLE FAULTS - please use the latest 1.0.10.x ****
-
Portal Usage - The followers can now use the portals (they still won't use them if the portal is too far away). Therefore they do not need to head back to town to catch up with the leader, when the leader goes through a portal (includes portal stones)
-
Party Formation - It was found that the number of party members was not, on occasion, loaded up correctly from the config window, thus resulting in the party either not being successfully formed (chars just standing there doing nothing) or not all members being invited. This has been fixed.
I figured Portal Usage being so key, this required a major version increase, therefore version 2
v2.0.1 (7th of November, 2012) **** POSSIBLE FAULTS - please use the latest 1.0.10.x ****
-
Portal Usage - Portal stone usage
tested and working!
-
Boss Encounters - Adria (Act II, after Mahgda and before Kulle) added to Boss Encounters
v2.0.2 (9th of November, 2012) **** POSSIBLE FAULTS - please use the latest 1.0.10.x ****
-
Portal Usage - Increased the search range for the portals from 11 to 50, in order to allow for stragglers (followers lagging behind)
-
Manual Control of Leader - The leader will now no longer TP to town when it dies if under manual control (this is set in the PartyLeaderPro config window)
v2.0.3 (11th of November, 2012) **** POSSIBLE FAULTS - please use the latest 1.0.10.x ****
-
Follower Boss Portal Usage Stuck issue - Fix applied for when the follower got stuck when accessing a boss portal (Azmodan et al), and the leader left the game in order to create a new game and party.
Now the follower will not interact with the portal, but instead TP back to town and wait for invite to new group.
v2.0.4 (14th of November, 2012) **** POSSIBLE FAULTS - please use the latest 1.0.10.x ****
-
Follower getting stuck on Azmodan's portal! - Okay, previous version 2.0.3, did not actually fix this! Now it is fixed!
Now the follower looks for the Local Area and if it's in the area that has the Azmodan portal, it then looks to see how far the portal is from the follower. As soon as the follower gets within 100 of the portal it disables portal usage.
If the group is actually still to take on Azmodan, the leader will activate the portal and the follower will accept the Boss Encounter invite.
I will add more pre-boss portal areas soon. Right now it only has Azmodan's.
v2.0.5 (15th of November, 2012) **** POSSIBLE FAULTS - please use the latest 1.0.10.x ****
-
Portal Usage/Lost Leader/TP to rejoin party - The algorithm that decides what to do has been completely re-written.
v2.0.6 (16th of November, 2012) **** POSSIBLE FAULTS - please use the latest 1.0.10.x ****
-
Party Disbanding after LeaveGame - The leader now leaves the group when it leaves the game, at the end of a run.
I'll look into how to make this work when the party stays intact. Currently it brings up errors when trying to create a new game if the party is not disbanded.
v2.0.7 (17th of November, 2012) **** POSSIBLE FAULTS - please use the latest 1.0.10.x ****
-
File Access and Threading - File access that occurs during the actual run, now execute in their own thread. (hopefully speeds things up a bit)
**** crash issues ****
v1.0.10.1 (18th of November, 2012)
-
Non Portal Usage with Leave game and party - Added a version of the non portal usage version of the plugin with the ability leave game and party.
Added this due to the recent infestation of gremlins in the version 2.x.x of the plugin!
Non portal version - followers/dude cannot use them
v1.0.10.2 (19th of November, 2012)
-
Party Formation Fault Fixed - This fix is the one applied to 2.0.0. It occurred due to the value for the total number of party members differing between the config window and what the plugin used. Basically, the value was not being set properly within the plugin to reflect what was in the config window.
Non portal version - followers/dude cannot use them
v1.0.10.3 (19th of November, 2012)
-
Boss Encounters - Boss Encounters fully coded for all bosses that the party will fight.
-
Azmodan - Dudes will not try to interact with Azmodan's portal (other boss areas to be added later).
-
Human control of leader - Leader will not TP if it dies, if it is under manual control.
Non portal version - followers/dude cannot use them
v1.0.10.4 (19th of November, 2012)
-
Crash Fix (not the original crashing) - Problem and cause discovered by Morfious. Problem was that a variable was acquiring a value of nul and there were no guards against that. It was being incorrectly instantiated.
Non portal version - followers/dude cannot use them
v1.0.10.5 (20th of November, 2012)
-
Distance of Dude from Leader - You can now set the distance of the dude from the leader, and it will attempt to maintain this during the run. You can set a value in the range of 0 to 100. Default is 0.
Non portal version - followers/dude cannot use them
v1.0.10.6 (23rd of November, 2012)
-
Dude death - Altered the death handling of the dudes, as I noticed they could end up stuck and not rez themselves. This is the same fix that was applied in another version, but was missed here after having to go back to an earlier version of the plugin.
-
Code Execution Optimised - code execution optimised slightly. No repetition of calls per pulse for things like is the dude InTown, IsDead, LostLeader. These sort of calls are only made once per pulse and the result stored, and the stored value is then used for the rest of the pulse().
Non portal version - followers/dude cannot use them
v1.0.10.7 (25th of November, 2012)
-
TP'ing / Lost Leader - Error was made in 1.0.10.6, which resulted in TP'ing not occurring in certain situations. This has been fixed.
I had used a variable when it should have been a method call, to see if the character's location had changed (IsInTown).
-
Use of Leader's Banner Sped Up - The bot will now use the banner super fast, once it has the character in town. I removed a couple of pauses/waits.
Non portal version - followers/dude cannot use them
v1.0.10.8 (28th of November, 2012)
-
Portal Usage back in place - The dudes can now use the portals again.
-
More code optimization - The PartyDudepro.cs file now uses static variables and methods, and all use of parameter passing has been removed. This will be applied to the other files of the plugin in the next version.
PORTALS BACK IN USE
v1.0.10.9 (29th of November, 2012)
-
Dudes/Bosses/Rezzing - Dudes/followers will now not attempt to rez themselves when they die during a boss encounter.
-
Dudes dancing around leader - Dudes/followers will now no longer dance/run around the leader when they get close to it.
-
More code optimization - Code optimization applied to PartyLeaderPro.cs (static variable/methods, etc)
PORTALS BACK IN USE
IF YOU DON'T SEE THE DOWNLOAD AVAILABLE THEN HANG ON A BIT ... UPLOADING IN A MO
STILL TO DO / ISSUES
1 ) Team combat - get the bots to work as a team
2 ) Arelog - make this plugin compatible with Arelog, and other reloggers
3 ) Synchronize town runs (1 goes, they all go - first full instigates town run event...)
4 )
TRINITY INCOMPATIBILITY ISSUE - Followers if using Trinity, will not pickup loot unless they walk directly over it
New Fix Idea - search for nearby loot, if there is any, then do not attempt to follow the leader
5 ) RadsAtom - get the followers to go to the menus when the leader takes a break (leader uses RadsAtom, followers do not, but they follow what the leader does)
6 ) Follower Not in Party - (an idea by tesslerc) - allow the follower to run a full profile if they are not in a party, and while in a party to use a CombatBot profile - Add this to the config window (CombatBot profile location - Backup profile location)
7 ) Party formation and going from game to game - have the party stay intact when moving between games, so that party creation need only be done once.
8 ) Plugin causing lagging - possibly due to constant file access - set the file access call up with their own thread.
9 ) Option to deactivate bot controlled combat, so that people using things like ISBoxer can control the combat themselves.
