The launcher is great and works really well. I'm planning to use it when more mods are out.
But also, there's a small thing I'd like to see fixed (should just be 1 line of code in the updater):
Firstly, I'm sorry if this is the wrong place - it's the best I could find.
Anyway, to the point, on Linux, when a new launcher update, it asks you like it should.
It updates fine, and restarts properly. BUT, when you close it down and re-run it,
Java refuses to launch it:
Contrary to what you might think by looking at the message, it's not because it thinks it's dangerous, it's just that the new downloaded file does not have its executable bit set. (as explained here: https://wiki.ubuntu.com/Security/ExecutableBit - thats also where the link points)
It's easy to use properties and check Executable (allowing you to run it again), BUT I think it'd be nice if the updater set the executable flag for you (it should be just one line of code, or maybe three, right?).
As I said, not a major bug, but something that would just be convenient.
But also, there's a small thing I'd like to see fixed (should just be 1 line of code in the updater):
Firstly, I'm sorry if this is the wrong place - it's the best I could find.
Anyway, to the point, on Linux, when a new launcher update, it asks you like it should.
It updates fine, and restarts properly. BUT, when you close it down and re-run it,
Java refuses to launch it:
Contrary to what you might think by looking at the message, it's not because it thinks it's dangerous, it's just that the new downloaded file does not have its executable bit set. (as explained here: https://wiki.ubuntu.com/Security/ExecutableBit - thats also where the link points)
It's easy to use properties and check Executable (allowing you to run it again), BUT I think it'd be nice if the updater set the executable flag for you (it should be just one line of code, or maybe three, right?).
As I said, not a major bug, but something that would just be convenient.