Quantcast

Jump to content


Photo

[Auto Players] Cheat! Auto Player


  • Please log in to reply
228 replies to this topic

#226 Aerodactyl

Aerodactyl
  • 41 posts

Posted 15 June 2016 - 08:43 PM

 

I keep getting this error whenever I try to start cheat:
 
Traceback (most recent call last):
  File "/cdx/svn/checkout/core/trunk/Program Manager/ProgramManager.py", line 1192, in run_with_except_hook
  File "Programs/1004/AutoCheat.py.nc", line 196, in run
  File "Programs/1004/AutoCheat.py.nc", line 93, in getPlayerInfo
TypeError: unsupported operand type(s) for +: 'int' and 'str

 

 

Not sure if this'll fix your problem, but you can try starting a cheat game manually and then start the bot.



#227 normlacasse

normlacasse
  • 1 posts

Posted 13 October 2016 - 10:25 AM

Traceback (most recent call last):
  File "/cdx/svn/checkout/core/trunk/Program Manager/ProgramManager.py", line 1192, in run_with_except_hook
  File "Programs/1004/AutoCheat.py.nc", line 196, in run
  File "Programs/1004/AutoCheat.py.nc", line 93, in getPlayerInfo
TypeError: unsupported operand type(s) for +: 'int' and 'str'
 
 
doent work anymore error everytime tried reinstalling as well


#228 jaredyne

jaredyne
  • 1115 posts


Users Awards

Posted 15 October 2016 - 04:34 AM

 

Traceback (most recent call last):
  File "/cdx/svn/checkout/core/trunk/Program Manager/ProgramManager.py", line 1192, in run_with_except_hook
  File "Programs/1004/AutoCheat.py.nc", line 196, in run
  File "Programs/1004/AutoCheat.py.nc", line 93, in getPlayerInfo
TypeError: unsupported operand type(s) for +: 'int' and 'str'
 
 
doent work anymore error everytime tried reinstalling as well

 

 

I was having that same error, until I followed @Aerodactyl's advice, you know, in that one post, directly above yours. Autoplayer runs fine after that. Have you tried manually starting a game first?



#229 Purrina

Purrina
  • 92 posts


Users Awards

Posted 04 September 2018 - 05:59 PM

I was getting this same error in Cheat!, and I was happy to come here and find there was a workaround.
 
I would like to thank @Aerodactyl for posting a solution.
and also thank @jaredyne for reminding us to read the thread before posting :D



0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users