Skip to content

Sometimes, the split file number starts at 0 - #94

Merged
K0lb3 merged 2 commits into
K0lb3:masterfrom
ablegao:master
Mar 10, 2022
Merged

K0lb3 merged 2 commits into
K0lb3:masterfrom
ablegao:master

Conversation

@ablegao

@ablegao ablegao commented Mar 6, 2022

Copy link
Copy Markdown
Contributor

No description provided.

@K0lb3
K0lb3 merged commit 6a9e604 into K0lb3:master Mar 10, 2022
@isHarryh isHarryh mentioned this pull request Oct 31, 2026
GoJean added a commit to GoJean/UnityPy that referenced this pull request Nov 2, 2026
As pointed out in the review by @isHarryh, the previous commit broke the old behavior where split files could start from either 0 or 1. 

This commit fixes the regression by only breaking the loop when `i > 0` (using `if i:`). If `split0` is not found, the loop will now correctly continue and try to load `split1`, preserving the compatibility introduced in PR K0lb3#94.
K0lb3 pushed a commit that referenced this pull request Nov 14, 2026
As pointed out in the review by @isHarryh, the previous commit broke the old behavior where split files could start from either 0 or 1. 

This commit fixes the regression by only breaking the loop when `i > 0` (using `if i:`). If `split0` is not found, the loop will now correctly continue and try to load `split1`, preserving the compatibility introduced in PR #94.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants