[Shannon Lockwood]

It has already been mentioned that they're working on a "more comprehensive" patch, that this is just an incremental one.

...of course in true "the solution is worse than the problem" style, head over to the "New Vegas PC Issues" forum and look at all the threads talking about problems introduced by the patch --- like several creatures in various places being set as essential now... *sigh*

Thankfully they have already fixed that.

[Melanie]

Yeah, but oddly the patch has introduced the bug to the Cowboy Repeater that it supposedly fixed. I never had that bug before. Now I have to click the fire button after reloading both it and the Hunting Shotgun while crouched. Don't know if it affects other weapons yet.

[Stephani Silva]

There is the issue of The Thorn, if you look it up on wiki, you will see all the issues with it.

[Robert Bindley]

When I buy ammo boxes while this "patch" is loaded, everytime I X the shop the game crashes.

Tested it several time with just the fnv.esm and then with cp loaded.

Using v.4 or .45 ,, where can I get .5 ? Maybe it got fixed

€: found it
http://www.sendspace.com/file/cvfaad

[Alan Whiston]

Thanks - will go in the next patch. Just waiting on a few more permissions. Does definitely slow things down a lot.

I think the way this is going to have to work is you'll just have to set a cut-off point for each patch release and let it into the wild, with perhaps a note in the readme/description listing those mods that are "pending approval". That way people can grab the individual mods to use until you get permission and the mod is incorporated into the next release. At this early point in the game's life, while the rate people are finding bugs and fixing them is still very high, it's the only way I can see things working.

Much kudos to you Zenball for taking this on.

[Dezzeh]

You should put up a bug tracker, like the one used for UF3P. It would be a lot easier to keep track of what needs to be done and what's been suggested already.

[Catherine Harte]

http://www.newvegasnexus.com/downloads/file.php?id=37041

Fix by Yukichigai at NVNexus to prevent companions from using Nuka-Cola Quartz/Victory while "sandboxing" at the Lucky 38.



-Flytrap

[Umpyre Records]

I think the way this is going to have to work is you'll just have to set a cut-off point for each patch release and let it into the wild, with perhaps a note in the readme/description listing those mods that are "pending approval". That way people can grab the individual mods to use until you get permission and the mod is incorporated into the next release. At this early point in the game's life, while the rate people are finding bugs and fixing them is still very high, it's the only way I can see things working.

Much kudos to you Zenball for taking this on.

Thanks for the suggestion, but I'm not going to do this as it will make tracking and releasing a nightmare. It is not up to me to chase people for permission. I ask and then wait. People are just going to have to wait until everyone gives permission, or fix makers are going to have to allow permission for the community patch on releasing their fix.

[Timara White]

Thanks for the suggestion, but I'm not going to do this as it will make tracking and releasing a nightmare. [snip]

Maybe not, say if you were going to release an update every month (or 2 or 3) and that was known (like in the mod description or what not: "Next Release: 11/30/2010" for example), so by that time you're either in or out, and anything that is done and approved still gets out there.

You've already got a list of what you want into it in the other thread; perhaps just put "Pending" in front of the ones that haven't replied and stick that in the mod description? Possible you wouldn't even need to maintain a separate list outside of that.

I know this is a good amount of work already, so I'm just trying to come up with some helpful suggestions that are low on the added work.

Do appreciate the patch, and thanks.

-Flytrap


EDIT: Did I read higher up that you have to ask for all of the permissions for EVERY fix time you update the patch, even if that part isn't updated? If so, disregard my suggestion and good luck to you, as that seems like a silly rule. Keep fighting the good fight.

[Penny Flame]

Once permission is given for inclusion, that should be good for all future versions. If anyone says they don't want to give that permission, I'd say not to include them.

I still hope that once you feel close enough to a release you'll post a list of missing fixes so that people can volunteer to make the patches you need.

[J.P loves]

2 New fixes:

• http://www.newvegasnexus.com/downloads/file.php?id=37052, with implicit permission in the description: "If this gets utilized elsewhere I won't demand credit for anything, after all it's just a tweak to utilize material that's already there. If you do use this file for something else here, though, and would like to mention me I wouldn't object. "
  
  
• http://www.newvegasnexus.com/downloads/file.php?id=37036#fileanchor small script fix and I requested permission for you in the comments of the mod.

[BlackaneseB]

Haha. My post got deleted.

Anyway, best of luck getting all the permissions and thanks for the mod, Zenball.

[ashleigh bryden]

This mod still works even if I haven't patched my game today, right? The new patch broke my game so I went back to the old .exe, I'd like to use this mod so just wanted to make sure it works.

edit: Also, I can't download the mod, says it's "under review"?

[P PoLlo]

Thanks for the suggestion, but I'm not going to do this as it will make tracking and releasing a nightmare. It is not up to me to chase people for permission. I ask and then wait. People are just going to have to wait until everyone gives permission, or fix makers are going to have to allow permission for the community patch on releasing their fix.

Honestly, I still think that this is entirely the wrong way for you to approach this anyway. You only need to seek permission to satisfy the Nexus' requirements, and it is my belief that the Nexus is really making an unnecessary rock for their back here. Unless the mod in question introduces entirely new assets created by another author, asking permission to use it in this way is a courtesy, not a requirement. Mods that themselves are only modifications to Bethesda/Obsidian's existing game assets "belong" to Bethesda/Obsidian in every meaningful sense; the only party legally allowed to assert any control over their distribution and use are Bethesda/Obsidian and they have made it clear that all IP remains with them. If anyone from Beth happens to be following this and feels like speaking up on the subject, it would be great, but this is my understanding of how the land lays.

However just because the Nexus has taken it upon themselves to enforce this particular courtesy on their user base (and of course they have that right), unless you are absolutely determined to have them host this, you are under no obligation to follow their rules. It seems clear to me that in this case doing so just makes a lot of unnecessary work for you and is well beyond the bounds of what courtesy would demand. The way you released this in the first place was exactly right - you sought permission from anyone whose assets you used, and you credited everyone you could, which was the polite (but not required!) thing to do. I'm sure that if anyone had contacted you and asked that you not include their work you'd have taken it out - though you'd have been entirely at liberty to reproduce their work yourself and then include your own fix instead.

My opinion: you should carry on as you were and just host this elsewhere. It's going to remain one of the most popular mods available for the game until such time as official patches are released that fix all these bugs, which should be at about the same time as pigs fly and hell freezes over. If the Nexus decides they don't want to host it then it's their loss - not yours, and not the communities as has been the case since this file was taken down.

[Russell Davies]

Is the ver 5 still good to use togheter with the new update `?

[MR.BIGG]

@Kal Choedan and others

My take on the permission handling in this mod:

I am in the process to correct a lot of weightpaint errors in the new armors in New Vegas (Ever sneaked in the male version of Leather Armor Mark II ? Then you know what I mean). Every armor needs about 3 or 4 hours work to remove the annoying clipping, dismemberment and display errors.

It's simple a sign of respect for my work to ask for permission if someone wants to put it in a 'Borg' patch. I will never go in a thread and beg that my work is included. Why should I?

I look at the german mod scene where high quality mods get translated, borged and the compilator gets all the praise from the magazines what perfect mod he hasn't made which is simply not true.

Sorry this isn't the way I want to play the modding game anymore.

[Ernesto Salinas]

It's simple a sign of respect for my work to ask for permission if someone wants to put it in a 'Borg' patch. I will never go in a thread and beg that my work is included. Why should I?

I look at the german mod scene where high quality mods get translated, borged and the compilator gets all the praise from the magazines what perfect mod he hasn't made which is simply not true.

Sorry this isn't the way I want to play the modding game anymore.

That type of problem is the main reason why I stopped modding back in Morrowind, and I released several mods, and helped with the development of several others. I got very tired of people ninjaing my work, posting it everywhere, claiming it as their own and so on. With regards to bug fixes and so on, for the most part I don't mind too much as long as I get get credit. I don't have the time or patience to work on a slew of bugs, I'd rather be working on something long term.

It takes a lot to piss me off, but a couple of select individuals managed to do it. So with that, I simply quit the scene, dumped my old forum name and went to this one.

[El Khatiri]

I am in the process to correct a lot of weightpaint errors in the new armors in New Vegas (Ever sneaked in the male version of Leather Armor Mark II ? Then you know what I mean). Every armor needs about 3 or 4 hours work to remove the annoying clipping, dismemberment and display errors.

I don't think you need to worry about that, because that involves more than just firing up the GECK and making some edits. The point that I have been trying to make in my previous replies to you is that there is no doubt in my mind that majority of people here, especially after this whole incident, would agree that before they add a 'fix' like that to their mod, they need to obtain permission. Where the point of debate is over is regarding the small fixes involving little more than editing in the GECK and NVEdit, like correcting the weight of an item, or a gun using improper ammunition. Not to minimize the time that the authors may have put into hunting down the source of the bug, but when the final patch is released down the road, the majority of those 'fixes' will be redunant. I don't know if Zenball is being asked to obtain permission for those 'fixes' as well (it seems that way). In the past (that is, for Fallout and Oblivion), when I uploaded such small fixes, I generally write "you can do whatever you want with this..." somewhere in the readme (which is now simplified through the new permission system on Nexus), because it is kind of banol to claim that this constitutes 'original content', so I think it is important to not compound the 'misunderstanding' by conflating the issues of contention.

[Robert]

I appreciate what you're saying guys, but really, it's just the nature of the thing. Getting upset because people are rude on the internet... well, you're going to spend a lot of your time upset, right? There are always gonna be jerks.

I'm just saying that for a mod of this nature, asking permission is a courtesy, not a requirement, and in the case of a compilation like this where the author has clearly gone out of his way to give credit and there is absolutely no suggestion of plagiarism, seeking explicit permission for each individual inclusion is an unreasonable expectation.

I realise that it's out of a genuine desire to protect modders, but I believe the Nexus has gone way overboard with this permissions thing and I suspect that when Bethesda's lawyers notice, the Nexus staff are going to get into hot water over it.

[Smokey]

And besides, I could still ask for your permission and then go around posting it everywhere claiming it's my work. Even if you don't give me permission, I could *still* download it and claim it's my work. I'm part of another modding community and there's been the same problem there. I think it's just far better to, if you're modding and putting something up on the internet, accept the fact that yes it's gonna be redistributed, yes it's gonna be criticized for completely insane reasons, yes another person may even claim ownership of it etc etc.
I mean, that's just how modding works. You're modifying a game which is not your own, and if you create assets of your own that you really care about and want ownership of, then you shouldn't post them on sites that thousands of people frequent and hope that people won't "steal" them. I think that is a bit naive.

I think this compilation is done with respect, there is no attempt from the author to claim the work as his own, the credit is there, and it's a huge service to the users of the game. If it weren't compiled like it is, I wouldn't make use of half these fixes. And in my opinion at least, I'd rather know that people were using my work that I put out for free knowingly, rather than maybe having them not use it, regardless of whether I get credit or not.

[Nikki Hype]

And besides, I could still ask for your permission and then go around posting it everywhere claiming it's my work. Even if you don't give me permission, I could *still* download it and claim it's my work.

To get my permission you have to give proper credits. That's simply how it is. If this isn't given no permission. People who are asking do it normally (the wouldn't ask otherwise).

Surely you can simply download it and claim it as your work. Which has only one effect that I am not releasing anything anymore. That's how naive I am.

[Heather beauchamp]

This is a "Community" patch, which means that it is a patch that services the community but is also guided by community -input-, including input around the ways in which the patch is produced. You may not like or agree with the norms and rules of the community but simply saying "screw them, people should be allowed to be a-holes if they want to" is, INHO, not an appropriate response. So for example, when you say

Getting upset because people are rude on the internet... well, you're going to spend a lot of your time upset, right? There are always gonna be jerks.

I take great offense at the idea that we should actually accept and breed that kind of apathy. Not that I am trying speak for Zenball, but this is not a position that I think Zenball would agree with. None of the modders whose work were included in the patch have stated they were upset. What your post implies is that there is some rampant desire on behalf of some jerk modders out there who want to insulate their work, which somehow spilled over to the impedient of the community bug fixes patch, which is just not true and is not how this patch came under scrutiny by Nexus staff. as explained by DarkOne in his reply in this thread.

What you are suggesting is that there will always be random users who will do what they want, and we should just accept it since we can never really stop it. Well, we do accept it, we just don't have to perpetuate it, because in that case, there is no 'community', and people will just do whatever they want, step on each other all they like. Why even bother doing a community compilation of fixes? You can all be (cyber-)libertarian individuals with no accountability to anyone but oneself and go make your own fixes. Is this the message that should dominate the atmosphere of our engagements with each other?

I agree that it may be excessive to hunt for permission even when the fix is just GECK edits, but that should not mean no permission is needed for -anything-. Very quickly, more involved fixes, like the ones Sesom is doing, will not be made available to the 'community' (since there would be no real 'community' to share it with), and just shared privately or included only as part of the modder's own work. Is this what we want?

I believe the Nexus has gone way overboard with this permissions thing and I suspect that when Bethesda's lawyers notice, the Nexus staff are going to get into hot water over it.

That's just silly.

Now, can we move on and starting talking about the patch, rather than Nexus policies?

[Nauty]

I can not download this file, it just says:

Site error
The site has run in to a problem, please look at the error message below...

This file is currently under review by a moderator and is not open for public access. Please do not contact the staff or the owner of the file regarding this issue or you might be penalised by the staff of the site.

Seems like they do not like your way of inserting other mods in your package...

[City Swagga]

Anyone got an answer to my question? This one:

This mod still works even if I haven't patched my game today, right? The new patch broke my game so I went back to the old .exe, I'd like to use this mod so just wanted to make sure it works.

edit: Also, I can't download the mod, says it's "under review"?

[Ben sutton]

Anyone got an answer to my question? This one:

It only changes ESM files and a few models/textures. An engine patch should have no effect on it at all.

Even the upcoming content patch shouldn't break the CBFCP, just make a few of its fixes unnecessary.