Posts: 6,485
Threads: 176
Joined: Jan 2012
Thanks: 131
Given 1074 thank(s) in 852 post(s)
12-29-2012, 01:05 PM
(This post was last modified: 12-29-2012, 01:05 PM by xoft.)
Cacti aren't entities, they're just blocks.
As for entity health, pickups have kinda health - they get destroyed when any kind of damage is applied to them.
Posts: 313
Threads: 32
Joined: Feb 2012
Thanks: 98
Given 14 thank(s) in 13 post(s)
What about dispenced arrows? How their TDI will be/should be transcripted?
Posts: 1,450
Threads: 53
Joined: Feb 2011
Thanks: 15
Given 120 thank(s) in 91 post(s)
Instigator / killer should be null then I think
Posts: 6,485
Threads: 176
Joined: Jan 2012
Thanks: 131
Given 1074 thank(s) in 852 post(s)
True, that does make sense - we might want to know which dispenser shot the arrow. Then the API would be incomplete. Any ideas?
This quite makes me inclined to really make the Attacker member a cEntity, so that it can point to the arrow being shot, and the cArrow would have all the info needed. So maybe it would make sense to move the weapon / armor API to cEntity, so that plugins don't need to check classnames all the time.
Posts: 91
Threads: 6
Joined: Dec 2012
Thanks: 1
Given 4 thank(s) in 3 post(s)
mmm, i just had an idea. Maybe you already considered and it doesn't work hehe... but what if you separate the damage portion of the API from the Weapon / Armor, and health . So you can give cEntity the ability to do damage, but they don't have "health or can wield Weapon and Armor to modify the damage sent.
Posts: 6,485
Threads: 176
Joined: Jan 2012
Thanks: 131
Given 1074 thank(s) in 852 post(s)
Too much work in case it isn't used by the plugins at all - too many cItem copy-assignments. Especially when we add enchantments to items, so cItem copy-constructor becomes non-trivial.