![]() ![]() I want to play a reasonably stable version of Oblivion that isn't going to bork my save game because some utility I'm running alongside it gets changed before its final release. Me? I've had enough of beta testing, already, with other software. You people are the "beta testing team", you're taking the chances, and for that I salute you. ![]() That means its not ready for "public consumption" because there could still be bugs and other unexpected behavior.įor those people willing to potentially break their game by utilizing beta versions of OBSE and mods that may use functions that could be altered by the time of final release, feel free to do so. I'm still not going to use it, or any mod that relies upon it, until it's out of beta and has a history of running solidly and predictably. Version 20 actually adds some new and important functionality into OBSE. Some companies don't have that! And you certainly aren't going to get it in a volunteer modding community where people have to do this work as time permits. We don't have the luxury of a full development and testing team. ![]() Yes there is a risk with that, but the OBSE team is very attentive and any complaints of problems are looked at quickly. If people don't run with the new version, then it will be simply declared a full release. So what I'm trying to say is that the more people we can get who are willing to run with the latest version, the better. I guess there are a number of modders that try to fill that role and I include myself in those numbers. It would be nice if OBSE had a beta testing team. We will also add new functionality to our mods based on what is available in OBSE. We run our existing mods against the new releases to make sure they still work. It is up to mod developers to adopt the new versions of OBSE as they are released - that's how the new versions are tested. Most of these requests are exposing functionality that exists already in the game, but Bethesda didn't provide the functions in the CS to use it. Basically the OBSE team takes requests for new functionality and adds them in. There are things that wouldn't be possible without these new functions. ![]() Had I released my mod at that point, I would have needed that version, whether it's a beta or not. I have requested some new functions and they were added in v19. The reason some mods require the latest version, even if it is a beta, is because they are using functions that were added in that version. It also means I'm not going to consider them (and I'm actually interested in the Camping mod) until such time as OBSE 20 has been released in a stable version. In my opinion, that means both of those mods are still in beta. A change to OBSE before a final release could easily break either of the two mods to which you linked. It's just my personal opinion on this issue, but I consider it to be verging upon irresponsible on the part of the author of any mod who puts a version number of 1.0 or higher on any mod that requires any resource which is, itself, still in beta. Nor, as a developer of a mod, would I release a mod that required a beta version of OBSE and not refer to my mod, itself, as a beta. Since I'm not part of a beta-testing team for OBSE I'm not taking a chance on breaking mods that require lower versions of OBSE just to get the added benefits of version 20. While I realize that version 19 is a subset of version 20, there can be no absolute guarantee that problems might have been introduced in the beta that affect the operation of purely version 19 or lower scripts. Well, OK, I use Windows and play both Oblivion and Borderlands, and I think I can make an argument that they're all really betas, but we won't go there. I make it point to never install a beta unless I'm specifically helping to test it. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |