(done) Suggestion: More than 3 attack methods

[Lord_BoNes]

I've noticed that even when I put more than 3 attack methods on an item, I can only use the top 3. I've tried to rework the base code, but the function sys_render_attack_method uses a "num" variable that seems to determine the number of attack methods that an item has... and this number seems to be capped to a max of 3. My suggestion is to add a new variable to global.lua that controls the maximum number of attack methods (something like METHOD_MAX would be good... with it obviously defaulting to 3).

[zoom]

what do you want to accomplish?
I can envision some "scope" on the weapon table
lets say a sword has a table with 3 actions
if fighter =LV"enough" display all 3 actions of that table

lets say a sword has a table with 5 actions
first,
display all 3 actions (1,2,3) as normal.
if dual wield, use a scope on the table for actions 2,3,4.
(still 3 actions to choose from in total)

so as I see it there is some shifting possible

[Gambit37]

Ha ha, interesting request: I'm actually *simplifying* the interface and removing the visible methods to make combat a bit faster and less fiddly.

[zoom]

Did you come any further with the simplifying, Gambit?

[Lord_BoNes]

I've created a more expanded interface, using the DM2 resources. It even includes the spell-casting gfx (the ones that show up in DM2 when casting, that represent a bit better what each rune does). And I've made the arrows completely disappear when you bring up the attack method menu... which has freed up quite a bit of room, enough for 5 or even 6 attack methods to fit in quite snugly above the console (which I have expanded to use 6 lines, instead of the usual 4).

[Sophia]

For the next version of DSB, I raised some hardcoded limits, so the engine will now recognize up to 16 attack methods.

This doesn't maximum actually have to be stored anywhere in the Lua code, because num passes the number of methods that are actually in use; this means the rendering code should continue to "just work."

[Lord_BoNes]

Sounds good to me. I'd imagine that 16 attack methods should be plenty overkill for almost any project