Comments

• ChrisIceBox

  January 2018

  You can set it to any value if you set it using an ActionList parameter.  Place the Action in a separate ActionList, and create a new Float parameter at the top of the ActionList's Inspector.  Then assign that parameter to the Engine: Change timescale Action's Timescale value.
  
  Then, call the Action using the ActionList: Run Action.  When you do, you'll be able to set the value of that float parameter - and hence the timescale - to an unrestricted value.
  
• Alarconte

  March 2019

  I was searching just for this information. I don't know if it's me, but after following the guide, it seems like Change Timescale doesn't accept changing the float by parameter. I'm using right now AC 1.65.2.

  If in that version it didn't work, it is hard to upgrade the code? I'm not updating AC anymore at this stage.

  PS: The parameter is well set, as allows me to change Engine: wait time, for example, for a parameter, but not change timescale.
• ChrisIceBox

  March 2019

  @Alarconte: Whoops! The Action hasn't in fact been upgraded to allow for setting through parameters. Thank you for the alert.

  I will upgrade this Action as part of the upcoming update. You should, however, be able to import only the ActionTimescale script into your project in order to see the change - backup your project beforehand, however.
• Alarconte

  March 2019

  that's good to know, and it's a pleasure to help.
• Alarconte

  March 2019

  You know, preparing some automated actions (like handy new item notifications), I've seen parameters are also not configured for documents, **As far as my version goes, and I failed to find a changelog for all more new versions than mine **, as inventory items are a type of parameter, but documents are not.

  I'll work without that for now but it will be handy if is on the engine.
• ChrisIceBox

  March 2019

  A new parameter type, Document, is also planned for the next release to allow parameterisation of the Document Actions.