Before I do that, I need to give an example to contrast with the title and prove that this is a bug: For the attribute "attack_damage": If I want to increase my attack damage by 32768:

/attribute @s minecraft:attack_damage base set 32768

Or: /give @s minecraft:netherite_sword[minecraft:attribute_modifiers={modifiers:[

{slot:"mainhand",type:"attack_damage",id:"base_attack_damage",operation:"add_value",amount:32760}

]}]

They can all work.

But if the attribute is "entity_interaction_range": If I want to increase my entity interaction range by 32768:

/attribute @s minecraft:entity_interaction_range base set 32768

It worked.

/give @s minecraft:netherite_sword[minecraft:attribute_modifiers={modifiers:[

{slot:"mainhand",type:"entity_interaction_range",id:"creative_mode_entity_range",operation:"add_value",amount:32765}

]}]

It does not work.

The problem is that some attributes work only with the "/attribute" command, but not in the data component format.