ag_smith 0 Posted May 30, 2003 Don't you think guys that OFPEC tags naming convention should be applied to new classes added in CfgSounds, CfgSfx, sections (etc.) as well as for new weapons or vehicles? Currently (as far as I can remember) even BAS addons are not compilant to this "standard". Since there's possibility to add custom sounds for animations, many new sounds have been attached to addons recently. It's just a matter of time when some nasty conflicts will arise  I want even mention that some of well-known addon teams (name it TOW) don't use proper class names even for their weapons (recent M24 pack relase) or units.  Please post some constructive replies here ("I agree" is most welcome  ) Share this post Link to post Share on other sites
theavonlady 2 Posted May 30, 2003 Using AMORE file naming conventions complies to this - almost. Class names in AMORE are: Amore_ofpecTag_anyname. The "Amore" prefix is required because the AMORE repository contains audio files from multiple contributors. Interesting how all these audio file threads are popping up all fo a sudden. Details on AMORE can be found on the AMORE section at The FAQ. Share this post Link to post Share on other sites
theavonlady 2 Posted May 30, 2003 Incidentally, OFPEC has given its blessing to the AMORE standard. Stay tuned for additional details. Share this post Link to post Share on other sites
ag_smith 0 Posted May 30, 2003 Hmmm, I was going about the sounds that come with addons, ie. door sounds, ramp sounds, that kind of stuff. AFAIK Amore is meant for music, radio phrases, etc, ? Share this post Link to post Share on other sites
theavonlady 2 Posted May 30, 2003 Hmmm, I was going about the sounds that come with addons, ie. door sounds, ramp sounds, that kind of stuff.AFAIK Amore is meant for music, radio phrases, etc, ? Depends. If the sounds are reusable for additional addons and you don't want to pack copies of them in every separate addon file, then AMORE fits the bill. Share this post Link to post Share on other sites
ag_smith 0 Posted May 30, 2003 Anyway, I want EVERY serious addon maker to read this and then remember about it when creating config.cpp. Share this post Link to post Share on other sites
dinger 1 Posted May 31, 2003 everything that uses a class should be tagged. every addon with a script using global variables needs to tag those variable names. Share this post Link to post Share on other sites
kegetys 2 Posted May 31, 2003 I thought the ofpec tagging already required you to use the tag on _all_ classes you add by the addon, inluding not only in sounds, but also in CfgModels and thus in the model name too... Share this post Link to post Share on other sites
VXR 9 Posted May 31, 2003 from the OFPEC site Quote[/b] ]OFP Tags are used in the following: Global variables Global function names New classes (in config.cpp files) P3D names Mission and addon PBO names A 'tag' is simply a three to five letter identifier that is individual to each designer. Here at OFPEC we have created a listing of all these tags, so that people can see who 'owns' particular tags and we don't have multiple designers using the same tag. Share this post Link to post Share on other sites
