Well... I would wait but... I GOTTA INSTALL! *installs*

Thanks again for the hack! I'll be sure to report any bugs!

[edit]why not use an "import product" file instead of the installer.php? I'd perfer this more as will others, since it makes it east to disable or uninstall the hack is needed.

Totally love the idea of this..

and I am really glad you got it to work with eBux too :)

thanks so much...

[high]* The Chief clicks install[/high]

Because this hack needs to add(/remove) and alter database tables, and I trust the vB XML installer system as far as I can throw a couch.
The hack installre system DOES reference to an xml file. Besides, I included an uninstaller as well, so there's no problems.
I refuse to work with install/uninstall code as vB did it.
Since eBux is similar to uCash in the money storage way, what works for one works for the other ;)


@everyone: Thanks for the comments, tis appreciated :)
Also Im glad to hear there haven't been any major problems off hand :p

Well, it was suggested as it is the point of vB 3.5 in most ways... as it does help the user manage the hack better, but meh, I'll still go for it since the hack is still awesome!
Actually, eBux has the option to convert the uCash to eBuxes, a nice feature they have :D So, yeah, shows they are similar in that aspect.

a early birthday gift thanks revan..

Well as I said, the hack DOES use the Product system to manage everything but queries. I don't feel comfortable working with that environment, and it makes upgrading a pain.
What if for instance some of you detected a template bug that required heavy editing? I couldn't update the zip because telling you to import the new XML as that would make it re-run the queries thus cause errors.
Id have to either bump version number or halt the fix.
Besides, I prefer Dreamweaver over the text boxes for install/uninstall code ;)
And finally, if the Product system is so fancy then why don't Jelsoft use it for their upgrades huh? :p j\k

*not trying to be rude* actually they use it to patch the software as an option instead of a full upgrade :P

Anyways, thanks alot for the hack. I perfer old school over new school, brings back memories and true RPG fun.

Arr I owned myself thar didn't I :p
Well I meant like upgrading to the next version, like 3.5.3 -> .4! So HA! XD

Revan you can use the version field to make the product xml queries run or not. or use IF NOT EXISTS in the queries themselves.

Dreamweaver can be used to edit the xmls ;)

Problem with my postbit thingy, see attachement.

Also, for the same thing in the attachment, would it be possible to make it collapsable, and have it collapsed by default? my postbit is quite large with my mods + the rpg postbit.