Time |
Nick |
Message |
00:00 |
|
sys4 joined #minetest |
01:11 |
|
Lesha_Vel joined #minetest |
01:13 |
|
sys4 joined #minetest |
01:23 |
|
smk joined #minetest |
01:36 |
|
sys4 joined #minetest |
02:28 |
|
___nick___ joined #minetest |
02:34 |
|
___nick___ joined #minetest |
05:00 |
|
MTDiscord joined #minetest |
05:05 |
|
Verticen joined #minetest |
05:08 |
|
gxt__ joined #minetest |
05:55 |
|
calcul0n joined #minetest |
06:00 |
|
mannerism joined #minetest |
06:16 |
|
AlexBrownSobinec joined #minetest |
06:33 |
|
AlexBrownSobinec joined #minetest |
07:07 |
|
definitelya joined #minetest |
07:58 |
|
sweetiebot joined #minetest |
08:03 |
lissobone |
OOOOOOOOOOOOOOOOOO |
08:04 |
|
Maverick2797[m] joined #minetest |
08:06 |
MTDiscord |
<ROllerozxa> 🤔 |
08:08 |
lissobone |
I've got a cool question. |
08:09 |
lissobone |
After a certain time, connection to a server times out. Â Is there a way to change this time? |
08:20 |
|
sys4 joined #minetest |
08:35 |
|
est31 joined #minetest |
08:47 |
|
mrkubax10 joined #minetest |
08:48 |
BuckarooBanzai |
lissobone: there's no such thing, how does the disconnect message look like, are you sure it isn't just the server restarting? |
08:58 |
MTDiscord |
<ROllerozxa> better question would be to ask: are you still trying to connect to my server? |
09:12 |
lissobone |
Yeah, why would I just give up? |
09:12 |
lissobone |
BuckarooBanzai: the message said that the connection had timed out. |
09:13 |
lissobone |
I am aware that I can just change the value in the code, but I would rather ask the wizards first. |
09:22 |
|
Warr1024 joined #minetest |
09:36 |
|
lissobone left #minetest |
10:18 |
|
Talkless joined #minetest |
10:26 |
|
fling joined #minetest |
10:47 |
|
mrkubax10 joined #minetest |
10:48 |
|
YuGiOhJCJ joined #minetest |
10:49 |
sfan5 |
network protocol timeouts are fixed in the code IIRC |
11:15 |
Krock |
CONNECTION_TIMEOUT (30 seconds) in Server::Server |
12:08 |
|
est31 joined #minetest |
12:25 |
|
YuGiOhJCJ joined #minetest |
12:29 |
|
YuGiOhJCJ joined #minetest |
12:29 |
|
appguru joined #minetest |
12:31 |
|
kilbith joined #minetest |
12:55 |
|
YuGiOhJCJ joined #minetest |
12:57 |
|
fr33d0m1 joined #minetest |
12:59 |
fr33d0m1 |
Anyone playing minetset on the pi 400? |
13:01 |
|
Talkless joined #minetest |
13:43 |
MinetestBot |
[git] SmallJoker -> minetest/minetest: Tile: Fix segfault caused by invalid PNG data 847ed04 https://github.com/minetest/minetest/commit/847ed04e0ad903b064f4f4a444d25f7cdc1130cb (2023-03-05T13:41:55Z) |
13:53 |
|
kilbith_ joined #minetest |
13:59 |
|
ChanChy joined #minetest |
14:08 |
MinetestBot |
[git] rollerozxa -> minetest/minetest: Minor adjustments now that OpenGLES 2 is the default driver on Androi… c91f3f9 https://github.com/minetest/minetest/commit/c91f3f99fdd81e37527b7208fbf0b6287421d779 (2023-03-05T14:07:40Z) |
14:10 |
MinetestBot |
[git] poggenpower -> minetest/minetest: Kubernetes: Deployments are stable since v1.16 4f06df7 https://github.com/minetest/minetest/commit/4f06df719d71923efe32457e3c43b9a854370afe (2023-03-05T14:10:22Z) |
14:33 |
|
grouinos joined #minetest |
15:15 |
|
AlexBrownSobinec joined #minetest |
15:58 |
|
stripeytype joined #minetest |
16:02 |
stripeytype |
Hi folks - I'm reading the wiki article re: minetest.conf; and running into some confusion because it is inaccurate regarding file paths. |
16:02 |
stripeytype |
Specifically, the notes about locations are ambiguous and incorrect. I would be happy to correct the article on the wiki but do not have permission to do so. |
16:03 |
MTDiscord |
<ROllerozxa> in what way is it wrong? |
16:03 |
stripeytype |
Would someone with wiki editing permission be willing to take some time to look at the document and correct it? |
16:03 |
MTDiscord |
<ROllerozxa> hi yes I have wiki editing permission, but I can't see where the issue is |
16:04 |
stripeytype |
Hi Rollerozxa. Specifically, the article makes the claim that minetest.conf is: |
16:04 |
stripeytype |
""" |
16:04 |
stripeytype |
../minetest.conf - (RUN_IN_PLACE version, relative to executable) |
16:04 |
stripeytype |
../../minetest.conf - (RUN_IN_PLACE version, relative to executable) |
16:04 |
stripeytype |
~/.minetest/minetest.conf - (globally installed version on Linux) |
16:04 |
stripeytype |
""" |
16:04 |
|
stripeytype was kicked by ShadowBot: Message flood detected. Use a pastebin like paste.ubuntu.com. |
16:04 |
|
stripeytype joined #minetest |
16:05 |
MTDiscord |
<ROllerozxa> that is all correct |
16:05 |
stripeytype |
Sorry. |
16:05 |
AlexBrownSobinec |
Geez |
16:05 |
AlexBrownSobinec |
That was not a flood |
16:05 |
stripeytype |
No, those paths are relative paths and reflect paths relative to CWD. |
16:06 |
MTDiscord |
<ROllerozxa> they are relative to the minetest executable |
16:06 |
stripeytype |
No , they are not. |
16:06 |
stripeytype |
The executable is installed at '/usr/bin/minetest |
16:07 |
MTDiscord |
<ROllerozxa> ...then you have a system-wide install, and the RUN_IN_PLACE locations won't exist |
16:07 |
stripeytype |
This would mean then that 'minetest.conf' would be installed at '/usr/minetest.conf' and '/minetest.conf' which is not at all the case. |
16:07 |
MTDiscord |
<ROllerozxa> when RUN_IN_PLACE=1, it will search in the parent and grandparent directory. when RUN_IN_PLACE=0 it will search in the user path which is ~/.minetest/ |
16:07 |
MTDiscord |
<ROllerozxa> I don't see where the issue is |
16:08 |
MTDiscord |
<ROllerozxa> if you've installed a RUN_IN_PLACE=1 build system-wide then that's on you |
16:09 |
stripeytype |
I mean, it's explicitly on the minetest package maintainers :D |
16:10 |
rubenwardy |
the lines that say "(RUN_IN_PLACE version" don't apply to you |
16:10 |
rubenwardy |
so it's just in ~/.minetest/minetest.conf |
16:10 |
stripeytype |
do you suppose that sort of language might be helpful in the documentation? |
16:11 |
MTDiscord |
<ROllerozxa> it already says which are for RUN_IN_PLACE and which are for system-wide installs, even explicitly for Linux installs |
16:12 |
MTDiscord |
<ROllerozxa> though I assume making it even more clear would be good |
16:12 |
stripeytype |
It seems reasonable to me to believe that the set of those people who run minetst at all and may wish to edit 'minetest.conf' contains but is significantly larger than the set of minetest developers who are familiar with the 'RUN_IN_PLACE' setting. |
16:13 |
stripeytype |
Is that setting an environment variable? |
16:13 |
MTDiscord |
<ROllerozxa> it's a build flag |
16:14 |
stripeytype |
Do you think maybe the documentation on how to use and edit 'minetest.conf' ought to me written with the audience in mind such that this specific domain knowledge is not a prerequisite for the document to be useful? |
16:14 |
stripeytype |
again: I would be happy to make the edit for readability, but I do not have that permission. |
16:14 |
|
linus joined #minetest |
16:15 |
|
lux joined #minetest |
16:16 |
stripeytype |
there are other minor problems; on a multi-user operating system, a user's $HOME is very much *not* a "globally-installed" location |
16:16 |
|
lynx joined #minetest |
16:17 |
MTDiscord |
<ROllerozxa> "globally-installed" means it's installed globally, as opposed to minetest being self-contained to $HOME |
16:17 |
MTDiscord |
<ROllerozxa> user data will still be specific to the user |
16:17 |
rubenwardy |
edited to clarify |
16:18 |
rubenwardy |
conflict, maybe not |
16:18 |
MTDiscord |
<ROllerozxa> ah yeah I edited it |
16:18 |
rubenwardy |
haha lol, I did the exact same thing |
16:19 |
rubenwardy |
like, same subtitle and structure |
16:19 |
MTDiscord |
<ROllerozxa> great minds think alike |
16:19 |
MTDiscord |
<ROllerozxa> anyways stripeytype is it better now? |
16:20 |
stripeytype |
That's a great edit, thanks very much. If I can, I'd propose changing the "system wide" language as well (because it isn't - each user gets their own copy, which is the opposite of what "system wide" means): |
16:20 |
stripeytype |
s/system-wide/per-user/ |
16:20 |
rubenwardy |
it is a system-wide install, there's just per-user information |
16:20 |
rubenwardy |
(system-wide on Linux) isn't needed though |
16:20 |
stripeytype |
yes, and the proposed change clarifies that. |
16:23 |
MTDiscord |
<ROllerozxa> rubenwardy: I think it points to somewhere slightly different on windows when RUN_IN_PLACE=0, though that won't matter since system-wide windows builds aren't exactly common |
16:23 |
rubenwardy |
yeah we don't have system-wide windows builds yet |
16:24 |
rubenwardy |
you can build it in that mode but it's not supported |
16:24 |
stripeytype |
thanks folks, very much. I really appreciate the clarification - it was confusing. |
16:26 |
stripeytype |
there seems to have been a discussion several years ago about also implementing per-world configuration: https://forum.minetest.net/viewtopic.php?t=15227 |
16:26 |
stripeytype |
Did that ever go anywhere or should it be disregarded? |
16:28 |
rubenwardy |
if you stumble upon anything else that is unclear let us know |
16:28 |
stripeytype |
Thanks very much |
16:28 |
rubenwardy |
Unfortunately not, per-world configuration is something that I'd like to see though as it will fix a few problems |
16:28 |
rubenwardy |
you can use --config when starting MT from a command line |
16:29 |
rubenwardy |
I use that to have different servers with different config |
16:29 |
stripeytype |
Yeah - that works well, I just didn't want to fall-afoul of some undocumented lookup |
16:33 |
stripeytype |
related-but-different question: if I move '~/.minetest/worlds/Foo' to '~/.minetest/worlds/Bar', will that break any references in minetest itself? That is, do I need to also make changes in minetest.conf or any of the sqlite DBs? or is it just a path and the game doesn't use the pathname for anything? |
16:40 |
|
fluxionary joined #minetest |
16:47 |
Blockhead256[m] |
the world's name will still appear the same in the world list instead of the matching that of the directory |
16:47 |
Blockhead256[m] |
to properly rename the world, edit `world_name` in that world's `world.mt` |
16:47 |
Blockhead256[m] |
other than that, there should be no issues, and that one is only cosmestic for the most part |
16:51 |
stripeytype |
Awesome, thanks very much! |
17:05 |
|
Desour joined #minetest |
17:52 |
|
mrkubax10 joined #minetest |
17:55 |
|
AlexBrownSobinec joined #minetest |
18:13 |
|
Oblomov joined #minetest |
18:33 |
|
est31 joined #minetest |
19:01 |
|
giov4[m] joined #minetest |
19:20 |
|
appguru joined #minetest |
19:34 |
|
mazes_80 joined #minetest |
19:44 |
MTDiscord |
<MisterE> wheres kilbiths docs for his camera lua api? |
19:45 |
MTDiscord |
<MisterE> nm, got it |
19:49 |
|
Trifton joined #minetest |
20:11 |
|
definitelya joined #minetest |
20:11 |
|
bwarden joined #minetest |
20:11 |
|
duds` joined #minetest |
20:11 |
|
amfl joined #minetest |
20:11 |
|
Lunatrius joined #minetest |
20:11 |
|
muurkha joined #minetest |
20:11 |
|
tel1 joined #minetest |
20:11 |
|
Pexin joined #minetest |
20:11 |
|
ghoti joined #minetest |
20:11 |
|
lumidify joined #minetest |
20:11 |
|
Thomas-S joined #minetest |
20:11 |
|
MinetestBot joined #minetest |
20:11 |
|
basxto joined #minetest |
20:11 |
|
nore joined #minetest |
20:11 |
|
Norkle joined #minetest |
20:14 |
|
Lunatrius joined #minetest |
20:16 |
|
AlexBrownSobinec joined #minetest |
20:20 |
|
sys4_ joined #minetest |
20:31 |
|
est31 joined #minetest |
20:39 |
|
gxt__ joined #minetest |
20:40 |
|
appguru joined #minetest |
20:51 |
|
sparky4 joined #minetest |
20:55 |
|
Desour_ joined #minetest |
20:58 |
|
TomTom joined #minetest |
21:14 |
|
Verticen joined #minetest |
21:15 |
MinetestBot |
[git] sfan5 -> minetest/minetest: Increase used IrrlichtMt version 9ef3c8c https://github.com/minetest/minetest/commit/9ef3c8ce388011f4f57adc9a7eb0326376aec750 (2023-03-05T21:00:27Z) |
23:03 |
|
sparky4 joined #minetest |
23:07 |
|
kilbith joined #minetest |
23:11 |
|
gxt__ joined #minetest |
23:13 |
Desour_ |
I find it funny how the icecube in #13285 looks for me like it's melting |
23:13 |
ShadowBot |
https://github.com/minetest/minetest/issues/13285 -- 🧊 Feature freeze time |
23:14 |
Desour_ |
at least in browser (but not in the browser tab header) |
23:16 |
rubenwardy |
haha |
23:22 |
|
proller joined #minetest |
23:40 |
|
sys4 joined #minetest |
23:59 |
|
sparky4 joined #minetest |