[Suggestion] Map and Event Plugin Param Types

[MakoInfused]

Description of the Feature:

• A dropdown/picker UI for plugin params of @type map.
• A dropdown/picker UI for plugin params of @type event. (Which would also require a map selection)

Mockups:
Map picker:

Event picker:


Why is this feature good?
This feature is great because of the following:

• Plugin users can get a visual representation of the map and events they're selecting.
• Plugin developers will have an easier time to make use of the input of plugin users.

Possible issues with this feature?
Issues that might arise from this feature:

• None that I can think of.

 

[Tsukihime]

I like it.

 

[Alexandr_7]

The editor does not interact with plugins. Only the game interacts with plugins. The editor only interacts with annotations and only in certain places. The editor does not interact with the plugin code in any way and they will not change it. If your suggestions concern the editor and js code of plugins, then it is doomed to be rejected.

 

[MakoInfused]

The editor does not interact with plugins. Only the game interacts with plugins. The editor only interacts with annotations and only in certain places. The editor does not interact with the plugin code in any way and they will not change it. If your suggestions concern the editor and js code of plugins, then it is doomed to be rejected.

Perhaps I described this feature incorrectly then, maybe you can help me describe it in a better way?

Essentially what I'm trying to suggest is a way for plugin developers to provide a @param with a @type of event, or map. Similar to how we can allow a @type common_event. This will allow users of the plugin to select a map or map and event combination from a dropdown, using the actual data from the project. If I can improve on my description in anyway, please let me know. Thank you!

 

[Trihan]

Personally given that there's a @state parameter type I'm not sure why the other database types weren't added, and this would certainly be a useful one for plugins.

 

[MakoInfused]

Personally given that there's a @state parameter type I'm not sure why the other database types weren't added, and this would certainly be a useful one for plugins.

I agree completely! This feature I suggested isn't really anything extraordinary, most of the work for this is potentially already mostly done. Plugin developers should have access to the current state of the all of the database objects, in order to be able to create more robust plugins with ease!

Thank you for your input!

 

[Trihan]

What I really want is conditional parameters i.e. ones that are only visible/selectable when another parameter has a certain value.

 

[MakoInfused]

Kinda like how in the editor when a user selects a specific radio button all other parameters will be greyed out? That's a great idea, I'd vote for it!