Gob Sack

[Seriha]

I still think you're sending pointless data with your proposed equipment method. As long as something isn't actively happening to change your stats, a performed action, either by or to you, can be pulled indefinitely from the stored data collectively harvested through base stats, (de)buffs, and gear. It's also more friendly to the tic system since the server doesn't have to ask the client if you're wearing something with regen/refresh/regain/etc. for each and every slot every 3 seconds because it should already know when those parameters were set involving the related stats. It also basically parrots monster stats since while they don't wear gear, side-by-side, they should look exactly like players when it comes to all possible parameters used to calculate combat data.

As for auto-attacking, it wouldn't be 'auto' if didn't loop. Haste/Slow aside, the act itself technically doesn't need to know our stats to run on its own, but rather they're queried to determine the result for when it can be successfully performed. The loop, in turn, ends if we die, the mob dies, or we disengage and is subsequently paused when the target is out of range/out of our frontal cone/we're slept/stunned or another action is performed like JA/WS/Magic/Item use. But as long as we're basically flagged for being in combat via /attack on, ctrl+a, or whatever, it will want to try and run forever. If that's not a loop, I don't know what is.

[Lokithor]

Gear is all managed server side to avoid client side hacks that would allow you to obtain any gear you like. Things that are not vetted server side are hackable (flee hack anyone?).

[Arcon]

I'm fairly confident that melee attacks are handled server-side only. The client does not send regular attack-data to the server. It's the reason why we can attack moving mobs by walking ahead of them and looking in the same direction as them. Because the server thinks that you're in optimal melee range, so it commences an attack. If that was handled client-side, the client would have no reason to start an attack when you're in front of the mob. Also, if that was the case, it could be hacked to attack faster than you should under normal circumstances (think Attack-button).

The way I think it works is like this, all of this below is my opinion, and largely unverified, but supports the observations I make around FFXI enough to form a stable platform:

"Gear" data does not actually store any stats at all. Only the slot, charges, and job, race and level requirements are actually stored in an item, the rest is just text. The game isn't aware of the boni to attributes, it just displays the items in the appropriate slots, and changes the graphics to reflect that.

All the stats of the gear is handled server-side. The client only receives the attributes of the player from the server. This includes STR, DEX, VIT, INT, MND and CHR stats, the boni to those attributes (the green +X), HP, MP, TP, Attack, Defense, skills, elemental resistance and job levels. It uses that data to display the values on the screen, but doesn't actually calculate anything. Otherwise it would have to know the potency of a buff as well (like the potency of March, which depends on the BRD's skill). The only stat it uses to actually calculate anything is movement speed.

The gearchange is always handled server-side. The client can only send commands to change it, the server decides when it's actually being changed, or if it's changed at all. A player's stats are updated every time gear is changed, the stats are saved in the server's player profile. So as soon as the gear is changed, the new stats take effect. These are then (periodically) sent to the client, so it can display the new values. This does not happen with the gear change, but it certain intervals, which is why Attack and Defense values sometimes seem to update "delayed" from an actual gearchange.

This is how I see it, and it seems to coincide with what's going on in the game. The stuff about R0ing I'll have to try out by forcing a R0 and see what I can do, I can't speak to that yet.

[Ashay]

I think it's safe to say we'll have to wait for some dev. feedback to know for sure whether or not this can be implemented. I'd imagine it would take time, but given that it would make things easier for players, I'd think they would want to do it.

[Amador]

It would be very sad not to be able to see this level of utility when it comes down to inventory, macros and overall potential found within these ideas.

The idea of being able to use Mog Sack and Satchel as Inventory 2 and 3 to be macro-able in terms of: /equip2 ring1 "Dark Ring" /equip3 ring2 "Dark Ring" /equip2 ear1 "Loquacious Earring" and so on would allow for better management of equipment in terms of MDT, PDT, TP, WS sets.

It would also allow for certain same name objects such as Dark Rings to not conflict with one another when used in the same Macro List since they would be pooled into your equipment. However, if this is a bit much it could be further simplified to add a "Gobbie Sack" which would be for holding equipment that can actually hold gear that can be macro as a /equip2 while keeping the others the same.

[Lokithor]

If the purpose of all of this is to be able to equip gear from 2 or more inventories, then maybe we also need to clarify other expectations. For example, items that are in your inventory can also be "used" from the items list. Things like food and equipped items with enchantments. There's also things that are consumed through game actions such as ninja tools and ammo. Maybe to cut the developers some slack, "usable" items would all still need to be in the main inventory.

[Amador]

It would be decent to be able to use items from an inventory other than the main one.

I for one dislike carrying all of my pop items, medicines and such on my main inventory. I tend to keep them in the satchel, or mog sack. So it is a bit of a hassle to dig them out, make room, use them, put them back and such.

So that too would definitely be nice looking into.

[Swords]

Well here's an offshot idea. We currently know that it's impossible to expand the current gobbie bag beyond 80 do to coding limitations, but what if they were developed into a organizational sub-bag type architecture, by breaking up the bag into smaller sections.

Essentially everything in your Gobbie bag would be broken up into categories like med's/food/head/body/feet/misc items/etc. Each of these categories would be treated like it's own individual bag up to 80 slots. The Macro's behavioral programming might have to be adjusted somewhat to address the change, but depending on how it's setup SE wouldn't likely have to worry too much.

But, that's just a random thought that might work.

EDIT: I didn't read past the first few posts btw, so if someone already posted a similar idea I apologize in advance.

[Seriha]

It's been brought up, and I'd generally be okay with that. Since my point of contention was that equip commands could be told where to look, /equipsack or /equipsatchel is basically the same as /equip feet "whatever" since the slot marked would be the pointer. In terms of gobbie bag quests, I guess people could start with 5 slots in all equipment areas, each one adding +2 each, ending in 25 slots (more than enough for people to start lugging around 8 staves/obis/gorgets/belts). A useable item section or general drop pool can remain at 80.

[Mirage]

Doesn't your character keep auto-attacking the mob you're engaged to even a short while after you've lost connection? That should be plenty of evidence of the client not sending auto attack data at least.

I also just skimmed most of this thread but if you didn't already think of this, it might worth knowing that if you use something like plasticsurgeon to change your appearance client-side, the client will no longer allow you to equip race-specific gear of the race the client thinks you no longer are. It stays on if you put it on before "changing" race, though.

Of course, I have never done this personally, I watched a friend who no longer plays do it.