• Visit Rebornbuddy
  • [Plugin] A ChuckyEgg Attempt! - Party Dude Pro, breaker breaker roger smack 'em!

    Discussion in 'Plugins' started by ChuckyEgg, Oct 4, 2012.

    1. ChuckyEgg

      ChuckyEgg Member

      Joined:
      Jun 14, 2012
      Messages:
      635
      Likes Received:
      8
      Trophy Points:
      18
      ChuckyEgg's Party Leader Pro / Party Dude Pro​

      The Party Management Plugin with Inter-Bot COMMS

      "breaker, breaker, roger, smack 'em"

      NOT CURRENTLY COMPATIBLE WITH TRINITY
      Followers are unable to pickup loot they do not walk over

      INTRODUCTION

      Here it is, the advanced version of my co-op bot plugin.

      With this plugin you will be able to run parties of 2, 3, or 4 bots, either
      1. Fully AFK, with the party leader and followers under the control of the bot and plugin
      2. Or as a Follow.Me type of plugin, where you control the leader and the followers are controlled by the bot and plugin.
      This version of the plugin has a communication system that enables the bots to communicate with each other, although for now, and until more things are added, most of the communication is between the leader and its followers.

      PartyLeaderPro and PartyDudePro use a flat database to communicate with each other.

      COMMS database
      This is a flat database (text file), and needs for you the user to specify where it is to be held. This is done in the config windows of both PartyLeaderPro and PartyDudePro, and must be done in both, so that both plugins can make use of it.

      *** IMPORTANT ***
      • Start the leader from the menus, unless you are taking control of the leader, then you must start in-game.
      • Start the followers anywhere in-game (CombatBot appears to crash the game if started from menus!!!!)
      • Idle Timeout should be disabled or set very high for the followers, as we do not want them leaving game (results in a crash - need to resolve this)
      • Config part must be done and saved before starting the bots or a new game. Doing it during a game will cause problems.

      QUICK'ish START:

      Place PartyLeaderPro folder into the Plugins folder of the bot that will be the leader

      Place the PartyDudePro folder into the Plugins folder of the followers

      Configure PartyLeaderPro and PartyDudePro, being sure to set the same:
      • path to the database (must end with a \ )
      • name of the folder that will hold the database
      Profiles
      • load CombatBot for the followers
      • load whichever profile you want to run for the leader (Queen, Champ, profile manager, etc.)
      • If this is for a Follow.Me type run, then load CombatBot for the leader
      Conguration of plugins in image form
      View attachment 68867

      Enable the PartyLeaderPro plugin

      Enable the partyDudePro plugins

      Send your followers anywhere in-game (get them out of the menus)
      • It's best if you put the followers in-game somewhere when this is first run. I found that with the CombatBot loaded, and D3 still in the menus, DB and D3 would crash.
      Start the leader bot (PartyLeaderPro)

      Start the follower bots (PartyDudePro)

      That's it. Your leader will now send out invites, and as soon as all the followers have notified the leader, via the database, that they are present in the party, the leader will start the run.


      LONG WINDED START

      INTRO

      The plugin has 3 parts:
      1. PartyLeaderPro plugin
      2. PartyDudePro plugin
      3. COMMS database
      Each plugin consists of 4 files
      1. main plugin file (PartyLeaderPro.cs, PartyDudePro.cs)
      2. a config file (ConfigSettings)
      3. an XML script that represents the Config GUI (PartyLeaderPro.xaml, PartyDudePro.xaml)
      4. a file that deals with the communication between the party members and the comms database (LeaderComms.cs, DudeComms.cs)

      COMMS database: this is automatically created by the PartyLeaderPro plugin, and is used to pass information between the bots.

      SETUP:

      Place PartyLeaderPro into the Plugins folder of your leader.

      Place PartyDudePro into the Plugins folder of your followers.

      Configure PartyLeaderPro
      • select the # of bots that will be in the party
      • select whether or not to have the PartyLeaderPro make regular checks if anyone has left the party
      • Set the path to the location you wish to have the database. This must exist, and be accessible by the leader and the followers.
        • examples:
        • E:\Database\
        • C:\Temp\partyComms\
        • \\KINGDOM\sharedfolder\
      • Set the name of the folder that will hold the database. This does not need to exist, as PartyLeaderPro will create it.
        • e.g.
        • CommsCentre
        • DatabaseFiles
      Configure PartyDudePro
      • Set the path to the location you wish to have the database. This must exist, and be accessible by the leader and the followers, and be the same as you set in PartyLeadePro
        • e.g.
        • E:\Database\
        • C:\Temp\partyComms\
        • \\KINGDOM\sharedfolder\
      • Set the name of the folder that will hold the database. This does not need to exist, as PartyLeaderPro will create it. It must be the same as you set in PartyLeaderPro
        • e.g.
        • CommsCentre
        • DatabaseFiles
      Followers
      1. Use the CombatBot profile, as they do not need to follow a profile, because the PartyLeaderPro will tell them where to go.
      2. Make sure the PartyDudePro plugin for all the followers is enabled
      Leader
      1. Load up whatever profile or profile manager you wish to use.
      2. Make sure the PartyLeaderPro plugin is enabled
      Send your followers in-game (get them out of the menus)
      • It's best if you put the followers in-game somewhere when this is first run, at the very start of a run. I found that with the CombatBot loaded, and D3 still in the menus, DB and D3 would crash.
      Start the leader bot

      Start all the follower bots

      PartyLeaderPro will now invite everyone to the party, and the run will start once everyone has joined.
      The followers will inform the leader that they have successfully joined.

      DONE :)

      Sources of information used to good effect in the creation of this plugin:
      - MyBuddy.Local aka Follow me - Author: xsol
      - GilesCombatReplacer - Author: GilesSmith
      - JoinMe! - Author: readonlyp


      USEFUL AND COMPATIBLE PLUGINS

      CIGGARC plugins
      Atom
      RadsAtom - precursor to Atom




      DOWNLOAD AREA
       
      Last edited: Nov 29, 2012
    2. ChuckyEgg

      ChuckyEgg Member

      Joined:
      Jun 14, 2012
      Messages:
      635
      Likes Received:
      8
      Trophy Points:
      18
      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.
       
      Last edited: Nov 29, 2012
    3. bio72301

      bio72301 New Member

      Joined:
      May 24, 2010
      Messages:
      95
      Likes Received:
      0
      Trophy Points:
      0
      AHA! First! --Trying now
       
    4. CooleRnax

      CooleRnax New Member

      Joined:
      Dec 5, 2011
      Messages:
      98
      Likes Received:
      0
      Trophy Points:
      0
      Last edited: Oct 4, 2012
    5. Looted

      Looted New Member

      Joined:
      Dec 26, 2011
      Messages:
      27
      Likes Received:
      0
      Trophy Points:
      0
      My partydude crashes diablo after accepting invite (not from menus, from ingame).
       
    6. CooleRnax

      CooleRnax New Member

      Joined:
      Dec 5, 2011
      Messages:
      98
      Likes Received:
      0
      Trophy Points:
      0
      private string commsFolderPath = @"..\";
      private string commsFolderName = "CommsCentre";
      private string commsDirectory = @"..\CommsCentre";
      private string partyState = @"..\CommsCentre\PartyState";
      private string gameState = @"..\CommsCentre\GameState";
      private string partyMemberID = @"..\CommsCentre\PartyMemberID";
      private string pathCoordinates = @"..\CommsCentre\PathCoordinates";

      That's why i get second folder created
       
    7. bio72301

      bio72301 New Member

      Joined:
      May 24, 2010
      Messages:
      95
      Likes Received:
      0
      Trophy Points:
      0
      OK --after some digging --- the Party Leader Pro isnt making the folder in the right place AND it makes it named Commcenter no matter what you change it to.
      Like I wanted it in D:\Comms\Database\
      So I set it up using the following screenshots so I can demonstrate the error

      Here I set it up the way I want it
      screen1.jpg


      Notice the time stamp on the folder creation of Commscenter, which isn't even anywhere in my config.

      screen2.jpg

      The leader doesnt seem to like to follow folder directions
       
    8. ChuckyEgg

      ChuckyEgg Member

      Joined:
      Jun 14, 2012
      Messages:
      635
      Likes Received:
      8
      Trophy Points:
      18
      Very strange

      I just grabbed the files from this thread, just-in-case I had uploaded the wrong version, and done a few runs with no problems at all. My party is currently running in a party of two on the Queen/Sarkoth run. No looping, nothing strange as yet.

      Anybody else having problems ?
       
    9. bio72301

      bio72301 New Member

      Joined:
      May 24, 2010
      Messages:
      95
      Likes Received:
      0
      Trophy Points:
      0
      Hey chuck .. i'd try changing some folder names --thats when mine went fubar'd
      The code that Cool posted also seems to be the only reference to the exact folder name that mine is creating

      I also pm'd u my skype in case you want assistance in bug testing
       
      Last edited: Oct 4, 2012
    10. ChuckyEgg

      ChuckyEgg Member

      Joined:
      Jun 14, 2012
      Messages:
      635
      Likes Received:
      8
      Trophy Points:
      18
      Okay, I just got a problem,

      3 man party, invites everybody, but one of the dudes did not update the the database to say it had joined the party!!

      Dammit!
       
      Last edited: Oct 4, 2012
    11. ChuckyEgg

      ChuckyEgg Member

      Joined:
      Jun 14, 2012
      Messages:
      635
      Likes Received:
      8
      Trophy Points:
      18
      Hmm, is the Idle Time set to a low amount ? It needs to be very high, so that it does not time out, for the followers, that is. The leader should be low, in order to guard against suck situations.
      If the idle time just happened to timeout it will made the char leave to the menus, and that will crash the system.

      I don't think I stated that the Idle Time for the followers needs to be disabled or set to a very high level!
       
    12. Looted

      Looted New Member

      Joined:
      Dec 26, 2011
      Messages:
      27
      Likes Received:
      0
      Trophy Points:
      0
      I'll give it a try, thanks.

      EDIT: Yup, that did the trick. Dude joins correctly now.

      Further observations. Dude lost the leader almost instantly in bastion keep, could port from there so just stood still. Seems like he cant find the leader at all, just keep porting over and over again.
       
      Last edited: Oct 4, 2012
    13. CooleRnax

      CooleRnax New Member

      Joined:
      Dec 5, 2011
      Messages:
      98
      Likes Received:
      0
      Trophy Points:
      0
      ChuckyEgg try relocate your db folders
       
    14. ChuckyEgg

      ChuckyEgg Member

      Joined:
      Jun 14, 2012
      Messages:
      635
      Likes Received:
      8
      Trophy Points:
      18
      I think I had forgotten to set the path in that char's config!

      I just rand it again in Queen/Sarkoth, Act 1 champ farming, and Act 2 champ farming, and it's running along nicely.
       
    15. ChuckyEgg

      ChuckyEgg Member

      Joined:
      Jun 14, 2012
      Messages:
      635
      Likes Received:
      8
      Trophy Points:
      18
      Ah, yeah, it can't TP in a big part of Bastion's Keep :(

      I need to look into that, as it needs to find its way to the banner to rejoin the party.

      Hey, Looted, are your bots running fine with that plugin, besides the Bastion Keep issue ?
       
    16. ChuckyEgg

      ChuckyEgg Member

      Joined:
      Jun 14, 2012
      Messages:
      635
      Likes Received:
      8
      Trophy Points:
      18
      I'm on IRC with Bio72301, and attempting to reproduce that issue...
       
    17. Looted

      Looted New Member

      Joined:
      Dec 26, 2011
      Messages:
      27
      Likes Received:
      0
      Trophy Points:
      0
      Unofortunately not. After i manually helped the dude get to a location he can teleport from, he did, used the banner, then instantly lost the leader again (and then just kept looping tp-banner). After that i tried to restart it to create the database again, but got the accept invite crash issue. Also, few suggestions:
      1. Maybe try keeping the plugin config in the demonbuddy settings folder, not in the plugin folder. Dbreloger injects the plugins from a separate folder after db logs in, so the settings are overwritten each time. The workaround is to put plugin with the settings saved in the dbreloger plugins folder, so it gets copied with the settings. Moving the settings to settings folder in db would eliminate this problem for people using relogger.
      2. Further down the road it would be nice for the plugin to be fully afkable (the previous version pretty much is, apart from bots desychronizing when doing town runs, and also when one finishes some time before the other). Apart from the bugs, it would be nice to implement a safety feature ? when bots cant find eachother for a long time, they just run the standard solo profile (so the party creation part doesn't loop).
      3. The golden mean would be to combine approaches from both version of the plugin ? bots run the profiles independently, but synchronize townruns, and make sure both are running the same profile at a time (atm after creation of a new game, one goes skycrown, and one core of arreat, which he didn't finish before).

      Im out of patiencie today (and probably close to input limit) so i'll continue testing tommorow. Great work so far though, love the plugin, it cuts my dph by half if not more, allows to use much more offensive builds, and increases gph by 30% at least. Cheers!
       
    18. ChuckyEgg

      ChuckyEgg Member

      Joined:
      Jun 14, 2012
      Messages:
      635
      Likes Received:
      8
      Trophy Points:
      18
      My bad...

      It looks like I uploaded the wrong version of the plugin... :(

      Firing squad at dawn ?
       
    19. ChuckyEgg

      ChuckyEgg Member

      Joined:
      Jun 14, 2012
      Messages:
      635
      Likes Received:
      8
      Trophy Points:
      18
      Proper version has now been uploaded :eek:

      I will now assume the position.... paddles, canes, and big clubs with nails in at the ready :eek:

      ------
      I do need to still stop the plugin from running when the bot has been stopped, but everything else should work.

      -----
      don;t mind the spamming of the bot, I'll strip the excess ones out in a mo.
       
      Last edited: Oct 4, 2012
    20. CooleRnax

      CooleRnax New Member

      Joined:
      Dec 5, 2011
      Messages:
      98
      Likes Received:
      0
      Trophy Points:
      0
      Nothing changed for me =(
      Still TP loop
       

    Share This Page