The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#1
|
|||
|
|||
Ok, so let me get this straight..
The Tips and recommendations that appear when you submit a new release MUST be followed or the hack can't be released? If so, wouldn?t that make it a requirement and not a recommendation? I'm not arguing but I'm asking a question, because it sounds to me as if rules are made up at random.
The explanation for requiring an attachment doesn?t even make sense. Just because they request the hack via private message doesn?t mean they won?t get a copy. They can still save it to their hard drive and refer back to it during an upgrade. So? what?s the deal? I really need to know the rules before participating any further. |
#2
|
||||
|
||||
Let me spell it out for you:
All hack instructions must be attached as a separate text file to the first post of each thread in Full Releases or Beta Hacks forums. Take my word for it. |
#3
|
|||
|
|||
Ok.. so at least now I know recommend = requirement around here. Thanks for clarifying that. May I suggest spelling that out in the written guidelines so you dont have to. Its very confusing when people are forced to follow policy that is subject to completely random interpretation.
|
#4
|
|||
|
|||
Oh BTW, the very first thread I came across in the full release forum doesn't have an attachment. I can find several hundred others if you need the links. We wouldn?t want a double standard to form around here.
|
#5
|
||||
|
||||
I'm not sure why you insist on pushing this issue - this has never been a problem before - it has always been a convention that hackers attach the hack to the thread.
We cannot allow people requesting PMs as this is not how it is meant to work - we do not want people posting threads requesting PMs for hacks, then ask for payment. |
#6
|
|||
|
|||
I?m pushing the issue because it doesn?t make sense to me. It?s not even like I?m disputing an existing rule. It is clearly labeled a recommendation. If it?s anything other than that, the guidelines should explicitly state such. I don?t like being shot at from all angles because the guidelines are woefully inadequate. This is a clear case of practice over policy, and that?s not a very effective way of implementing your ideals.
I can?t say the rule, or the reasons for said rule, is improper. I have a problem with the way it?s presented and enforced. At least you conversed with me on the matter, and didn?t resort to deleting my threads and ignoring my concerns. For this you are to be commended. |
#7
|
||||
|
||||
Where is this guideline and I'll edit 'recommended' to 'required' so we can put this to rest.
|
#8
|
||||
|
||||
I've already raised this issue about the clarity of the rules with Chen and the rest of staff. Like I said, no one else has had this problem with understanding what we have all taken for granted, but if it is confusing to even a minority, then it is something we must address.
|
#9
|
||||
|
||||
Steve, just click on "New Thread" in the Full Releases forum, scroll down and you'll see it.
|
#10
|
||||
|
||||
Unfortunately that's from some sort of hack and I have no way to edit it. Either Chen or someone with access to the server will need to do this.
In the meantime it's recommended - er, required - that you take Erwin's word on this until the written rule can be updated for more clarity. |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|