Twitter and 1.2 patch

Hello!

I’m back on track and 2.0 is ready. I’ll be submitting today, should be available around next week. You can check what’s new here. Instructions on the update from 1.2 to 2.0 will be given next week.

There’s a new Twitter account for the plugin so that it’s simpler for me to post news, updates, and whatever. You might want to follow it if you plan to use VIDE, just to keep updated if anything comes up 🙂

Lastly, I’m uploading a small patch for 1.2. It fixes some important issues with SetNode and ActionNodes. If you’re not updating to 2.0 and wish to keep using 1.2, then you might want to apply that patch.

That’d be about it for now! Let me know if there’s anything I can help you with 🙂

VIDE Dialogues will no longer be free

VIDE started out as a personal project for personal use. I never expected it to be successful-ish.

Starting from the next update (2.0) VIDE Dialogues will no longer be free.
I initially launched it for free so as to get feedback from users and see if it turned out to be a useful tool. Since then, I’ve been reading your feedback, helping out those with bugs and issues, and working on updates to improve it, and despite the fact that I enjoy doing so, the task has become time-consuming. I thought on submitting a “Pro” version instead, but that would be even more time-consuming.

I’m aware that VIDE doesn’t offer a number of features that some other paid assets offer as it focuses on delivering raw data, so I’m not planning for it to be expensive, at all. Regardless, the price point is still TBD.

Of course, those who already own the asset will not have to pay for anything. So, if you haven’t yet, this is your chance 🙂

As a paid asset, I’ll be more actively working on improvements. Some of the things I plan to add/change for the next update: Check here

Thanks for your understanding.

 

 

 

 

 

Preview VIDE 1.2

[EDIT]
I’m actually gonna get rid of the Editor Tools window and put everything into a toolbar before uploading. YOLO
[EDIT]
DONE

main

The small update turned out to be a bit bigger than expected. It was a fun weekend 🙂

Here’s a preview of what VIDE 1.2 will be bringing:

  • Fixed VIDE_Data loading wrong dialogues (with an offset) after creating or deleting new dialogues.
  • Add sprites to your dialogues and nodes! Select default Player/NPC sprites from VIDE_Assign component and/or set a specific one for each node. Access the sprites through VIDE_Data.assigned.defaultPlayerSprite and NodeData.nodeSprite. Sprites should go inside Resources.
  • Brand new Extra Variables system. Store strings, ints, floats, or booleans as values. Access the objects from the extraVars dictionary using custom keys. Deprecated extraData is still available, though it will be removed in a later version.
  • Added UpdateExtraVariables method to modify Extra Variables at runtime.
  • Added ‘extraVars’, ‘nodeSprite’, and ‘dirty’ variables to NodeData.
  • Added buttons to expand/collapse window content to free space.
  • Added checkbox to disable the performance view when panning inside the VIDE Editor (Empty nodes when panning).
  • Inspector multi-object editing is now supported for VIDE_Assign component.
  • Updated exampleUI.cs and example1 scene with sprites and extraVars.
  • Updated documentation.
  • VIDE_Data’s methods and variables are now static and can be accessed from anywhere; instance no longer needed. You’ll have to update your scripts.
  • Renamed VIDE_Assign.dialogueName variable to VIDE_Assign.alias. You might have to set the names again for every VIDE_Assign component and update your scripts. This was a necessary change as ‘dialogueName’ was misleading.  

NOTE: The last 2 changes in the list will require you to make some changes on your VIDE_Assign components and manager scripts, keep this in mind when deciding whether to update or not.

  • When changing dialogueName to alias, the string field gets reset. You’ll have to input the custom name for any VIDE_Assign that was previously using the dialogueName variable.
  • You no longer need an instance of VIDE_Data in your script to access the contents. Now, whenever you are referring to a class, variable, or method inside VIDE_Data, you will type, for example, VIDE_Data.Next(). This change was made as to allow easy access to VIDE_Data without the need of referencing. You still need 1 VIDE_Data component in your scene.

 

Extra Variables replaces extraData, and you can modify them during runtime! Extra Data will still be available to use but will be removed in a later version.

Set default sprites from VIDE_Assign and node-specific sprites from each node. Sprites must be stored inside a Resources folder.

Remember to check out the updated Documentation and exampleUI.cs for reference. CrazyCap demo character is even crazier now!
Capsule_Wowed

The update should be available before this weekend.

Cheers 🙂

 

 

VIDE Dialogues 1.1 coming pretty soon

I’ve been working on a big update.
It includes Action nodes as a new type of node. Action nodes will add much more dynamic to the dialogues you create by easily calling methods from your scripts.
Also, new features and fixes coming along with the update.

I’m looking forward to uploading for approval during the weekend. It gotta go through some testing first.

🙂