Version: , by Zachery
Developer Last Online: May 2017
Version: Unknown
Rating:
Released: 11-22-2005
Last Update: Never
Installs: 0
No support by the author.
Basicly, were are nearing the final stages of handing over the project to a group of coders so they will be able to continue the work. We would like to keep area51 open but matthew wants to use his license else where, since hies no longer directly involved. (That means we are sans one vB license for area51).
The uShop code is just about ready for a BETA test, it just needs to be packaged, documented, etc. Which will be the responsability of the new coders.
I will be announcing them over the next few days as we finalize some things.
Show Your Support
This modification may not be copied, reproduced or published elsewhere without author's permission.
For everyone enquiring about uCash: I would recommend not installing it as it is pretty buggy and has ways of cheating the system to earn $$$$$$$$$$ very easily.
I doubt the ushop developer team would use the existing code without updating it, so my guess is that ucash minor/major version will be notched up one when the shop is released..... besides which, whats the point of ucash without ushop?
Hats off to the developer team... I am able to assist with cross browser / XHTML compliance if required.
For everyone enquiring about uCash: I would recommend not installing it as it is pretty buggy and has ways of cheating the system to earn $$$$$$$$$$ very easily.
o rly? Well feel free to contact me or another developer with proof-of-concept code or detailed instructions for these exploits.
I don't know about the old developers, but *we* take this very seriously. Although, since I don't have CVS access at the time of writing this, I can't vouch for the uC code released (nor be held responsible for any bugs/exploits in the system).
As for the version number, I assume the hack is using a version number schema like "MajorVersion.MinorVersion.Build", which I assume means such serious bugs will bump the MinorVersion by 1, and possibly a Build increment as well.
o rly? Well feel free to contact me or another developer with proof-of-concept code or detailed instructions for these exploits.
I don't know about the old developers, but *we* take this very seriously. Although, since I don't have CVS access at the time of writing this, I can't vouch for the uC code released (nor be held responsible for any bugs/exploits in the system).
As for the version number, I assume the hack is using a version number schema like "MajorVersion.MinorVersion.Build", which I assume means such serious bugs will bump the MinorVersion by 1, and possibly a Build increment as well.
I realise it will most likely be a minor version upgrade (for bug fixes) but thought that maybe ucash would receive additional functionality and it was **possible** a major version could be reached.
Regarding the exploits... they are all listed in the ucash for vb 3.5 thread in the extensions forum.... please dont make me read it all again to pull them out... lol
Revan....From memory, I think one bug involved clicking preview over and over when making a post.... you got credited with each preview if I recall the post from the other thread correctly.
I realise it will most likely be a minor version upgrade (for bug fixes) but thought that maybe ucash would receive additional functionality and it was **possible** a major version could be reached.
Regarding the exploits... they are all listed in the ucash for vb 3.5 thread in the extensions forum.... please dont make me read it all again to pull them out... lol
I see... I will get on reading that at a later point.
Quote:
Originally Posted by rob30UK
Revan....From memory, I think one bug involved clicking preview over and over when making a post.... you got credited with each preview if I recall the post from the other thread correctly.
I see. Thanks for notifying me, I will look over the placement of the uC code before releasing the bundled version.
Quote:
Originally Posted by Regs
Still?
Have the 'new' developers met yet to plan things out or code anything?
Thanks,
~Regs.
Today we recieved a CVS snapshot. A CVS/SVN server is not yet operational (though I can setup SVN in 5 mins, as long as I have everyone on IM to give out usernames/passwords). As such, it is pointless to start any development/bugfixing because I would have to trust people to download the new files. I would much rather wait until we have a version control server setuo.
The new coders have not yet met, I have only seen PixelFx (excluding myself) and as I understood it there would be several coders.
Organising this meetup and talk is taking too long, and since Zak is too busy, I am going to try taking the responsibility. I have (yet again) requested a list of the new coders, as well as admin/ftp rights for the development forum so I can get it upgraded to the latest vB version as well as contacting the new coders to organise a meetup.
I will post again in this thread once I have more news, for now this concludes the status update.