debian44 reports: We need campfire!! ... #770
Labels
No Label
1. kind/balancing
1. kind/breaking
1. kind/bug
1. kind/construction
1. kind/documentation
1. kind/enhancement
1. kind/griefing
1. kind/invalid
1. kind/meme
1. kind/node limit
1. kind/other
1. kind/protocol
2. prio/controversial
2. prio/critical
2. prio/elevated
2. prio/good first issue
2. prio/interesting
2. prio/low
3. source/art
3. source/client
3. source/engine
3. source/ingame
3. source/integration
3. source/lag
3. source/license
3. source/mod upstream
3. source/unknown
3. source/website
4. step/approved
4. step/at work
4. step/blocked
4. step/discussion
4. step/help wanted
4. step/needs confirmation
4. step/partially fixed
4. step/question
4. step/ready to deploy
4. step/ready to QA test
4. step/want approval
5. result/cannot reproduce
5. result/duplicate
5. result/fixed
5. result/maybe
5. result/wontfix
ugh/petz
ugh/QA main
ugh/QA NOK
ugh/QA OK
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#770
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
debian44 reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
I second that, that would be an awesome awesome addition for the adventuring experience in the game and source of many cool screenshots. But how to get there...don't know yet, but will hopefully find out in time.
I started working on this today, reviewing the new_campfire mod in my second dev environment. I couldn't make it run even with installing the mods it's depending on. This is weird, there must be some miscommunication between them as at least two of the three were even authored by the same person. So why won't campfire detect I have base material installed and enabled? Can't say much about the mod if I can't get it to run.
With the other dependency...I just hope it is fire plus, otherwise I can't really find a "fire" mod in the modslist (if it isn't in the default game)
update: realize the basic_materials mod unchecks itself whenever I boot my world up, even if I checked activate mod. How...why...
fire is a game mod of MTG, it´s in
minetest\games\minetest_game\mods\fire
not inminetest\mods
check if the dependencies of basic_materials are also activated
Thanks for the feedback, Bla!
I checked with Alias, he says it's a known bug where MT auto disables basic_materials in the modlist when any other modpack you have installed has basic_materials included already...but then it doesn't work because that mod you want to test/play needs the basic_materials from the modlist. And you can imagine I have a ton of mods installed to review so finding out which ones to yeet could be quite...tiresome.
Alias told me how to safely transport this mod over to my other test environment to test it in the YL environment where this dependency bug shouldn't happen.
Okay, first round of testing through. I did not like it. I found and installed the "old" campfire mod and liked that lightweight furnace feeling more. I would like to tweak that model though.
Update: found out this is not a 3D model, this is coded...that's actually amazing.
Banged my head against the wall for a couple of hours trying to get things to work. Will revisit the topic when I know a bit more about minetest and meshes.
Update: it clicked and I could import an old model I made and a textuer for it without a problem. Okay...that means I have more tools to play with as a dev in the future.
Update: breakthrough, I made a brand new 3D model for our own campfire today and textured it with some difficulty, but in the end successfully. Will tackle the mechanics of our own new mod the next session I am working on this.
Fixed in:
commit c593fae55d1943081386c56201e0d1c3f4d1a756
and
commit 4f7da950bc20d3d155a01c0b6a3c170c71a5db55