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

crash while booting AbyssalCraft-1.8.9-1.9.0 #64

Closed
Divineaspect opened this issue Mar 2, 2016 · 6 comments
Closed

crash while booting AbyssalCraft-1.8.9-1.9.0 #64

Divineaspect opened this issue Mar 2, 2016 · 6 comments
Labels

Comments

@Divineaspect
Copy link

http://pastebin.com/idHvkgUi

@Shinoow Shinoow closed this as completed in 413cac2 Mar 2, 2016
@Shinoow Shinoow added the bug label Mar 2, 2016
@Shinoow
Copy link
Owner

Shinoow commented Mar 2, 2016

Thanks for reporting this on such short notice! It could've really turned into a horrible mess.

@Divineaspect
Copy link
Author

did this get a stealth update?

@Shinoow
Copy link
Owner

Shinoow commented Mar 2, 2016

Pretty much. Did a re-release on 1.8.9-1.9.0.

@Divineaspect
Copy link
Author

rereleases without version changes are hell on pack devs, and screwup auto updaters such as those used by ATL, FYI.

@Shinoow
Copy link
Owner

Shinoow commented Mar 3, 2016

If the stealth update is released 5 hours after the original one (which at the time has received 20 downloads), there should be next to no impact. Besides, I hardly do stealth updates, only when the new version breaks at startup (and was released less than 8 hours ago).
I also make a note that there was an issue causing there to be a re-release (which I unfortunately didn't spread too much this time).

@Divineaspect
Copy link
Author

my auto updater, through ATL, tracks by version number.

It DLs automatically when there's an update, and that file is what gets referenced by a pack who uses their auto update feature. Meaning as far as they can tell they have the most up to date version, because, you know, that's what version numbers mean.

In the event of a stealth update, while no one knows you needed to fix anything, no one knows anything they see breaking is fixed. Then they think your mod is buggy, and not how cool it is. Making mistakes and fixing them, makes you look more reliable / less wrong in the long run.

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

No branches or pull requests

2 participants