Remove equipment level requirement/make equipment untradable

[aceover9]

Is it possible to accomplish these things? I suspect there's some file I can edit, just not sure which one.

Here's the thought process behind this: I want players to not have to keep old armor around but I want them to still have to acquire/earn it rather than just have it traded to them.

Ideally the equopment would check their highest job level instead of their current job level so players would have to obtain the minimum level at least once but that sounds like it would be something not easily accomplished/implemented.

[Delaide]

Your sql table item_armor/item_weapon.
Please check https://wiki.dspt.info/index.php/Items, it will explain the sql table data, and the flags. For flags, check under the "item_basic" information, for the armor/weapons, check under the item_armor and item_weapon.

[aceover9]

Thank you for both the info and the link. This will help greatly.

[aceover9]

I see info about changing armor level requirements. Weapons don't seem to have a level entry though I'll checl the sql file again to see if I missed it. I cannot find anything about making a piece of equipment or a weapon untradable.

I'll be reading through a lot of that faq just so I know what can be done but that's one thing I haven't been able to find.

I'm also working on trying to allow spells like enfire and blaze spikes be cast on allies.

[jono659]

I cannot find anything about making a piece of equipment or a weapon untradable.

From the DSP Wiki

item_basic
Stores basic item information that is common to all items. For an item to exist, it must have an entry in this table.

item_id should match what is found in POLUtils or on ffxiah.com

subid Only used to display which item was sold on the AH

name is the long name of an item, such as flask_of_echo_drops. If you're scripting a file, this is the file name you should use - from Log Name (Singular) field.

sortname is the shortened name, such as echo_drops - from Name field.

stackSize determines if an item should stack, and how many should stack. The client acts a bit odd if you stack items that aren't supposed to be stacked, but generally will let you stack things like Frozen Giant Skulls if you want to improve the Dynamis experience, for example.

flags stored as a bitmask. Add values together. (Example, an ex scroll that could not be delivered would use 16384(ex flag) + 8192(no delivery flag) + 128 (scroll flag) = 24704). You can also remove flags (Turn an into a non-ex) by deleting the flag you want to get rid of from the current value (example: want to wield x2 mandau? flag="63552", and if you want 2, you need to remove the "ex" flag (ex flag = 16384). So, 63552 - 16384 = 47168. The flags set for this example are: Rare, Ex, No delivery, No sale, Can equip, No auction

Value Flag
1 wall hanging
2 obtainable from goblin box
4 usable inside mog garden
8 unknown
16 delivery inner
32 inscribable
64 no auction
128 scroll
256 linkshell
512 can use
1024 can trade npc
2048 can equip
4096 no sale
8192 no delivery
16384 ex
32768 rare

[aceover9]

Thanks for the info.

I saw that faq and it mentions a flag for trading to NPCs but does that flag apply to trading to players as well?

[Delaide]

The rare/ex is what will apply to you.

[aceover9]

So I would make every item ex or rare or perhaps both? Thanks for the response by the way.

[Delaide]

Take away the ex to make it player tradable, the rare if you want to hold more than 1

[aceover9]

Perfect! Thanks a lot for the help!