#texturepacker
Live, measured metrics for the hashtag #texturepacker from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #texturepacker
This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.
Day-by-day usage
measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-27 09:47 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · fosstodon.org (Mastodon public search API) · fetched 2026-07-27 09:47 UTCNo related tags with measured usage found for #texturepacker.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 09:47 UTCEverything below is measured over the latest 4 public posts (spanning ~23232 hours).
Posting hours (UTC)
Languages: English (4)
Avg boosts / post: 1.3
Used together with
Top of the latest posts
Seems TexturePacker (https://www.codeandweb.com/texturepacker) does not have support for Bevy or Bevy does not handle the atlas format. That's a shame, as it was a really useful tool aeons ago when I used Cocos2D to just pack random sprites
Adding the editor interface for our new #TexturePacker support. Here is an example with multiple pages. Next up, is rendering them in the viewport... #defold #gamedev
What can I say, I'm quite pleased that I got it working now. I can now use a custom #Defold exporter for #texturepacker, and compile it through our pipeline, and get the sprite to show. It wasn't that big effort, as we've been working towar
Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/texturepacker