Standardized Macro Naming Conventions

[MakeGyver]

Hey guys,

Just an idea, can we have a standardized naming convention to help development of macros for this next COD title?
It'd make versioning and testing faster. It looks like most people are doing their own style anyways.

VKM:

• Weapon or Action
• Short Macro Description
• +Relevant Perks/Features enabled
• -Relevant Perks/Features not enabled
• Forum Username
• Version

example:
mk14.burst+kick-rapid.makegyver.8.vkm




maybe for VKS:
Short set Description
Forum Username
Version
Description for each page in notes.

Just throwing this out there, if people are down, someone could put the final standard in a sticky in the blops2 forum. Any thoughts?

-make

 

[WHITE 4ND N3RDY]

That is some good thinking but all that isn't really necessary. This will just make the vkm file name be to long. Ill break it down step by step. When u make a macro there is a description box. first it will ask the author then u put your name in then it will ask u to name your vkm file say MK14-RFperk+breath. Then there will be a description box below. there u will describe the macro and how it is to be used. EX. MK14 without rapid fire perk with built in breath. assign to right trigger or any tac button. Now u have a fully detailed vkm file and the vkm file name is short and to the point. Now when u want to share it to the comunity just make sure u put it in the proper forum. In the forum with blkops 2 NY jets has already broken down categories to file your vkm's in. there's one for rapid fires, jitters, fast reloads and miscellaneous for say turbo knifes, akembos, drop shots ect. So this being a rapid fire vkm id file it in that section of rapid fires for blackops2. Very important when you download your vkm in that section be sure to re describe what it does and how it works. I think this is where people get confused they just go by the vkm title not knowing how it works. If u ever assign a vkm u can go to the timeline editor and click on the gear box in the upper right corner and it will tell you everything u need to know about how to operate that file and what it does "if the person that made it did everything right". The way u want to do it isn't necessarily bad it just takes up too much letter space and it still doesn't explain how the functions work on it. If you got into a real detailed vkm with a lot of things going on u would run out of letter space to read the whole vkm file. As long as u keep the vkm title short and explain in the forum how it operates then people will get it.

 

[MJ23KB24]

Yeah not many people get confused on what your downloading plus in titles you are not allowed to put periods while naming files since the computer will try to read anything that comes after the period as a file extension.

 

[odingalt]

The general problem is we are not tending to our library of macros. The macro library needs a total re-vamp. For that matter, what would be the awesomer-est would be to have the Viking GUI have a screen added to the right-hand side that is a macro library, and do away with the on-line web-based macro library, and then have some sort of drag-n-drop.

Nothing I am going to add with the 360 macro controller unfortunately, but I can tell you, if we have a macro for the next gen console, I am going to dump some more money into the software and make up for all our shortcomings with the macro! Need better library integration and need better "monitoring" and tending of the library by staff. Also need youtube videos submitted with each macro to help people who are browsing the library figure out what it is they are downloading. Lots of ideas . . .

 

[akbigt]

like modio.....