PackIt - Multi-bag system [GUI] V1.2.2

[Rheiko]

Hello, thank you for the submission! Here's my review so far:

This system is cool and could be really useful — but right now, it lacks proper configuration options. Adding a new bag seems unnecessarily tedious. I have to duplicate triggers and manually change variables? That introduces a high risk of user error, and the system might break if something is set incorrectly.

A system should be easy to configure, especially for beginners. I assume that’s one of the goals of this system: ease of use. In general, users shouldn’t need to understand or touch the internal logic of the system. Instead, they should be able to change configurations via a dedicated configuration trigger.

So instead of having multiple triggers for each bag, consider using a smaller set of core triggers that handle all bags dynamically, and expose configuration settings through a separate trigger.

Duplicate triggers, while sometimes harmless, should generally be avoided — they can cause unnecessary performance overhead and make debugging harder.

Here are a few configuration values that should be exposed via a config trigger:

• Number of bags (no trigger duplication should be needed).
• Model used for the special effect and its attachment point (string variables work great here).
• Sound effect used.
• Unit type used as the bag.
• The ability associated with the bag.

Also, I recommend using a 2 to 4 digit prefix for all your variables. This helps avoid conflicts with other systems or triggers that might be used in the same map. See: GPAG - GUI Proper Application Guide

You mentioned the system could be made multiplayer-compatible by switching from Game Cache to Hashtable. So why not use Hashtable from the start? That way, users don’t have to worry about compatibility depending on the map type — it’ll just work.

In its current form, the system isn’t quite lightweight or beginner-friendly enough. That said, it’s a great idea and a promising start. I really hope you keep improving it — looking forward to the next version!

Cheers!

Awaiting Update

 

[SoyMante]

Hello, thank you for the submission! Here's my review so far:

This system is cool and could be really useful — but right now, it lacks proper configuration options. Adding a new bag seems unnecessarily tedious. I have to duplicate triggers and manually change variables? That introduces a high risk of user error, and the system might break if something is set incorrectly.

A system should be easy to configure, especially for beginners. I assume that’s one of the goals of this system: ease of use. In general, users shouldn’t need to understand or touch the internal logic of the system. Instead, they should be able to change configurations via a dedicated configuration trigger.

So instead of having multiple triggers for each bag, consider using a smaller set of core triggers that handle all bags dynamically, and expose configuration settings through a separate trigger.

Duplicate triggers, while sometimes harmless, should generally be avoided — they can cause unnecessary performance overhead and make debugging harder.

Here are a few configuration values that should be exposed via a config trigger:

• Number of bags (no trigger duplication should be needed).
• Model used for the special effect and its attachment point (string variables work great here).
• Sound effect used.
• Unit type used as the bag.
• The ability associated with the bag.

Also, I recommend using a 2 to 4 digit prefix for all your variables. This helps avoid conflicts with other systems or triggers that might be used in the same map. See: GPAG - GUI Proper Application Guide

You mentioned the system could be made multiplayer-compatible by switching from Game Cache to Hashtable. So why not use Hashtable from the start? That way, users don’t have to worry about compatibility depending on the map type — it’ll just work.

In its current form, the system isn’t quite lightweight or beginner-friendly enough. That said, it’s a great idea and a promising start. I really hope you keep improving it — looking forward to the next version!

Cheers!

Awaiting Update

Hi! Thanks for your suggestions. I'll work on a more convenient mode that uses fewer duplicates of the same trigger. When I have some free time, I'll work on refocusing the system better.

The reason I'm using GameCache is because the system, as it is, is focused on single-player, campaigns in general, or similar maps. Not multiplayer. That's why GameCache is necessary, since as far as I know, the hash tables only record and load data for the same map.

 

[Rheiko]

The reason I'm using GameCache is because the system, as it is, is focused on single-player, campaigns in general, or similar maps. Not multiplayer. That's why GameCache is necessary, since as far as I know, the hash tables only record and load data for the same map.

I see! If you ever want to make a multiplayer support for this that utilizes hashtable, you could make a separate system, so user can simply choose between the two. Just update the instruction, so they don't get confused.

Hi! Thanks for your suggestions. I'll work on a more convenient mode that uses fewer duplicates of the same trigger. When I have some free time, I'll work on refocusing the system better.

Awesome! glad to hear that. Looking forward to it.

 

[SoyMante]

I see! If you ever want to make a multiplayer support for this that utilizes hashtable, you could make a separate system, so user can simply choose between the two. Just update the instruction, so they don't get confused.

I'll work on that once I have the system more polished as it is.

Awesome! glad to hear that. Looking forward to it.

Update completed. I still need a way to further minimize user intervention. For now, I think the system is even clearer than before, and more automatic.