Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    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
    I’ve seen AoS take ~12-24 hours
    Amadeusz Sadowski
    @amis92
    @capitaladot the refresh is scheduled each 12hrs, but the precise time varies. So in most cases one should start worrying after 12hrs passed.
    If you feel like investigating, take a look at which hour were latest updates published on Twitter. This should give you an idea at which times it runs (every 12hrs).
    Austin C.
    @capitaladot
    Oh, I see. Did not recall the timing. Mostly just "fire and forget".
    Earl Bishop
    @DrTobogganMD
    That's about right - but then you have to forget for at least 12 hours to be safe :p and then hope that appspot doesn't take a dump and lose the repo for a period of time.
    Andrew Bao
    @ThePatient
    Hi all, found a Battlescribe specific bug in the iOS app. Should I create an issue here https://github.com/BattleScribe/Release/issues or use the uservoice link in the app?
    OftKilted
    @OftKilted
    @ThePatient Release issues is a solid place for found issues. (I’ve submitted them there previously and had good response. Make sure you identify that it is iOS specific.) if you don’t mind the curiosity, what’s the issue?
    Andrew Bao
    @ThePatient
    I don't know if it is iOS specific, but I do know that it exists on iOS (haven't tested the other platforms). The issue is that melee and missile attacks with the same name don't both get displayed in the "View" screen. It displays one, but not both.
    OftKilted
    @OftKilted
    If you have them labeled the same then ... yeah ... it isn’t just iOS, it also exists on desktop. Typically from a catalog workaround perspective one would modify one of the attack names. (That had to be done for the Horrors in AoS as they had identical attack names.)
    Andrew Bao
    @ThePatient
    Ah. So should I create the issue in the data repo?
    OftKilted
    @OftKilted
    If you have multiple attacks with an identical name then only one of them will show up in the roster view
    Andrew Bao
    @ThePatient
    I've noticed it for SCE on the Knight Venator as well as the Prosecutors when outfitted with celestial hammers.
    OftKilted
    @OftKilted
    Sure. Sounds like a good case for a relatively ‘easy’ data fix. I’m not sure if the behavior is expected or not.
    (From a Battlescribe app perspective)
    Andrew Bao
    @ThePatient
    Given that the attacks have different ids it seems like the app should be able to differentiate, but I agree the data fix seems easier. I'll create the issue app side first and see what they say.
    OftKilted
    @OftKilted
    @amis92 Are you familiar with the Battlescribe feature where if a multiple profiles have the same name only one of them displayed in roster view?
    @ThePatient I’m pretty sure that the data file fix will be faster...
    Andrew Bao
    @ThePatient
    @OftKilted I agree, but I'm not really in a rush. Seems better to fix it systematically. I'll raise it. If they decide it's not worth fixing, I can always put in a pr on the data repo.
    OftKilted
    @OftKilted
    Here’s the side issue ... in a Battalion, where all the stats are lumped together having multiple versions with the same name can lead to substantial@confusion
    So, changing the profile name to identify the applicable unit will help users. Having multiple items with the same name ... not so much.
    Andrew Bao
    @ThePatient
    Are you saying if they change the app to display all the attacks with the same name but different IDs it will cause it to also duplicate battalion info display?
    OftKilted
    @OftKilted
    One would see multiple instances of “Celestial Hammer” in the Weapons list in a Battalion ... if both units were in the Battalion.
    With no identification of which goes to which.
    I’ll use the Horror Attack “Magical Flames” it’s a missile attack that has an identical name for all horrors (Pink/Blue/Brimstone)
    They all have different range and hit values.
    Without an identification that this profile is for Pink/blue/Brimstone etc... in a Multitudinous Host how would you know which one to use?
    They are all in one big block of attacks.
    (Users don’t care specifically about different ids)
    Andrew Bao
    @ThePatient
    Theres' a few issues there. 1) the attacks should probably be listed with the unit name. 2) I'm talking about two attacks of the same unit that have the same name but one is missile and one is melee (so both should definitely be included in both battalion and single unit roster displays). 3) I'm talking about the app's ability to distinguish the attacks as separate. Of course the user doesn't care about IDs.
    OftKilted
    @OftKilted
    @ThePatient It’s ... basically the same from a roster perspective. A single unit having attacks that are the same name but different values vs multiple units with attacks with the same name but different values.
    Literally speaking they are both “weapon attacks” with a naming difference for Melee vs Ranged in the “Weapon type”
    Field
    It isn’t a “Melee Weapon Attack” and a “Ranged Weapon Attack” type
    (Or melee vs missile)
    IF they were different profile types it might not be the issue. (But the data catalog didn’t configure them that way)