HaxeFlixel / HaxeFlixel/flixel
Adobe Animate Offset Issue Examples
Nobody has claimed this yet.
- Dominant language
- Haxe
- Stars
- 2.2k
- Forks
- 522
- Avg merge
- 34m
- Merged PRs (30d)
- 1
Description
In March, we added frame offset modifiers for atlases, and I'm curious as to why they are needed. It seems like ASEprite atlases work fine, but Animate atlases have issues.
if you could provide FLA files that require code offsets, when exported, please provide them here. I'm trying to see if maybe we aren't parsing the files correctly, of - if adobe is fucking up - we can procedurally work around it. I don't think you can embed a fla in github comments so please either link to a file in a public repo, or use google drive so I'm not downloading suspicious zips.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no repository files, tests, or entry points. Start by finding or creating Adobe Animate FLA files whose exported atlases require code offsets, then provide links to the files in a public repository or Google Drive. Done means the examples are publicly accessible and clearly demonstrate the offset issue.
Written by the indexing model from the issue text.
Assessment
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100