Expanded getinventorylist:

[dastgirp]

Pull Request Prelude

• I have followed proper Hercules code styling.
• I have read and understood the contribution guidelines before making this PR.
• I am aware that this PR may be closed if the above-mentioned criteria are not fulfilled.

Changes Proposed

getinventorylist now creates extra variable named @inventorylist_idx, which returns items corresponding
inventory index.
It would be useful for #2394

Example:

	getinventorylist();
	for (.@i = 0; .@i < @inventorylist_count; .@i++) {
		dispbottom(sprintf("Index %d: %s (%d)", @inventorylist_idx[.@i], getitemname(@inventorylist_id[.@i]), @inventorylist_id[.@i]), C_AQUA);
		if (@inventorylist_id[.@i] == Beret && @inventorylist_expire == 0) {
			delitemidx(@inventorylist_idx[.@i]);
			dispbottom(sprintf("Deleted Index %d: %s (%d)", @inventorylist_idx[.@i], getitemname(@inventorylist_id[.@i]), @inventorylist_id[.@i]), C_RED);
			break;
		}
	}

Issues addressed:
None

[HerculesWSAPI]

This change is 

[AnnieRuru]

yup, tested working, however the example on *delitemidx has to change accordingly

[Emistry]

btw, if the idea of using inventory index to select/update/adjust item are approved, perhaps can consider to further expand it in future?

• compound card based on inventory index
• delitem based on inventory index
• refine item based on inventory index
• identify item based on inventory
• etc

summary, enable to alter/adjust the item state/info based on inventory index.

to be honest, the method we all have been using this whole time, delitem then getitem are ugly. I believe most of you know why its ugly, we aren't actually deleting an item, we're actually updating an item, so no point of deleting it and create unnecessary log.
its more precise if we take consideration when using script commands like equip, delitem, etc, inventory index allow us to pinpoint exactly the item we intended to update/alter, come in handy when there are multiple identical items appeared in inventory.

just saying ...