Ambiera ForumDiscussions, Help and Support. |
|
|
|||||
|
If you develop extensions you will notice it can become confusing. action_MoveElastic.js or something like that are customised for every different project you have. Then when you load some example project to learn from then these extensions are added to your CC Editor aswell. My dumb and simple solution is this: My ccb projectfile is let say named ScaryHillGame-v3.24b.ccb with version number v3. iteration 24 variation b all, that means every extension (actions + behaviors) that I use in this file are named the same like this: action_shMoveElastic.js behavior_shMoveElastic.js the added sh letters are keeping my extensions nicely together in the windowsExplorer window, where sh ofcourse stands for ScaryHill. Then every extension gets a description that reflects the game file it is intended for like this:
the description="sh: are keeping my extensions nicely grouped together in the CC Editor ExtensionExplorer window. Hopefully you find this little trick usefull. |
||||
|
Good! An interesting thing! |
||||
|
|
){kind=link}