RPG Style Weapons + Upgrades + Player Stat Upgrades

[MunchGamer]

I don’t think changing a config file to add a new weapon really counts as “modding” IMO But I do see your point. Things like NPC (written) dialogue, texture filepaths and other sorts might also belong outside of the code.

[theagentd]

@loom_weaver

@theagentd

How much you need to complicate things mostly depend on what kind of upgrades that you have. If you want to be able to add and remove “buffs” and modifiers then you’ll need to keep track of the base value of the weapon and either compute the value every update or when a weapon’s stat modifiers change.

Exactly! With all entities represented as a simple data structure i.e. a HashMap, this becomes really easy. A damage buff/debuff is stored as a tuple of <String, Integer> e.g. “damage”, 10. Negative numbers are debuffs.

Store a list of them and calculate the final value only when you need it. Adding a buff to a weapon/item/mobile/anything is easy: just instantiate another tuple and add it to the list. Expiring buffs are a snap as well: just remove them from the list.

Okay, so now you’re storing weapons, their modifiers and items in HashMap<String, Object>s. Are you going to store player properties in a HashMap too? Game objects? I’d say you’re completely missing the point of object orientation. HashMaps also do not preserve the ordering of objects. This kills determinism for online games, and it might also be good to be able to control in which order for example modifiers are applied, because you’d want a +20% damage bonus to be applied before a +5 flat damage bonus so the % bonus is applied to the flat bonus too. What you’re doing is emulating objects with Strings in HashMaps. HashMaps themselves are in my opinion just a glorified emulation of references anyway, so you’re emulating objects and keeping them in emulated references. I’d stay far away from that kind of code if I were you… ._.

[loom_weaver]

@theagentd

Okay, so now you’re storing weapons, their modifiers and items in HashMap<String, Object>s. Are you going to store player properties in a HashMap too? Game objects? I’d say you’re completely missing the point of object orientation. HashMaps also do not preserve the ordering of objects. This kills determinism for online games, and it might also be good to be able to control in which order for example modifiers are applied, because you’d want a +20% damage bonus to be applied before a +5 flat damage bonus so the % bonus is applied to the flat bonus too. What you’re doing is emulating objects with Strings in HashMaps. HashMaps themselves are in my opinion just a glorified emulation of references anyway, so you’re emulating objects and keeping them in emulated references. I’d stay far away from that kind of code if I were you… ._.

Nah, the statistics are in the HashMap but the modifiers are stored separately e.g. in a List.