I keep getting the "unresponsive script" trying to play a game and VERY tired of this error

This is the slow script error, and it gets thrown when the content that Flash Player is running uses an inordinate amount of CPU time.  When that happens, we intervene and throw the dialog instead of letting the content hang the browser instance or machine.

You have a few options at your disposal, but they basically come down to freeing up resources:

• Reboot the machine to address any issues related to memory fragmentation.  Flash needs RAM to be both available and contiguous.  The longer a system is running, the more likely it is that RAM allocations are fragmented in a way that makes them less useful.
  
  (Flash Player is designed to run on a wide variety of machines, and trades performance for RAM usage.  Where plenty of contiguous RAM is available, Flash will do more caching to minimize time spent processing.  When RAM is constrained, Flash will lean more heavily on the CPU as it repeatedly processes things that would otherwise be cached.)
  
  
  
• Close all of your open applications and other browser tabs when you're playing that game.  Depending on the browser in use, all of those other tabs are doing "stuff" that competes with the game for resources.  The less contention there is for system resources, the better the application you care about is going to perform.
  
  
• Experiment with other browsers (some have less overhead than others)
  
  
• Report the problem to the game developer.  Adobe provides free profiling tools (Adobe Scout) to content authors, which allow them to identify slow code in their games.  In most instances, developers can then optimize the most egregious hot-spots in their code to prevent the slow-script dialog from popping up.  In the rare event that there's an underlying language/virtual machine issue that needs to be addressed, the content author is in the best position to identify and report that problem (and they're welcome to reach out to me directly via private message, by clicking my name above).
  
  
• Finally, since the root of the issue here is CPU contention, a faster machine and/or more RAM may help, but it's really dependent on why the content is slow in the first place.  Again, the content author is best positioned to debug that.

Thanks!