Skip to content

Releases: luvies/TaledensInvManagerUpdated

v1.7.7

08 Mar 00:11
c3de487
Compare
Choose a tag to compare
  • Added parachute block support (#25)

v1.7.6

04 Mar 19:36
049c786
Compare
Choose a tag to compare

Release v1.7.3

04 Mar 21:55
51f2685
Compare
Choose a tag to compare

The next minor release for TIM.

It contains the following adjustments & fixes:

  • Reset default update frequency to 100 ticks
  • Added real-time update frequency option
    • By setting the USE_REAL_TIME option to true, TIM will update using the number of milliseconds given by UPDATE_REAL_TIME
    • The deault is still to use game ticks, so you have to manually enable the real time update frequency option
    • Defaults to updating every 1 second
  • Set MAX_RUN_TIME to 35 milliseconds by default
  • Doubled assembler and refinery default item requests
    • Assembler ite requests now default to 10 if no speed it known

Release v1.7.2

04 Feb 17:45
Compare
Choose a tag to compare

The next minor release for TIM.

Changes:

  • Added execution limit checking to item allocation process steps (these are steps 7 and 9, but step 9 seems to be the most affected by this)
    • Due to this, large and complex setups might have a responsiveness drop, however TIM will become MUCH less resource intensive
  • Set run frequency to every 10 ticks rather than every 100
    • This will improve responsiveness overall, and should affect how well large/complex setups perform
    • The only issue with this, is that on lower end PCs and worlds with a lot of PBs running TIM, there may be some performance drops
    • To combat this, I've added a parameter near the top to allow you to edit the update frequency
  • Improved exception handling
    • If something goes wrong, you can give me the exact terminal output, and I'll know much better what went wrong
  • Added support for some mods

Release v1.7.1

20 Jan 18:44
Compare
Choose a tag to compare

A bugfix release addressing the following issues:

  • If the script detected that it was over the execution limit, but had completed all steps anyway, it would abort early and cause a crash on next call

Release v1.7.0

19 Jan 22:41
Compare
Choose a tag to compare

This is the next minor release for TIM. These are the following changes:

  • Rewrote argument parsing completely
    • Will ignore TIM_Version
    • cycle argument removed
    • Each argument should be on a new line in one of the following formats:
      • arg → for arguments without a value
      • arg=value → for arguments with a value
  • Added dynamic execution pausing
    • No longer need the cycle argument, as TIM will now cancel processing until the next call if exeuction time has gone above 30ms
    • Should mean that the random script complexity errors should not happen any more
      • Warning: Some process steps take up an enormous amount of the processing allocation (mainly step 9 from what I can tell), meaning that some steps can go way over the limit
        • I cannot stop this at the moment, if it happens then try to reduce the complexity of the grid system
        • I am working on added exeuction length checks inside some processing steps, so they can put off some of their exeuction until the next call, which should solve most of this problem