[Feature Request] Batch Operation for Favorites #1074

New Issue

MrUnknownDE · 2026-04-05T16:50:42+02:00

MrUnknownDE commented

2026-04-05 16:50:42 +02:00

Originally created by @LIII-Works on 6/1/2023

Explain in detail what your suggested feature would be used for.

The proposed batch operation feature would enable users to transfer worlds between collections in a more efficient and time-saving manner.

Describe how it would look if it requires a UI.

A button could be added next to the Export/Import button in the Favorites menu.

The interface would display a list of worlds from different collections, similar to the combination of the world collection and import menus. Collections could be expanded to show individual worlds with checkboxes for selection. Users could select favorites by clicking on the checkbox or on the item itself. They could then choose a target collection and initiate the transfer of selected favorites.

For VRChat online collections, if there are API limitations, batch operations could be processed slowly but automatically.

The process would involve:

Opening the Batch Operation menu
Expanding groups
Selecting favorites for transfer
Choosing a target group
Initiating transfer

Example:

Explain why people would want to use it.

This feature would benefit world travelers and players who use VRCX to manage world collections by significantly reducing the time required to transfer large numbers of worlds between collections. This feature is crucial for world travelers and players who use VRCX to manage large numbers of worlds in their collections.

Here is an example of why batch processing is needed

*Originally created by @LIII-Works on 6/1/2023* ### **Explain in detail what your suggested feature would be used for.** The proposed batch operation feature would enable users to transfer worlds between collections in a more efficient and time-saving manner. ### **Describe how it would look if it requires a UI.** A button could be added next to the Export/Import button in the Favorites menu. ![image](https://github.com/vrcx-team/VRCX/assets/56265123/39b8c810-26a7-42e9-9c7c-fe9fc755738d) The interface would display a list of worlds from different collections, similar to the combination of the world collection and import menus. Collections could be expanded to show individual worlds with checkboxes for selection. Users could select favorites by clicking on the checkbox or on the item itself. They could then choose a target collection and initiate the transfer of selected favorites. For VRChat online collections, if there are API limitations, batch operations could be processed slowly but automatically. The process would involve: 1. Opening the Batch Operation menu 2. Expanding groups 3. Selecting favorites for transfer 4. Choosing a target group 5. Initiating transfer Example: ![Untitled-1](https://github.com/vrcx-team/VRCX/assets/56265123/1164343a-52c0-4d20-93ca-c2187e8bb5f7) ### **Explain why people would want to use it.** This feature would benefit world travelers and players who use VRCX to manage world collections by significantly reducing the time required to transfer large numbers of worlds between collections. This feature is crucial for world travelers and players who use VRCX to manage large numbers of worlds in their collections. Here is an example of why batch processing is needed ![image](https://github.com/vrcx-team/VRCX/assets/56265123/30f20e47-c02b-42fb-a292-07b5f727cfd9)

MrUnknownDE closed this issue

2026-04-05 16:50:42 +02:00

Sign in to join this conversation.

No Label Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/VRCX#1074