[1.3.0] Launch Numbering 0.4.0

[linuxgurugamer]

28 minutes ago, Gargamel said:

would have been the 10th flight of a vessel, and it number it -0A

Its a bug, apparently it has an X where it should have an N in the code.

I assume you want this for 1.3.1?

Ill see if I can get it updated tomorrow.

regarging your request, I believe that it already ignores minor changes

[Gargamel]

30 minutes ago, linuxgurugamer said:

Its a bug, apparently it has an X where it should have an N in the code.

I assume you want this for 1.3.1?

Ill see if I can get it updated tomorrow.

regarging your request, I believe that it already ignores minor changes

Don't hurt yourself on my account!  I knw you're busy with everything, including Real Life.    But yes, 1.3.1 please :D.

And what constitutes a minor change?    Every time I've made changes, it results in a numbering reset, which can get confusing if I have multiple Vessel-01's in flight.  But if I can identify what the limit is, I should be able to make changes under that limit, launch and revert, and make more changes, yes?

[linuxgurugamer]

7 hours ago, Gargamel said:

And what constitutes a minor change?    Every time I've made changes, it results in a numbering reset, which can get confusing if I have multiple Vessel-01's in flight.  But if I can identify what the limit is, I should be able to make changes under that limit, launch and revert, and make more changes, yes?

and therein is the problem.  How can the mod determine what a minor change is?  I looked at the code, and apparently it does NOT do any sort of checks.  So, it may be possible, but how can I decide what a "minor" change is?  Think about it from the mod's point of view:  A rule needs to be defined which will be checked all the time, so, for example, putting on an RCS thruster may be considered a minor change (or changing an engine from one to another), but changing the size of a tank may not be.

[linuxgurugamer]

Minor fix to my unofficial version now available here:

https://github.com/linuxgurugamer/KSPLaunchNumbering/releases/tag/u3

• Numeric format changed from hex to numeric

[Gargamel]

20 hours ago, linuxgurugamer said:

and therein is the problem.  How can the mod determine what a minor change is?  I looked at the code, and apparently it does NOT do any sort of checks.  So, it may be possible, but how can I decide what a "minor" change is?  Think about it from the mod's point of view:  A rule needs to be defined which will be checked all the time, so, for example, putting on an RCS thruster may be considered a minor change (or changing an engine from one to another), but changing the size of a tank may not be.

My suggestion would be to have an option to ignore changes at all, and if the vessel's save name doesn't change, the numbering won't reset.  This would be a toggle with the Block numbering system, as they would have to be mutually exclusive.

18 hours ago, linuxgurugamer said:

Numeric format changed from hex to numeric

This made me laugh.  Thank you sir(?), you are the best.  Have some snacks to go along with the likes.   

[Gargamel]

20 hours ago, linuxgurugamer said:

Minor fix to my unofficial version now available here:

https://github.com/linuxgurugamer/KSPLaunchNumbering/releases/tag/u3

• Numeric format changed from hex to numeric

WHOOPS!  LOL!

Appreciate the rapid response LGG, so get to this when you can, no rush. 

[linuxgurugamer]

1 hour ago, Gargamel said:

WHOOPS!  LOL!

 Appreciate the rapid response LGG, so get to this when you can, no rush.  

Well, it IS numeric

Here you go: https://github.com/linuxgurugamer/KSPLaunchNumbering/releases/tag/u4

[linuxgurugamer]

@Damien_The_Unbeliever has given me permission to continue this mod, please move discussions over to this thread:

 

[vardicd]

Ooops

Edited April 25, 2019 by vardicd