some random guy complaining

[20:26:39] <Tails> Is the 2.1.7.3 release on the Wiki page yet? The adf.ly download just points to a 2.1.7 file
[20:27:37] <@Kilobyte> it is
[20:27:56] <@Kilobyte> lemming didn't add the .3 to the file name
[20:28:01] <+Andrew2448> yep it will download 2.1.7.3 dont worry
[20:28:20] <Tails> Ah, I see that now. Would make it a teeny bit easier to include that in the filename
[20:28:39] max96at [~max96at@d86-32-81-108.cust.tele2.at] hat den Server verlassen: Quit: I'm gone
[20:29:11] <Tails> And in the mcmod.info file, as well
[20:30:07] <@Kilobyte> well oficially it is 2.1.7
[20:30:16] <@Kilobyte> just internally its 12.1.7.3
[20:30:20] <@Kilobyte> *2
[20:31:24] <Tails> Yet most mod authors make a note of making the x.x.x.<y> visible, so users know if the download link has been updated. Also, the mcmod.info should at the very least include it, so users know they have correctly updated
[20:32:31] <Tails> Even Mozilla used to update their installation files with the bugfix prefix :p
[20:32:54] <@Kilobyte> meh, added small info to linl
[20:32:56] <@Kilobyte> *link
[20:33:58] <Tails> Cheers. Does the NEI plugin also follow the same system, or has that stayed untouched since 2.1.7 was released?
[20:34:13] <@Kilobyte> dunno
[20:34:18] <@Kilobyte> i'm no developer
[20:34:40] <Tails> And this is what the inclusion of that number to the filename would fix ^^
[20:34:55] <@Kilobyte> yeah
[20:34:59] <@Kilobyte> i told lemming
[20:35:51] <Tails> Cool, ty ;)
[20:36:04] <@Kilobyte> i already did yesterday
[20:36:11] <@Kilobyte> but he was like meh
[20:37:38] <Tails> The filename isn't really the big issue; it's the mcmod.info file. That should be updated, at the very least, because it prints out the version in both Forge and MultiMC
[20:37:55] <@Kilobyte> like i said, i'm no dev
[20:37:59] <Tails> If I add new updates, and if the mcmod.info file hasn't changed, I have two identical files in the interface
[20:38:04] <@Kilobyte> i'll slap hi when i see him next time
[20:38:09] <Tails> hehe