Athough you can edit the XML manually (if you really know what you are doing), but in 99,9999% of all situations this is not necessary.

OK, I must have the wrong concept in my head. Or I'm confused about something.

I thought that with this new system you would have to write the XML file essentially from scratch.

You can ... but i'd not suggest doing that, could give major headaches ;)

- Create a Product
- Create all the necessary Phrases / Settings / Plugins / Templates and make sure you select the product
- Add necessary Install/Uninstall code
- Export it

Done.

For some reason, it won't export vbulletin options for me...
It does export the vbulletin option phrases, but the option category itself (<options></options>) is blank... why?

Did you set the setting group + setting as vBulletin default?

No, I set it as non-default... I thought that it will prevent the setting to be deleted on vbulletin upgrade. Or no?

That's what I thought too, set them all to default otherwise it won't export. They should rephrase that...

Ok thanx.

As long as the setting it attached to a product, it will be fine.

Actually, it's not fine. It seems if you add settings to one of the default groups, they won't export unless "vBulletin Default" is set to yes. It also seems to not even save the title and description of the setting. Is this the way it's supposed to be?