[SCRIPT3R]

Originally Posted by iguanairs

That means that DURING DEVELOPMENT of this modification, those users helped out with the core code of the modifications and reported errors that had been corrected for the version of VB that the mod was written for.

and where do newbies find such information that THAT is in fact what it means? i already know this, but to a lot of newbies, this little bit of information could help as it's not easily found within this forum.

This is NOT confusding. BETA is NOT checked because this modification was not a beta WHEN IT WAS RELEASED! When this modification was released, it worked fine. The only thing you needed to change was the vBulletin to read vbulletin in the xml. When this modification was released, it was for vB Version: 3.5.0 Beta 4 and it wasn't a beta. Everything worked for that version!

first of all, it DID NOT work "fine" for 3.5.0 Beta 4 as you claim. there were some of the same errors people are seeing now. if this is not confusing as you say, then why are there soo many post questing soo many things about this hack? everything about this particular hack is confusing to soo many people... hence all the posting - duh.

It doesn't matter how many coders actually click the supported box. If it is not checked, they have stated that they do not intend on supporting the modification. If they have time, and they do still support the mod, that is a bonus. If life happens, and they walk away from the mod leaving it unsupported, they are not doing anything they didn't already say they would do.

as i've already said... i know this, but many newbies do not as they can jump from thread to thread and get help from the coders instantly although soo many hacks are ticked as unsupported. again, another confusing aspect not made clear here.

I don't know cloudrunner, so I am not trying to defend his actions on a personal level. I am however pretty tired of coming to vb.org and seeing people talk trash when the version of vb they are running is not the version the mod was written for and the mod is listed as unsupported.

so why do you still come into this thread if it bothers you soo much? i think by now it's obvious that this hack is no longer in development and unsupported as you've said, so no reason to come back and check for updates or to read all the comments from other users... right? did you ever hear the statement about the guy that went to the doctor and told the doctor that his arm hurt when he moved it? the doctor replied to the man - don't move your arm then.

Look under my name, I am a member. I am not a coder on the level that a lot of these people are. I myself have helped in this thread several times. I would love to see this mod updated to 3.5.2 but I am not expecting it to be because it is listed as unsupported.

Helping in the thread as members is great, but leave the trash talk about the author out. Its old and tiring to read people saying someone abandoned a mod when it is clearly listed as unsupported and was written for a version that is several versions old now.

i agree that the trash talking should be left out... but as i've pointed out several times already, everything about this hack is confusing on soo many levels.

Before anyone comments on a mod, they need to read and see what version of VB the mod is for and if it is listed as supported. If it is for a different version of Vb and is listed as "unsupported", there is nothing to complain about. This mod WASN"T abandoned. It is several versions old and listed as unsupported.

i agree... to a point. developing a product for a beta release of anything is incomplete no matter what anyone thinks IMO! sure it may work for a beta release, but you have clear advanced knowledge that said product WILL eventually go GOLD and your hack may then become obsolete... perhaps within hours or even minutes until a next beta release or GOLD release. if you develop with the intention to only develop for BETA releases, this should also be stated... which clearly isn't in this case.