Jump to content
  • 0

Changlog of the STEP guide(s)


Question

Posted

Hi all!

 

I'm not actually sure this is the right place to put this but if it is, please move it the correct section.

 

I wanted to ask if perhaps in the changelog of STEP, it can be added if a mod from the previous STEP guide has been updated(Weapon and Armor Fixes for instance). Because if you have 2.2.8 installed, it is fairly easy to up it to 2.2.9, due to Mod Organizers VFS. But since you can't know if an update of the mod has been uploaded, you kinda needs to check all the mods, unless you just happen to know that support for a mod is no longer maintained.

Of cause, if this would cause much trouble for the developers of STEP, it is not a must, but it would help immensly upgrading the guides, since a completely new install, takes quite a while.

 

~Sincerely

 

Halde.

9 answers to this question

Recommended Posts

  • 0
Posted

 

 

But since you can't know if an update of the mod has been uploaded, you kinda needs to check all the mods, unless you just happen to know that support for a mod is no longer maintained.

 

Open MO, right click on any mod, select "All mods", then "Check all for update".

Also, it is a good thing to actually track the mods you use on nexus, in case they get updated without a version number change (for compatibility patches, mostly)

  • 0
Posted

Yes, but I have noticed that this "Check for update" function is rarely actually correct. Whether this is an oversight in Mod Organizer or Nexus I don't know. Mod Organizer is flagging a lot of my mods for not being up-to-date, when they in fact are up-to-date.

  • 0
Posted

Take for instance "Birds and Flocks". Mod Organizer list my installed version as "2014-06-03"(install date) and newest version as "2.4". But there hasen't been release of "Birds and Flocks" since December 2012.

Actually I wanted to not do the "Check for update" function, because this happend last time as well. Now all mods are flagged, with about 80% of them being flagged just like "Birds and Flocks" is flagged. And while it is practically meaningless, I dislike that my left pane of Mod Organizer now appear so ironically disorganized.

  • 0
Posted

We don't have enough people to maintain something like that. It is very tedious and unless we could automate it, there would be no way for use to keep up with all the updates. We have enough trouble with that as it is.

 

Right now we have 1 site dev/admin, three guide devs, three or four moderators, and two testers. We would need to double all those just to be able to implement nice stuff like that into the guide.

  • 0
Posted (edited)

I don't mean maintaining it. Only when a new STEP is released(this new 2.2.9 for instance), write in the changelog the mods that has been updated as well. It would not be fair to expect you to constantly update the condition of the mods. I only meant when you release a new version of STEP. I assume you check all the mods inbetween releases anyway, because if a major change has happend(take again Weapon and Armor Fixes, now with a Fomod not previously available), you would need to know.

So when people who already have STEP setted up, when a new guide is released, they could just go to the changelog and everything will be up-to-date without having the do a complete reinstall of STEP and without having to check every single of the 200 mods.

Again, this would be neat, though certainly not something that should be prioritized over the more important aspects of STEP, but I can't imagine that it would take a lot of time.

Edited by Halde
  • 0
Posted

I think best we could is make a list of the version of every mod that is current when the guide updates. That would be something to compare mods against from STEP to STEP (pun intended ::P: ).

  • 0
Posted

Days without bad STEP puns: 7 0

 

Concerning the versions displayed in MO, you can very easily fix them manually by typing in what version you have installed to get rid of the warnings. You'd have to the same if you were using NMM, for the record.

 

To do that, just click on the "2014-06-03" twice (slow double-click) and type in the actual version number.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.