Feature Request: Various QoL Features about legendaryexplorer

[SirCxyrtyx]

QoL Request 3 - Shift Multiple Objects
This exists already, though you can certainly be forgiven for not having found it. In Pathfinding Editor, select Experiments > Show Experimental Level Tools. This adds two new tabs to the panel on the left, Groups and Level Tools. Right-click on objects and select Add To Group, then use the Level Tools tab to translate and rotate the whole group. Visibility and usability of this tool should definitely be improved.

QoL Request 10 - Autosave
My worry with this is that saving a file necessarily entails changing it if any edits have been made. Not sure it's a good idea for that to happen automatically.

[Mgamerz]

My thoughts:

1. This has been discussed internally before but just hasn't had time dedicated it for implementation - delete key functionality.
2. This is somewhat implemented in CrossGen-V. I don't know how much work it would take to bring over. It's tricky cause you essentially hack the relinker.
3. Don't know a bunch but the code is all single-object selection right now. A hack could be added for multiple move but it wouldn't be trivial.
4. The color wheel is provided by a third party library - I don't think we've ever looked at how it actually works. There might be better color wheels than Xceed's.
5. This has been discussed - might be possible with the script decompiler being able to read properties, even though it's not on a defaults block.
6. Porting preview would be a great feature but it's pretty unrealisitc because until you actually pull things into the file you don't know what you actually need. The relinker is an unfathomably complicated piece of code. Even when working internally it is difficult to find why something is being brought over.
7. We have code to open the highest mounted file already, we use it pretty extensively. Probably wouldn't be hard to add this.
8. You can hold shift and drag to relink entries already.
9. Seems reasonable. Note: We have code that re-uses trashed exports so you have to be careful with this, if you try to restore, it may point to another export that was re-used from trash.
10. This could potentially be done. I don't see much that would stand in the way of this beyond some time.
11. Probably could just be a dialog 'Do you want to correct the yaw?'

[ElysiumFic]

Am I allowed to suggest Dark Mode might be a nice feature? (If it's already available, I haven't been able to find it.) I'm a huge night owl and opening Package Editor blows my eyes out.

[AudemusN7]

QoL Request 11 - Clone to Another Sequence

Sequence Editor has a clone object button, which is super useful. But many times it may be needed to clone that object to a different sequence in the package. Currently, the only way to do this would be to

• Clone the object
• Remove it from Sequence A
• Go to Sequence Band add the new export to the array
• Go to the new sequence object in package editor and correct the instanced path from Sequence A to B
• Correct the parent sequence on the object.

So this QoL request is for a new RMB menu option called "Clone to Sequence" where you select the object and it gives you a drop-down list of all the sequences in the package. When you select it, it automatically clones the object to that sequence instead, negating the need to do any of the above.

[SirCxyrtyx]

There's actually a simpler way to do that currently.

• Clone the object
• Remove it from Sequence A
• Go to new sequence, right-click and select Add Existing Object (or select Tools > Add Object from the menu.)

This isn't ideal of course, as you have to remember the UIndex of the object. Perhaps a Copy RMB option on the object and a Paste RMB option on the canvas (that would work across sequences)?

[AudemusN7]

QoL Request 12 - Correct Object Index on Porting

Sometimes when porting objects between packages it can be troublesome when there are existing objects in your destination package that share a class/object index with those in your source package. While sometimes you may want for these matching objects to be ignored, if you don't want them to be ignored then you currently need to go through every object and manually correct the indexes to ensure there are no duplicates before importing. Otherwise, certain objects will not port into the destination package, and will instead reference the existing object in the package.

For the QoL request, I propose a checkbox added to the porting dialogue which changes this behaviour. When checked, any objects being ported will automatically have their object index corrected and will then be ported into the package. This already exists when porting an object directly, but when these objects are referenced externally (such as when porting a sequence) this is not currently taken into account.

This feature would reduce a lot of headaches, repetition, and mistakes when porting.