why not just make it a product? Then you don't have to do an install script. ;)

Yeah I agree with amy. Also it could be a lot easier to install / uninstall especially for the new people in here. ;)

Because ibProArcade does all bring its own file with it and the installscript just does the SQL-commands. To make one version for vBulletin 3.0.x and 3.5.0 it is most simple to keep this all the same :)

I don't want to hesitate too long with the release, but I will take a look on the possibility to make a "product"

Then again, I doubt a product XML file will be parseable by 3.0.x, which he already stated the hack should be compatible with.

3.0.x won't interpret this XML so it may reside there without any effect. The installscript will sure be there for 3.0.x

I will look what is the best way :)

Question. What if we had the old vB 3.0.X version already installed before we upgraded to 3.5.X? I would really like to know. o_o Is there gonna be an update script so we can keep our scores and settings? O_o;

As there are several 3.0.x versions around (stlmike did some "AllMod"-versions and spread them via ibproarcade-vb) you have to make sure that all db-tables for my extended version are existing... I will see if I can do some "db updater" for it.

If using my upcoming version of ibProArcade you can easily move from 3.0.x to 3.5.0 later as there is just little work to do (insert one plugin) and everything continues its work

I did not have an "allMod" version on my forum. :| Does that mean that you may need to make several db update scripts?

No, thanks for the tip - I will adapt the installationscript to detect if there are several tables existing and thus it will make sure to put everything in the right place.

Please do me a favour and send me information about your database-structure concerning the arcade-tables - I am waiting for your PM to compare :) Thx!

Sent as 2 PMs. :D (silly 20,000 character limit. o_o)