| Time |
Nick |
Message |
| 01:08 |
|
smk joined #minetest |
| 01:40 |
|
YuGiOhJCJ joined #minetest |
| 02:33 |
|
beanzilla joined #minetest |
| 02:38 |
|
beanzilla joined #minetest |
| 02:45 |
|
Bluebird joined #minetest |
| 02:47 |
Bluebird |
Ok, so I've run into a problem with `minetest.register_on_player_hpchange()`. The short of it is that the 'hp_change' argument isn't the actual amount of damage done --- it's the amount that the player's HP will change by, never allowing HP to go below 0. |
| 02:48 |
Bluebird |
This means I can't use 'hp_change' to know how much damage *would* be done by the weapon, in the usual case. |
| 02:50 |
Bluebird |
ATM I'm thinking that I'm going to have to save the 'damage' obtained from minetest.register_on_punchplayer(), and retrieve it later in minetest.register_on_hpchange(). |
| 02:50 |
MTDiscord |
<Warr1024> I ran into similar issues. It seems like the closest-to-sane thing to do is just lie to the engine, tell it the player has oodles of HP, then divert the damage to an alternate system. Unfortunately, that means you have to do all the work of establishing an alternate standard and maintaining an API. |
| 02:50 |
Bluebird |
Except that ... will not work if the damage is caused by a mob, I think? |
| 02:51 |
MTDiscord |
<Warr1024> hooking up the damage on punchplayer only works for damage done by mobs, and won't cover stuff like falling or environment damage. |
| 02:51 |
Bluebird |
Yes, your right (I hit enter too quicky, I see what you're saying) |
| 02:55 |
Bluebird |
Darn. I'm already using the max allowed HP range (0 - 65535) for players. |
| 02:56 |
Bluebird |
I may end up having to rethink the other problem that caused me to start looking into this. |
| 02:58 |
|
Bluebird left #minetest |
| 03:01 |
|
gxt__ joined #minetest |
| 03:10 |
|
Yad joined #minetest |
| 03:33 |
|
gxt__ joined #minetest |
| 03:35 |
|
sparky4 joined #minetest |
| 03:40 |
|
peterz joined #minetest |
| 04:00 |
|
MTDiscord joined #minetest |
| 04:15 |
|
est31 joined #minetest |
| 04:18 |
|
Verticen joined #minetest |
| 04:25 |
|
est31 joined #minetest |
| 05:10 |
|
Verticen joined #minetest |
| 05:47 |
|
Lesha_Vel joined #minetest |
| 06:38 |
|
calcul0n joined #minetest |
| 07:09 |
|
appguru joined #minetest |
| 07:47 |
|
Tomtom joined #minetest |
| 09:22 |
|
sparky4 joined #minetest |
| 10:29 |
|
appguru joined #minetest |
| 10:45 |
|
gemmaro joined #minetest |
| 10:58 |
|
definitelya joined #minetest |
| 11:04 |
|
Lunatrius joined #minetest |
| 11:11 |
|
proller joined #minetest |
| 11:40 |
|
Desour joined #minetest |
| 12:01 |
|
appguru joined #minetest |
| 12:28 |
|
Desour_ joined #minetest |
| 12:32 |
|
appguru joined #minetest |
| 12:58 |
|
est31 joined #minetest |
| 13:03 |
|
Desour_ joined #minetest |
| 13:15 |
|
illwieckz joined #minetest |
| 14:49 |
|
mrkubax10 joined #minetest |
| 15:34 |
|
Kilroy joined #minetest |
| 16:08 |
|
mrkubax10 joined #minetest |
| 16:11 |
|
Desour_ joined #minetest |
| 16:11 |
|
proller joined #minetest |
| 16:27 |
|
fling joined #minetest |
| 16:41 |
|
appguru joined #minetest |
| 16:43 |
|
Desour joined #minetest |
| 16:44 |
|
Desour_ joined #minetest |
| 16:44 |
|
dv^_^ joined #minetest |
| 16:51 |
MinetestBot |
[git] Desour -> minetest/minetest: GUIEditBox: Use primary selection 062b4d0 https://github.com/minetest/minetest/commit/062b4d036a38d21539f56d7ef8000dae094c46cf (2023-04-27T16:50:17Z) |
| 16:51 |
MinetestBot |
[git] Desour -> minetest/minetest: GUIChatConsole: Use primary selection e9e8eed https://github.com/minetest/minetest/commit/e9e8eed36065609b927b0a5a316771b887d1b316 (2023-04-27T16:50:17Z) |
| 16:52 |
MinetestBot |
[git] Desour -> minetest/minetest: Reduce number of recursively included headers 8b73743 https://github.com/minetest/minetest/commit/8b73743baacb710500b0efef5fbc4ba65d0ed28b (2023-04-27T16:50:33Z) |
| 16:52 |
MinetestBot |
[git] Desour -> minetest/minetest: Use json forward-declarations 7f6b09d https://github.com/minetest/minetest/commit/7f6b09dce82be5c2a881c075ca76c5ac8f84ad52 (2023-04-27T16:50:33Z) |
| 16:55 |
|
Talkless joined #minetest |
| 17:17 |
|
appguru joined #minetest |
| 18:12 |
|
definitelya_ joined #minetest |
| 18:19 |
|
appguru joined #minetest |
| 18:50 |
|
Yad joined #minetest |
| 19:05 |
|
Verticen joined #minetest |
| 19:19 |
|
sparky4 joined #minetest |
| 19:29 |
|
proller joined #minetest |
| 19:41 |
fluxionary |
is it considered a bug that if 1 item is aliased to another, they don't stack? i don't see any issues discussing this. |
| 19:58 |
MTDiscord |
<Jonathon> no idea if its considered a bug, but its something that some mods exist to patch/some mods check for this while others do not |
| 19:58 |
MTDiscord |
<Jonathon> seems worthwhile to file an issue as a feature request if nothing else |
| 20:29 |
fluxionary |
how would mods patch for fix this? |
| 20:29 |
fluxionary |
oh i see https://content.minetest.net/packages/SFENCE/items_update/ |
| 20:34 |
sfan5 |
nodes updates when aliased so why shouldn't items? |
| 20:34 |
sfan5 |
update* |
| 20:35 |
|
Lunatrius joined #minetest |
| 20:40 |
MTDiscord |
<Jonathon> never bothered to look why (yes, sorry), just know its an issue |
| 20:54 |
|
Lunatrius joined #minetest |
| 21:00 |
|
Lunatrius joined #minetest |
| 21:25 |
fluxionary |
alright i'll create an issue for it |
| 21:27 |
MTDiscord |
<Jonathon> i suppose its probably best to file it as a bug, always can change the labels later |
| 21:56 |
|
sid0 joined #minetest |
| 22:34 |
|
panwolfram joined #minetest |
| 22:50 |
|
fling joined #minetest |
| 23:06 |
|
Lunatrius joined #minetest |
