Forum Discussion

IrvTheCurve's avatar
3 years ago

Script to enlarge windows like "Ranking" and "Roster"

With the recent update, I had to update my scripts but in the process I seemed to have lost the ability to see windows using all of the vertical space available. I looked at my old individual scripts...



... and was able to successfully move over to using the "CnCTA SoO (SinsofOmission) SCRIPT PACK".

Does anyone know if there is a script in this pack or outside of it that can still do this?

Here is an example of the window I am referring to ... I could have sworn this was used all of the vertical space before the update. I don't see anything in the new script pack directly related to this.



  • Your infernal wrapper is not the latest one in the SOO pack and it includes code that is required for many scripts to work.

    Check again the scripts you've installed from the SOO pack and see if you've missed anything else that needs updating.
  • Thanks for the feedback @gamerdruid. I am running the latest version of SOO which was updated for Firefox on Sept 28th. It has infernal wrapper v1.51 ... is there a newer version than that?


  • The first post showed the IW was 0.39xxxxxxx. The 1.51 is the latest I am aware of.

    Could the use of the screen real estate change be because of a change in zoom level or overall screen resolution rather than a script?

    I ask because I get this:

    when I view the same information as you.

    I'm viewing my screen at 67% zoom level @ 1920x1080 on a large monitor. I'm not aware of having a script installed to make use of more screen real estate.
  • "gamerdruid;c-2222412" wrote:
    The first post showed the IW was 0.39xxxxxxx. The 1.51 is the latest I am aware of.


    Ah, yes ... those were the old ones I have since replaced. :smile:
  • I've narrowed this issue down and it is related to a script conflict within the SOO pack. I disabled everything but the infernal wrapper and this issue went away. I started enabling scripts after that and everything is still working. Sorry for the bother ... if i can find out the conflict, I will post a defect on GitHub.