The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#11
|
||||
|
||||
Quote:
|
#12
|
||||
|
||||
An owned licence is not that expensive - I think $160 is easily affordable if you really make an effort for it
And no, the only thing you lose when your owned licence members area expires is the ability to download the *latest* version of vBulletin - You can download any version previous to the latest that was within your licence period - I.e. for me, all the way back to 2.2.5 and up to 3.5.0 Chris |
#13
|
|||
|
|||
I think we need to look into allowing mod authors to support their modifications if they no longer have a license. We'll look into this
|
#14
|
||||
|
||||
Yes! This should be easy to implement actually I think, if I guessed a little of the vborg schema.
I assume upon posting a hack, you enter into a usergroup caled coders, with titles that are based on installs/hack #s. You ALSO get (as a secondary group) the 'authenticated' usergroup, which allows access to post new threads and download in the hack area. So, when the authenticated usergroup expires, they still have the primary coder status, which has the base priviledges of posting in threads that they created :-p Just access masks! If however, vborg has a completely crazy alternate system up instead of slight tweaks to the system already there, then this will be harder to switch to, i dunno. PS. and 160$ isnt as cheap as you might expect to some of the admins who are buying vb (some regularly 16 and under). When we first bought it, (me and my partner) it was just for the year and I barely was able to scrounge up my 40$ (i dont have allowance!) and we were able to get to 160$ purely from me selling scripts that i wrote during the duration of that year. So yeah, those who are 25 and have had steady jobs, this is a half-week endeavor :-p but i do feel their pain. |
#15
|
|||
|
|||
How can they support their hacks if they don't have a license? (Ie...bug fixes/upgrades)
|
#16
|
||||
|
||||
well, the code they wrote had nothing to do with vbulletin, it just ran on it :-p so if its a problem with their unique code, then they would be the ones who coded it and thus would know what went wrong. you could disable new uploads (which would make sense since they would no longer be able to download) but they should still be able to assess errors people encountered with THEIR code. most especially true when the hack is a major addition and has entire files which do little more with vb than just set up a session :-p again, at least some limited access to maintain whats already there.
|
#17
|
||||
|
||||
Quote:
Chris |
#18
|
||||
|
||||
Quote:
|
#19
|
||||
|
||||
Quote:
Chris |
#20
|
||||
|
||||
Quote:
|
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|