Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Alternate launcher carriage return issue #38

Open
Todd1215 opened this issue Mar 4, 2021 · 1 comment
Open

Alternate launcher carriage return issue #38

Todd1215 opened this issue Mar 4, 2021 · 1 comment

Comments

@Todd1215
Copy link

Todd1215 commented Mar 4, 2021

Alternate Launcher seems to write the carriage return for the key file as LF instead of LFCR. While BMS might not care about this carriage linefeed ending using Excel Key File Editor does care about how the carriage return is defined. If its defined with just LF then importing a key file into the Key File Editor that has been written by Alternate Launcher results in Excel trying to copy the entire contents into a single cell rather than importing each line in the key file into a separate row.

Since this is a Windows tool wouldn't it be better to write the key file out with CRLF endings?

@Hawkeye4040
Copy link
Contributor

Hawkeye4040 commented Mar 6, 2021

I think it would be better to use CRLF for other reasons as well. I'll ask him about changing it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants