Skip to content
This repository was archived by the owner on May 24, 2022. It is now read-only.
This repository was archived by the owner on May 24, 2022. It is now read-only.

Intel Items: Suggestions for Improvement #233

Description

@Drofseh

Is your enhancement related to a problem?
I'm setting up some intel items for a mission and I've encountered a couple of things that I feel could use QOL improvements.

Solution you'd like:

  1. Documentation
    Right now there is no documentation on the Ace3 Wiki. A small entry that mentions how the 3DEN Attributes for the items work (will they accept structured text, what filepaths can be used for the photo item) and gives an example of acex_intelitems_fnc_addIntel would be nice.

  2. Inventory Management
    Because of the limited number of item classes available to use when I have more than one of the same class I can't know which intel item I will drop when I want to pass it to another person.
    For example, if item X and item Y are both acex_intelitems_notepad and I want to give someone only item Y there is no way for me to know which will be dropped.

    Possible solutions would be to add an ace interaction node to drop the item, or to use unique classes and serialize them in the same way that ACRE2 does with radios. A serialized solution could also make use of Item Rename Framework CBATeam/CBA_A3#1329.

  3. Pickup Interaction
    Right now the condition for picking up the items includes a check for inventory space.
    This made me think the addon wasn't working properly until I realized my inventory was full leaving no room for the item.
    I think it would be better to have the condition to pick to be true and have the inventory space check happen in the statement, if not enough room is found then output a hint saying so.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions