search

Bungie-net / api

Resources for the Bungie.net API
Other
1.22k stars 92 forks source link

Any chance of a better Seasonal Artifact screenshot? #1086

Open NigelBreslaw opened 5 years ago

NigelBreslaw commented 5 years ago

The seasonal artifact image is without the eye powered up and looks quite sad. Any chance this could be updated as it is such a cool part of Shadowkeep?

https://data.destinysets.com/i/InventoryItem:1387688628

Screenshot 2019-10-10 at 10 59 01
vthornheart-bng commented 5 years ago

Ooh, good question - so the reason why it's the sad and unpowered one has to do with how we generate the screenshots.

I'll log a bug on it, as this does feel like one that'd be worthy of getting a better one-off screenshot for: but there's another pressure, which is that if we start making custom screenshots for items we could be setting ourselves up for a lot of work if more "statefully changing" items like this appear in the future. I'd be up for at least doing this one, but if we get a lot of these I can't promise that we'd have the resources to keep it up as a policy!

justrealmilk commented 5 years ago

Maybe you could do something with https://www.bungie.net/7/ca/destiny/bgs/seasons/VEye.png? It's a straight on angle but heh

vthornheart-bng commented 5 years ago

I filed the bug, but I need to warn that it's likely a low enough priority that it's going to end up in the great and terrible bug backlog. :(

floatingatoll commented 5 years ago

https://www.svg.com/169042/destiny-2-shadowkeep-how-to-get-the-seasonal-artifact/ Has one that’s really well lit, but I don’t know if it’s an in game screenshot, a Bungie marketing promo image, or something they made up.

On Oct 10, 2019, at 10:34, Tom Chapman notifications@github.com wrote:

 Maybe you could do something with https://www.bungie.net/7/ca/destiny/bgs/seasons/VEye.png? It's a straight on angle but heh

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

vthornheart-bng commented 5 years ago

The act of generating a new screenshot isn't the problem as much as turning part of our automated pipeline into a manual one.

I think if we do generate a new screenshot for it, we'd want it to be uniform with the other screenshots we make rather than harvesting from another location: but the part of making one off screenshots or using existing ones that we harvest from other media is the precedent for additional manual work before every release. We're already stretched thin for time, and I don't have any firm understanding of whether items with dynamic visual states will proliferate over time and turn a bit of one-off work into a decent amount of one-off work.