May I ship a generated DOF config with my little rumble project? Asking first :)

[kara2010]

Hi everyone,

 

first of all: the DOF config tool and the database behind it are a big part of
why my little beta project works at all, so before anything else - thank you to
arngrim and everyone who has fed table configs into it over the years. It is
genuinely amazing how much knowledge is sitting in there.

 

The project is this one, released today:

 

https://vpuniverse.com/forums/topic/14760-beta-gamepadrumble-dof-feedback-on-an-xbox-controller-no-cabinet-hardware/

 

In short, it lets people without any cabinet hardware feel shaker, knocker and
motor effects through the rumble motors of an Xbox controller. And of course it
only works because DOF and your config database tell it what happens on the
playfield.

 

Now to my question. For setup, every user currently generates their own
`directoutputconfig.ini` and `tablemappings.xml` in the config tool - I wrote a
step by step guide with screenshots for that, and it works fine. But it would
make things a lot easier for newcomers if I could simply include one
pre-generated config for a "cabinet" that contains nothing but the gamepad.

 

I deliberately did NOT do that, because the site terms say content from
VPUniverse may not be re-distributed or packaged, and I honestly was not sure
whether a generated config counts as that. Rather than guess wrong and step on
anyone's toes, I would much rather just ask:

 

1. Does a config generated by the config tool fall under that rule, or is the
   generated file considered the user's own?
2. If it does fall under the rule - would it be possible to get permission for
   this specific case?
3. And if the answer is no, that is completely fine too! The guide stays, people
   generate their own config, and everything keeps working. No hard feelings at
   all - I just did not want to do anything behind the community's back.

 

Thanks for reading, and thanks for all the work that went into this ecosystem!