by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Earl Bishop
    @DrTobogganMD
    so hiding based on equip would fail
    Amadeusz Sadowski
    @amis92
    :D Yeah, that was the problem!
    Earl Bishop
    @DrTobogganMD
    I mean, it was clean that way
    :p
    @Jonskichov Then my request, while I'm sure I could use it, is no longer a necessity for me :p
    Jon Taylor
    @Jonskichov
    Haha nice one :)
    I hate bugs, but I love the moment of enlightenment when you finally find the solution :+1:
    Amadeusz Sadowski
    @amis92
    :bug: hello there
    Earl Bishop
    @DrTobogganMD
    Thanks for pointing that out amis
    41 additions and 378 deletions
    :D I love Deletions.
    Hey Jon, I see this every now and then in the DIFFs
    • <entryLink id="eb5c-5150-1e9d-f961" name="!Character" hidden="false" targetId="5973-c86d-b500-4a14" type="selectionEntry">

    • <entryLink id="eb5c-5150-1e9d-f961" name="Character" hidden="false" targetId="5973-c86d-b500-4a14" type="selectionEntry">

    I changed from !Character to Character over a week ago when I released the file
    Any idea why the entry link name just now changed?
    Not that this has any affect on the file at all, just curiosity on my part
    Jon Taylor
    @Jonskichov
    Huh. Assuming it was saved correctly in your local file, I have no idea. I wonder if GitHub just wasn't flagging the change?
    Earl Bishop
    @DrTobogganMD
    Yea, it was in the local file in v ... 11? just uploaded v15 and noticed that in the diff
    no issues, just outright curiosity
    tekton
    @tekton
    had you not click on that entry in the editor in a long time? that seems to be it for me most of the time.
    Earl Bishop
    @DrTobogganMD
    That could be - I did touch it this time when cleaning up the relic logic
    The entry was changed a while ago, but I just poked the link to it in the individual knights, probably for the first time in a bit
    Amadeusz Sadowski
    @amis92
    @Jonskichov Links don't update their name attribute at all (including during the creation). They do update only once you "click"/focus the three view on them (which requires clicking something else and back on the link when creating). Don't know if that counts as a :bug:, but it's there :)
    Austin C.
    @capitaladot
    Filed a bug for the immediate null point error I receive trying to load the HH files.
    Jon Taylor
    @Jonskichov
    ICYMI I put out build 110 that fixes the hang when changing the CatalogueLink target... dumb mistake, my bad ;)
    Joe Beddoe
    @CrusherJoe
    :+1: Thank you @Jonskichov
    Austin C.
    @capitaladot
    Nice!
    So, working on linked catalogues in earnest.
    OftKilted
    @OftKilted
    @Jonskichov Run into an editor issue on 'current release' where if you set modifiers and conditions on a force type (to modify name or points maximums based on a selection) the editor won't show the modifiers/conditions when the GST is reopened. #18
    The actual data appears to still be in the file, but the data editor doesn't show it as existing.
    (And you can make valid rosters, and the functionality from the modifiers still seems to be there ... just doesn't show up.)
    Earl Bishop
    @DrTobogganMD
    @Jonskichov Any chance of allowing conditionals based on count of specific forces in a roster?
    IE: Increment X for every instance of Force Y in roster. If you do it currently, it increments X for every selection inside any force Y in the roster.
    Austin C.
    @capitaladot
    +1; this would really help with a few things.
    Earl Bishop
    @DrTobogganMD
    It seems that the way I'm thinking of is how it should work ... it seems that way logically, so I don't know if it's a bug or intended behavior
    Austin C.
    @capitaladot
    It is a little confusing to glean the intent to count instances of a container (like a Force) vs. the number of selections inside it. I think it actually counts the number of selections inside the given Force.
    Earl Bishop
    @DrTobogganMD
    That is how it currently works yes
    I’d love if it worked how I requested or an option to do so was added
    Austin C.
    @capitaladot
    Agreed; just stating the current behavior is counter-intuitive.
    Joe Beddoe
    @CrusherJoe
    @Jonskichov dunno if this was mentioned previously or not, but 2.01.15 Windows the "Unsaved" warning in top right never goes away
    Austin C.
    @capitaladot
    Busted on MacOS, too.
    Austin C.
    @capitaladot
    Hey @Jonskichov looks like the release bot isn't pickup up an initial release from a new repo.
    Amadeusz Sadowski
    @amis92
    Austin C.
    @capitaladot
    Am I see a cached page lol?
    OftKilted
    @OftKilted
    Try a different browser
    Austin C.
    @capitaladot
    It is there now, you're right! Maybe something had tipped over and was quietly fixed?
    OftKilted
    @OftKilted
    browsers will often do an eventual recheck for new page content when navigating back to a site
    Austin C.
    @capitaladot
    Did the release about 5:00gmt and still didn't see it at like 13:00gmt.
    OftKilted
    @OftKilted
    I wouldn’t worry unless a release is over 24 hours old