The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#1
|
||||
|
||||
Co-Authors
I have done a lot of things with Steve M. I'm put as a co-author. Why can't the system that you use take into account the co-author. This would really help some people who never actually release a hack by themselves. And can the same thing go for:
username has installed this mod. This could be useful for a lot of reasons. |
#2
|
||||
|
||||
Can you explain further - what system do you mean exactly, and what are you asking that a co-author should be able to do that they cannot atm ?
|
#3
|
||||
|
||||
OK, I'm referring to all hack systems right now. When you release a hack, you can add files, send updates, edit modification information, and see who has installed it. I think that there should be a way for co-authors to be given permissions by the original author for certain things. A separate edit post (where it makes changes but the hack author has a roll-back option to the last post made by the hack author {thread starter}) section, upload section for screens and files, and the "Username has installed this mod" in the postbit for co-authors. This would help with things like support when you only want to support those who care enough to click install. Things like that.
I also think that it should be a more accurate listing in hack authors profiles to show all hacks that they are listed "Co-Authors" on. As they (most likely) did some coding for the hack. They deserve a link in their profile. Just a separate section for "username has co-authored these hacks". This would be very helpful. |
#4
|
||||
|
||||
Yeah I second this.
|
#5
|
||||
|
||||
I third it.
By way of example, Sniper is unable at the moment to support his popular and excellent moods hack due to other real life commitments. Since I made some changes to the mood hack on my site, I offered to support the hack for him until he can get the time again. However, I have no ability to upload a new version, or edit the original post in anyway. |
#6
|
||||
|
||||
Yes I fourth this!Like the way the release levels are calculated they take into account thread ratings,installs and such and they should also include Co-Authors.
|
#7
|
||||
|
||||
There are no plans for such a facility.
|
#8
|
|||
|
|||
the best thing coders can do is working in duet with the co-authors, and when you release a hack, make it quick to let your co-authors post the first replies... so they can add to these replies when they want to support...
these first posts are usually the place where we first read after the hack description, and you can always indicate something like "read further below for support from the co-authors"... |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|