The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#11
|
|||
|
|||
It only leaves you not so much room for the hackname anymore. And if you do like i do, prefix everything with it, then it is a hell of a lot to type.
|
#12
|
||||
|
||||
Quote:
Quote:
Another way we could do it is via vB.org userid So mine would be 4197_apf? Satan |
#13
|
||||
|
||||
I don't need no vBorg id.
14716 would work for me and leave 9 characters for hack name. Can I file a userid change request? |
#14
|
||||
|
||||
Quote:
Anywho - I cannot see any other way of ensuring uniqueness unless we either use your vB.org username or vB.org userid... Satan |
#15
|
|||
|
|||
Don't forget that you have a description field, which could include any info you want to pass along
Quote:
|
#16
|
||||
|
||||
Quote:
So if there are 2 Hacks using the same ID the User can't install both, so it would be easily discovered. |
#17
|
||||
|
||||
Quote:
On a slightly side-note: Can someone add a "Uses Product Manager?" option when creating a new modification? Seems only fair to warn users that they will have to upload a plugin file via the product manager... Quote:
Satan |
#18
|
||||
|
||||
The product id will be 25 chars in RC2, not 15.
I will probably prefix all mine with paulm_ - after that I will most likely just use the date/time I create it (like paulm_200507271126) as it's not really that relevant - the pid is not really used or displayed anywhere. The Description field is criminally small at the moment, it would also be handy to be able to have a support url field (which could be the hack thread after you have released it - but obviously you would have to update it after first release). |
#19
|
||||
|
||||
Quote:
Satan |
#20
|
|||
|
|||
I like the url to support the hack / plugin. I think that should be implemented.
|
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|