Version Numbering Issues

[BAPACop]

Mod Organizer is doing a weird thing where the version number I type in isn't the number it displays. For example, 1.1.3a turns into 1.1.3alpha. 2.0b turns into 2.0beta. And when trying to enter versions in a date format, there's not enough room for characters in the box. You can't enter 12.12.2012d into the box because it won't accept the "d" at the end. You have to edit the meta.ini file directly instead.

[hishutup]

It automatically does that for beta and alpha

 

I know, I dislike it also but I think tanin refused to change it.

[BAPACop]

How do I make it not do that?

[TechAngel85]

How do I make it not do that?

You don't. You deal with it. haha! MO still reads it as the correct version

[BAPACop]

I don't need MO to read it as the correct version, I need to read it as the correct version and I can't do that if it doesn't properly reflect what I type in.

[GrantSP]

There have been a number of variations employed by Tannin in formatting the version numbers. The current format covers most mods available and does the job it is designed for.

Keep in mind the version number is only indicative of the number the author has on the header part of the mod page. It is possible to have the latest version as described by the "File Section" but have MO show it as needing attention because the mod author hasn't fixed the page.

 

In the scheme of things the version numbering is very minor and if it doesn't suit your likes then there isn't a lot to do other than deal with it.

 

Additionally, there is no need to post a question here AND place multiple bug reports on the tracker. One report is sufficient. Please keep this in mind in the future.

[hishutup]

Like I said, I dislike it but it's kinda something that is stuck...

 

I wish it would reflect the version that the mod gives but that "feature" kinda ruins that for some mods. So, they always seem to need to be updated even though ita just the numbers being dumb.

[GrantSP]

If the issue is the incorrect format shows as needing an update, just right-click and "Ignore update".

[BAPACop]

The last time I posted an issue here no one responded. You'll forgive me for posting in multiple locations to ensure someone actually gets around to talking to me about it. I don't link to Nexus mods. I put mods in myself and I type the version numbers in myself. I need to be able to compare the version numbers in MO to the version numbers available for download. Why do I have to "deal with it"? Why can't an obviously broken feature be fixed? I typed 1.1.3a. I didn't type 1.1.3alpha. Why would MO displaying anything other than what I typed in ever be proper behavior?

 

When I type in "2.04.4" it spits out "2.4.4". How are those numbers the same?

When I type in "new" it spits out "0.0.0ew". How are those the same?

And it doesn't store them the same and just display them different. No, it stores them as "2.4.4.0" and "n0.0.0ew". So no, MO doesn't still read it as the correct version. Not even close.

Edited November 30, 2014 by BAPACop

[Nozzer66]

Unfortunately, there's not much we can do about it, as it's a MO thing. I know what you mean and you're not the first person to say something about it.

 

It's just a matter of 'having to deal with it' until Tannin fixes it, if he ever does.

[GrantSP]

This is a tool developed by one man, in his free time and offered for no money!

With an attitude like that it is probably indicative of why you don't get what you want all the time.

 

How about just being appreciative of the fine software that is given freely. No one is forcing you to use it.

 

@Nozzer66

You ninja'd me so it looks like I'm responding to you, I'm not.

Edited November 30, 2014 by GrantSP

[BAPACop]

[sarcasm]Oh, it's free? Well then! I guess that means it's absolutely immune from criticism.[/sarcasm]

 

It doesn't matter if it's free. It doesn't matter if it only has one person working on it. If it doesn't work right, it doesn't work right.

[GrantSP]

So get your copy of the source code, make the needed changes, submit them to the repo and let Tannin incorporate them.

 

If any of those steps are beyond your scope, then just be grateful for what you have.

 

Urgh... the age of entitlement has a lot to answer for.

[BAPACop]

Really? It's entitlement to expect something to work properly? And since when do you have to know how to do something to be able to criticize it?

[GSDFan]

Just a preemptive strike here before this gets out of hand. Everyone is welcome to post their thoughts in a constructive, level headed manner and engage in thoughtful conversation for the betterment of MO and STEP. Please don’t escalate this conversation to that point.

[hishutup]

I completely understand where @BAPACop is coming from.

If it has a feature then why doesn't that feature work correctly, especially with how mature MO is.

 

I would prefer a simple non-intrusive version numbering system but it is what it is at this point.

 

If you want to take this further then look for tannin bug genie  and look for a current Enhancement/feature/bug that talks about the version numbering system and then kindly request for what you would like to see it become.

Tannin will likely refuse.

If so, that is his choice.

 

Yes, it is free and its made in Tannin's free time but it is completely open to criticism because it is released to the public and accepted by many users.

 

This should probably end the discussion...

maybe...