1.1.118 #3401

Closed
opened 2023-01-01 16:19:26 +00:00 by AliasAlreadyTaken · 37 comments

new mods/features:

  • (ready for QA) #21 choppy
    • (ready for QA) #3066 woodcutting tries to violate protection
    • (ready for QA) #3174 woodcutting w/out an axe
    • (ready for QA) #3738 woodcutting giant ferns
    • (ready for QA) #3789 node replacer triggers woodcutting
    • (ready for QA) #3865 choppy & unified trees
  • (ready for QA) #777 playeranim
  • (ready for QA) #2049 Cheese mod
  • (ready for QA) #3453, your-land/yl_statuseffects#1 basic builders' flight
  • (ready for QA) #??? draw line mod by debiankaios
  • (ready for QA) #??? nerdpole reporting by Ravise
  • yl_settings your-land/administration#114

major updates needing integration:

  • (ready for QA) #2915 moreblocks/stairsplus
    • (ready for QA) #1255 ethereal:slab_crystal_block does not glow
    • (ready for QA) #1370 moreblocks:slope_stone digs as morebloks:slope_cobble
    • (ready for QA) #1518 invsaw for creative players
    • (ready for QA) #1731 allow placing stairlights on moreblocks stairs
    • (ready for QA) #1792 saws lose materials
    • (ready for QA) #1981 saws are confused about the cost of various things
    • (ready for QA) #2251 cut node recipes missing from guide
    • (ready for QA) #2399 no group slab_wood_8
    • (ready for QA) #3349 inconsistent microblock SFX
    • (ready for QA) #3488 remove microblock craft schemata
    • (ready for QA) #3527 microblock conversion rates are inconsistent
    • (ready for QA) #3662 hide/remove deprecated moreblocks tiles from before facedir
    • (ready for QA) #3669 no-faces trees don't work right in the saw
    • (ready for QA) #3820 saw-able category in unified_inventory
    • (ready for QA) #3823 saw loses material (not the same bug as the other similar things)
    • (ready for QA) #3966 crafting 2 1/16th slabs gives a single 1/8th slab, though each 1/16th slab requires 1/8th a node of material.
  • (ready for QA) #3683 sandwiches
    • (ready for QA) #2232 bonemeal on peanut crops
    • (ready for QA) #3537 cucina_vegana:peanut_seed duplicates sandwiches:peanut_seed
    • (ready for QA) #3703 attempting to override unknown item sandwiches:blackberry_jam
    • (ready for QA) #3711 cooking peanuts is borked
    • (ready for QA) #3791 Could not load image "sandwiches_peanut.png"
    • (ready for QA) #3843 Recipe for Blueberry jam sandwich broken.
    • (ready for QA) #3904 recipe for hot veggie sandwiches broke again
  • x_bows #3684

bugfixes ready for QA:

  • #2644 [arena_lib] (minor fix)
  • #3614 [petz] can't place fish
  • #3185 [petz] fishtank - warn when trying to put wrong items into it
  • #3232 [petz] glitchwolf
  • #3600 [petz], [mesecons_debug] HUD problems
  • #3616 [petz] show wrong value when healing
  • #3504 [petz], [skinsdb], [3d_armor] fix broken emotes
  • #3314 [petz] thrown object improvements
  • #3022 [skinsdb] missing hands
  • #3612 [unified_inventory] minor UI bug
  • #3631 [yl_commons] golden apples disappear when felling trees
  • #3695 [yl_commons] mobs chicken eggs in the world
  • #3709 [yl_commons] fruit should fall as items
  • #3720 [yl_commons] make rollback hard to accidentally use
  • #3733 [yl_commons] petz fishtank usage infospec
  • #3806 [yl_commons] fix recipe for chocolate block -> bars
  • #3834 [yl_commons] add some cocoa bean (powder) recipes
  • #3836 [yl_commons] biome cows should respect protection and ownership
  • #3864 [yl_commons] fix alias for ethereal bowl
  • #3909 [yl_commons] strip translation: don't crash on malformed input
  • #3679 [yl_nether] electrumese axe - don't drop "air" nodes
  • #3653 [yl_nether] fix crafting rotated electrumese
  • #3870, #4011 [yl_nether] avoid race condition when preventing creation of areas
  • #3992 [yl_nether] electrumese hoe should plant all seeds

other:

  • #3577 fix anvils on test server (remove cottages update)
new mods/features: * [x] (ready for QA) #21 choppy * [x] (ready for QA) #3066 woodcutting tries to violate protection * [x] (ready for QA) #3174 woodcutting w/out an axe * [x] (ready for QA) #3738 woodcutting giant ferns * [x] (ready for QA) #3789 node replacer triggers woodcutting * [x] (ready for QA) #3865 choppy & unified trees * [x] (ready for QA) #777 playeranim * [x] (ready for QA) #2049 Cheese mod * [x] (ready for QA) #3453, your-land/yl_statuseffects#1 basic builders' flight * [ ] (ready for QA) #??? draw line mod by debiankaios * [ ] (ready for QA) #??? nerdpole reporting by Ravise * [ ] yl_settings your-land/administration#114 major updates needing integration: * [ ] (ready for QA) #2915 moreblocks/stairsplus * [ ] (ready for QA) #1255 ethereal:slab_crystal_block does not glow * [ ] (ready for QA) #1370 moreblocks:slope_stone digs as morebloks:slope_cobble * [ ] (ready for QA) #1518 invsaw for creative players * [ ] (ready for QA) #1731 allow placing stairlights on moreblocks stairs * [ ] (ready for QA) #1792 saws lose materials * [ ] (ready for QA) #1981 saws are confused about the cost of various things * [ ] (ready for QA) #2251 cut node recipes missing from guide * [ ] (ready for QA) #2399 no group `slab_wood_8` * [ ] (ready for QA) #3349 inconsistent microblock SFX * [ ] (ready for QA) #3488 remove microblock craft schemata * [ ] (ready for QA) #3527 microblock conversion rates are inconsistent * [ ] (ready for QA) #3662 hide/remove deprecated moreblocks tiles from before facedir * [ ] (ready for QA) #3669 no-faces trees don't work right in the saw * [ ] (ready for QA) #3820 saw-able category in unified_inventory * [ ] (ready for QA) #3823 saw loses material (not the same bug as the other similar things) * [ ] (ready for QA) #3966 crafting 2 1/16th slabs gives a single 1/8th slab, though each 1/16th slab requires 1/8th a node of material. * [x] (ready for QA) #3683 sandwiches * [x] (ready for QA) #2232 bonemeal on peanut crops * [x] (ready for QA) #3537 cucina_vegana:peanut_seed duplicates sandwiches:peanut_seed * [x] (ready for QA) #3703 attempting to override unknown item sandwiches:blackberry_jam * [x] (ready for QA) #3711 cooking peanuts is borked * [x] (ready for QA) #3791 Could not load image "sandwiches_peanut.png" * [x] (ready for QA) #3843 Recipe for Blueberry jam sandwich broken. * [x] (ready for QA) #3904 recipe for hot veggie sandwiches broke again * ~~[ ] x_bows #3684~~ bugfixes ready for QA: * [x] #2644 \[arena_lib] (minor fix) * [x] #3614 \[petz] can't place fish * [x] #3185 \[petz] fishtank - warn when trying to put wrong items into it * [x] #3232 \[petz] glitchwolf * [x] #3600 \[petz], \[mesecons_debug] HUD problems * [x] #3616 \[petz] show wrong value when healing * [ ] #3504 \[petz], \[skinsdb], \[3d_armor] fix broken emotes * [x] #3314 \[petz] thrown object improvements * [ ] #3022 \[skinsdb] missing hands * [x] #3612 \[unified_inventory] minor UI bug * [x] #3631 \[yl_commons] golden apples disappear when felling trees * [x] #3695 \[yl_commons] mobs chicken eggs in the world * [x] #3709 \[yl_commons] fruit should fall as items * [x] #3720 \[yl_commons] make rollback hard to accidentally use * [x] #3733 \[yl_commons] petz fishtank usage infospec * [x] #3806 \[yl_commons] fix recipe for chocolate block -\> bars * [x] #3834 \[yl_commons] add some cocoa bean (powder) recipes * [x] #3836 \[yl_commons] biome cows should respect protection and ownership * [x] #3864 \[yl_commons] fix alias for ethereal bowl * [x] #3909 \[yl_commons] strip translation: don't crash on malformed input * [x] #3679 \[yl_nether] electrumese axe - don't drop "air" nodes * [x] #3653 \[yl_nether] fix crafting rotated electrumese * [x] #3870, #4011 \[yl_nether] avoid race condition when preventing creation of areas * [x] #3992 \[yl_nether] electrumese hoe should plant all seeds other: * [x] #3577 fix anvils on test server (remove cottages update)

Update x_bows

Yes, shooting with bows feels like under powered, I used it to attack balrog (to distract mostly)

yl_commons feature: Builders Flight

This is a must. You don't know how many ladders I had to use

>Update x_bows Yes, shooting with bows feels like under powered, I used it to attack balrog (to distract mostly) >yl_commons feature: Builders Flight This is a must. You don't know how many ladders I had to use
Member

i'd also like to do admin issue #150: cleanup all the yl_* mods. cleaning up the dependency ordering will help out maintenance in the long term, and i'm certain that there's a lot of minor bugs waiting to be discovered.

i'd also like to do [admin issue #150: cleanup all the yl_* mods](https://gitea.your-land.de/your-land/administration/issues/150). cleaning up the dependency ordering will help out maintenance in the long term, and i'm certain that there's a lot of minor bugs waiting to be discovered.
Member

Update x_bows

oh wow, it looks like we've divered quite a lot from upstream. what features does it have that we want?

> Update x_bows oh wow, it looks like we've divered quite a lot from upstream. what features does it have that we want?
Member

diff

function XBowsEntityDef.on_activate(self, selfObj, staticdata, dtime_s)
    if not selfObj or not staticdata or staticdata == '' then
        selfObj.object:remove()
        return
    end
    ...
end

oof, i don't like the look of that (distinct self and selfObj) :\

[diff](https://bitbucket.org/minetest_gamers/x_bows/branches/compare/7067a6c1cad8a9b71c027adbb5834242a0e09d2c%0Dd57d5b0cf39f9e9843d5bfe31e451f0cc1babf73#diff) ```lua function XBowsEntityDef.on_activate(self, selfObj, staticdata, dtime_s) if not selfObj or not staticdata or staticdata == '' then selfObj.object:remove() return end ... end ``` oof, i don't like the look of that (distinct `self` and `selfObj`) :\
AliasAlreadyTaken added the
1. kind/other
label 2023-01-02 01:20:02 +00:00
Member

i'd be happy to implement a version of builders' flight that's just a placeholder until we can do it properly, when the right APIs (e.g status effects) have been created. there's a number of builds i've got on pause until builders
flight exists. i wanted to wait until APIs existed so i could create builders' flight "the right way" from the start, but those APIs are still many months down my pipeline. creating an approximation doesn't prevent us from refining it later, and i'd be fine creating it as a stand-alone feature w/ simple, limited mechanics.

i'd be happy to implement a version of builders' flight that's just a placeholder until we can do it properly, when the right APIs (e.g status effects) have been created. there's a number of builds i've got on pause until builders flight exists. i wanted to wait until APIs existed so i could create builders' flight "the right way" from the start, but those APIs are still many months down my pipeline. creating an approximation doesn't prevent us from refining it later, and i'd be fine creating it as a stand-alone feature w/ simple, limited mechanics.

Any plans for TNT?

Any plans for TNT?
Member

Any plans for TNT?

tnt is currently dependent on privilege; i think we ought to add tnt to "basic privs", so that staff (and bailiffs?) can grant and revoke it as necessary. it shouldn't be enabled by default. even if it can't destroy protected areas anymore, tnt is still a potential menace.

> Any plans for TNT? tnt is currently dependent on privilege; i think we ought to add tnt to "basic privs", so that staff (and bailiffs?) can grant and revoke it as necessary. it shouldn't be enabled by default. even if it can't destroy protected areas anymore, tnt is still a potential menace.
flux added the
2. prio/elevated
label 2023-01-04 04:00:18 +00:00
flux added this to the flux's TODO list project 2023-01-04 04:00:21 +00:00
Member

Any plans for TNT?

created an issue for discussing this: #3685

> Any plans for TNT? created an issue for discussing this: #3685
Member

i propose to put off updating x_bows until a future release of your-land and/or x_bows. i don't think it'll be easy to get it ready anytime soon. it's become quite complicated to modify.

i propose to put off updating x_bows until a future release of your-land and/or x_bows. i don't think it'll be easy to get it ready anytime soon. it's become quite complicated to modify.
flux added this to the 1.1.117.1 milestone 2023-01-31 21:19:32 +00:00
flux added the
4. step/at work
label 2023-02-02 03:40:19 +00:00
Member

i propose that we feature-freeze 1.1.118 by 2023-02-04 00:00:00Z (between friday night and saturday morning, UTC), do testing over the weekend (until 2023-02-06 00:00:00Z), and put off anything that doesn't make it until the next release.

because it'd be tricky to cherry-pick them, QA for updates to yl_commons and petz should be prioritized, because there's a ton of them.

anything that isn't signed off on by the end of the QA period should be put off until the next release. because cherry-picking is tricky, if we need to put off petz or yl_commons updates, subsequent updates to those mods will also have to wait.

outside of yl_settings, i think pretty much everything is ready for QA, or 99% there. @AliasAlreadyTaken if you ok it, i can try to work on yl_settings now, and i promise to keep it to your style as much as i can understand it.

i propose that we feature-freeze 1.1.118 by 2023-02-04 00:00:00Z (between friday night and saturday morning, UTC), do testing over the weekend (until 2023-02-06 00:00:00Z), and put off anything that doesn't make it until the next release. because it'd be tricky to cherry-pick them, QA for updates to yl_commons and petz should be prioritized, because there's a *ton* of them. anything that isn't signed off on by the end of the QA period should be put off until the next release. because cherry-picking is tricky, if we need to put off petz or yl_commons updates, subsequent updates to those mods will also have to wait. outside of yl_settings, i think pretty much everything is ready for QA, or 99% there. @AliasAlreadyTaken if you ok it, i can try to work on yl_settings now, and i promise to keep it to your style as much as i can understand it.
AliasAlreadyTaken modified the milestone from 1.1.117.1 to 1.1.118 2023-02-02 10:37:22 +00:00
Author
Owner

Fixing the armour duplication bug #3668 demands haste, we'll release 1 1.1.117.1 hotfix and then go about 1.1.118 in peace.

Here's #3700 to discuss 1.1.117.1

Most of the 1.1.118 things are not where we want them and as suggested we should hold off on merging x_bows until we got a good look at it.

Fixing the armour duplication bug #3668 demands haste, we'll release 1 1.1.117.1 hotfix and then go about 1.1.118 in peace. Here's #3700 to discuss 1.1.117.1 Most of the 1.1.118 things are not where we want them and as suggested we should hold off on merging x_bows until we got a good look at it.
Member

alright, i'll move the most urgent things to 1.1.117.1

alright, i'll move the most urgent things to 1.1.117.1
Member

i've added a bunch of issues which will be resolved w/ my moreblocks/stairsplus fork to the 1.1.118 milestone

i've added a bunch of issues which will be resolved w/ my moreblocks/stairsplus fork to the 1.1.118 milestone
Member

i've added a bunch of issues which will be resolved w/ choppy to the 1.1.118 milestone

i've added a bunch of issues which will be resolved w/ choppy to the 1.1.118 milestone
Member

added a number of issues that will be resolved by the sandwiches update

added a number of issues that will be resolved by the sandwiches update
Member

i propose that we put off yl_settings until a later update; i think most of the other things are ready to go w/ some testing, yl_settings is high-priority, but still needs development, and i don't know when alias will find the time to do that.

i propose that we put off yl_settings until a later update; i think most of the other things are ready to go w/ some testing, yl_settings is high-priority, but still needs development, and i don't know when alias will find the time to do that.
Member

added a number of loose yl_commons updates, which had commits between other things which were formally on the 1.1.118 milestone.

added a number of loose yl_commons updates, which had commits between other things which were formally on the 1.1.118 milestone.
Author
Owner

I added the cheese mod and the playeranim mod to yourland-mods

They do not reside with the mt-mirror account, but with a new organization https://gitea.your-land.de/org/your-land-mirror/dashboard so that other can have access, too.

I added the cheese mod and the playeranim mod to yourland-mods They do not reside with the mt-mirror account, but with a new organization https://gitea.your-land.de/org/your-land-mirror/dashboard so that other can have access, too.
Member

playeranim doesn't seem to work well w/ the 5.7-beta client:

image

cf.

image

playeranim doesn't seem to work well w/ the 5.7-beta client: ![image](/attachments/3d7f5a2b-0683-4b19-b143-e8c062ece89b) cf. ![image](/attachments/f32fb9d6-0af3-4806-9a2f-07c33773596e)
Author
Owner

Rebuild your client please, seems like there was a brief moment in either MT master or irrlicht master where it looked like this.

I had the same, but after I pulled latest of both and built them, it looked normal again.

That picture ... maybe we should make it into a mob :D

Edit: Broken bone issue might be resolved here: a67f3003de

Rebuild your client please, seems like there was a brief moment in either MT master or irrlicht master where it looked like this. I had the same, but after I pulled latest of both and built them, it looked normal again. That picture ... maybe we should make it into a mob :D Edit: Broken bone issue might be resolved here: https://github.com/minetest/irrlicht/commit/a67f3003de693998ab3ec9864383d7155175c353
Author
Owner
  • Add to world.mt:
load_mod_cheese = true
load_mod_playeranim = true
  • mail mod migration takes around 3 minutes after first server start
- Add to world.mt: ``` load_mod_cheese = true load_mod_playeranim = true ``` - mail mod migration takes around 3 minutes after first server start
Author
Owner

It's been more than three month since the last update and some stuff has queued up. Let's freeze, test and release before MT engine releases 5.7.0, else we'll have to test both at the same time or postpone 5.7.0 until 1.1.118 was on the main server for a while. Especially since the postgresql upgrade from 14.5 to 15.2 will also take a while and I don't want more than one change at the same time, I'd like to start testing for 118 rather sooner than later.

Additionally:

  • Publish future plans for item buffs/debuffs: Debuff for crystal boots, adjustments for builders flight, debuff for invis potion.
  • decide on fate of moreblocks. con: core mechanic, dependencies, license, no way back VS pro: fluxmod, frees nodecount, demo for downstream
  • Rough timeline for YL 118, MT 570 and postgres 15. If 5.7.0 gets release before 15th: Let's try to have 118 out by 20th April, then test for MT 5.7.0 until 30th April, then upgrade database afterwards. Else let's upgrade postgres first.
It's been more than three month since the last update and some stuff has queued up. Let's freeze, test and release before MT engine releases 5.7.0, else we'll have to test both at the same time or postpone 5.7.0 until 1.1.118 was on the main server for a while. Especially since the postgresql upgrade from 14.5 to 15.2 will also take a while and I don't want more than one change at the same time, I'd like to start testing for 118 rather sooner than later. Additionally: - Publish future plans for item buffs/debuffs: Debuff for crystal boots, adjustments for builders flight, debuff for invis potion. - decide on fate of moreblocks. con: core mechanic, dependencies, license, no way back VS pro: fluxmod, frees nodecount, demo for downstream - Rough timeline for YL 118, MT 570 and postgres 15. If 5.7.0 gets release before 15th: Let's try to have 118 out by 20th April, then test for MT 5.7.0 until 30th April, then upgrade database afterwards. Else let's upgrade postgres first.

I would say

  1. YL 1.1.118, updating on known versions makes more sense
  2. postgresql 15.2, better update with a longtime known minetest version
  3. minetest 5.7.x, expecting 5.7.0 to be released soon but based on previous releases it will be followed by a .1 version "shortly" after.
I would say 1. YL 1.1.118, updating on known versions makes more sense 2. postgresql 15.2, better update with a longtime known minetest version 3. minetest 5.7.x, expecting 5.7.0 to be released soon but based on previous releases it will be followed by a .1 version "shortly" after.
Author
Owner

Now that they released 5.7.0, let's tie together what we have for 1.1.118 and start testing, else delivery will take more than another month.

This means we'll once again move moreblocks and yl_settings to the next milestone.

The draw line mod doesn't have a use yet, also they made an engine funtion to achieve something similar.

The pillar mod should go to the testserver asap, maybe it needs to be integrated to yl_commons though.

We'll see whether we can integrate watchtower. I'll pull stuff from upstream as quickly as possible, then we can start QA.

Now that they released 5.7.0, let's tie together what we have for 1.1.118 and start testing, else delivery will take more than another month. This means we'll once again move moreblocks and yl_settings to the next milestone. The draw line mod doesn't have a use yet, also they made an engine funtion to achieve something similar. The pillar mod should go to the testserver asap, maybe it needs to be integrated to yl_commons though. We'll see whether we can integrate watchtower. I'll pull stuff from upstream as quickly as possible, then we can start QA.
Member

This means we'll once again move moreblocks and yl_settings to the next milestone.

what outstanding issues are there w/ moreblocks?

> This means we'll once again move moreblocks and yl_settings to the next milestone. what outstanding issues are there w/ moreblocks?
Author
Owner

Add

smartshop.storage_max_distance = 256

to minetest conf due to #4156

Add ``` smartshop.storage_max_distance = 256 ``` to minetest conf due to #4156
Author
Owner

This means we'll once again move moreblocks and yl_settings to the next milestone.

what outstanding issues are there w/ moreblocks?

The same like with smartshops: We can't go back once it's on the server. It's a core mechanic we can't simply "disable" like a food mod. Also your-land/administration#173

> > This means we'll once again move moreblocks and yl_settings to the next milestone. > > what outstanding issues are there w/ moreblocks? The same like with smartshops: We can't go back once it's on the server. It's a core mechanic we can't simply "disable" like a food mod. Also https://gitea.your-land.de/your-land/administration/issues/173
Author
Owner

I completed pulling all the upstream mods and merging them into yl_stable. Some mods have issues or at least things we need to know/ consider:

  • worldeditAdditions: known issue #3583
  • chesttools: pre 118 commit d1093fe448 : People really don't liek the new colours and are confused by the wallmounted type
  • cottages: We need to know about other cottages settings. See below
  • ingots: We did major rework, but now upstream updates
  • nether: brings new mapgen items. -> yl_testing
  • mobs_redo : back to upstream, but your-land/administration#144 (comment)
  • petz : yl_testing
  • pie: new setting quarters instead of slices. Do we want that?
  • replacer: outstanding decision your-land/administration#143 -> 1.1.119
  • unified_inventory_plus: AGPL dep since 40bc9b1666 OK since nonessential
  • x_bows: We did major rework, but now upstream updates

Add to minetest.conf

cottages_feldweg_mode = mesh_incl_45

I also simply pulled all the worldmods and restarted. Let's test :D

I completed pulling all the upstream mods and merging them into yl_stable. Some mods have issues or at least things we need to know/ consider: * worldeditAdditions: known issue #3583 * chesttools: pre 118 commit d1093fe448 : People really don't liek the new colours and are confused by the wallmounted type * cottages: We need to know about other cottages settings. See below * ingots: We did major rework, but now upstream updates * nether: brings new mapgen items. -> yl_testing * mobs_redo : back to upstream, but https://gitea.your-land.de/your-land/administration/issues/144#issuecomment-43559 * petz : yl_testing * pie: new setting quarters instead of slices. Do we want that? * replacer: outstanding decision https://gitea.your-land.de/your-land/administration/issues/143 -> 1.1.119 * unified_inventory_plus: AGPL dep since 40bc9b1666 OK since nonessential * x_bows: We did major rework, but now upstream updates Add to minetest.conf ``` cottages_feldweg_mode = mesh_incl_45 ``` I also simply pulled all the worldmods and restarted. Let's test :D
Author
Owner

Both trashcan #4077 and watchtower https://gitea.your-land.de/Ravise/watchtower may still take a bit of testing and development. If either isn't ready for 1.1.118, it'll go to 1.1.119

Both trashcan #4077 and watchtower https://gitea.your-land.de/Ravise/watchtower may still take a bit of testing and development. If either isn't ready for 1.1.118, it'll go to 1.1.119
Author
Owner

restore old tutorial shapeless recipe following fix #4034

restore old tutorial shapeless recipe following fix #4034
Author
Owner

Add to minetest.conf

mesecon.luacontroller_print_behavior = noop

https://github.com/minetest-mods/mesecons/blob/master/settingtypes.txt#L33

Add to minetest.conf ``` mesecon.luacontroller_print_behavior = noop ``` https://github.com/minetest-mods/mesecons/blob/master/settingtypes.txt#L33
Author
Owner

During QA:

The following mods are on those branches on the testserver. When good, those branches need to go to yl_stable

nether : yl_testing
yl_bailiff: yl_testing
mail_mod : 1.1.x
yl_unified_trash: yl_testing
yl_statuseffects: builders_flight

During QA: The following mods are on those branches on the testserver. When good, those branches need to go to yl_stable nether : yl_testing yl_bailiff: yl_testing mail_mod : 1.1.x yl_unified_trash: yl_testing yl_statuseffects: builders_flight
Author
Owner

Add to minetest.conf

[yl_unified_trashcan]

yl_unified_trash.review_width = 4
yl_unified_trash.review_height = 1
Add to minetest.conf ``` [yl_unified_trashcan] yl_unified_trash.review_width = 4 yl_unified_trash.review_height = 1 ```
Author
Owner

We'll once again postpone the new nether. New nether will remain in yl_testing

yl_settings, moreblocks and bailiff commands will be postponed

draw lines was not tested

watchtower needs a bit more love or be integrated

cucina_vegana has a bug https://github.com/acmgit/cucina_vegana/issues/25 was reset to 7cf3ac73ee

smartshops has a bug #4257, so we had to reset to 0997e9f

chesttools is not yet ready for more colours, we had to reset to 470774008a106e52a2a09171f9a7e79c215d8ec7

Everything happens in the yl_stable branch now, except NPCs. yl_speak_up is still on branch trade_list and needs to be switched back to y_stable in the next update

We'll once again postpone the new nether. New nether will remain in yl_testing yl_settings, moreblocks and bailiff commands will be postponed draw lines was not tested watchtower needs a bit more love or be integrated cucina_vegana has a bug https://github.com/acmgit/cucina_vegana/issues/25 was reset to 7cf3ac73ee smartshops has a bug #4257, so we had to reset to 0997e9f chesttools is not yet ready for more colours, we had to reset to 470774008a106e52a2a09171f9a7e79c215d8ec7 Everything happens in the yl_stable branch now, except NPCs. yl_speak_up is still on branch trade_list and needs to be switched back to y_stable in the next update
Author
Owner

Add to world.mt:

load_mod_yl_unified_trash = true
load_mod_choppy = true

Change in world.mt:

load_mod_woodcutting = false
Add to world.mt: ``` load_mod_yl_unified_trash = true load_mod_choppy = true ``` Change in world.mt: ``` load_mod_woodcutting = false ```
Author
Owner

Update failed due to #4259

We went back to 1.1.117.1

The issue is reproducible on the testserver

Update failed due to https://gitea.your-land.de/your-land/bugtracker/issues/4259 We went back to 1.1.117.1 The issue is reproducible on the testserver
Author
Owner

A couple of hasty changes to yl_livemapping (read: removal of the 33 MB file) the update worked. It did spawn a couple of issues, but they will be addressed in 1.1.119.

Following Milestone 1.1.119 issue: #4181

A couple of hasty changes to yl_livemapping (read: removal of the 33 MB file) the update worked. It did spawn a couple of issues, but they will be addressed in 1.1.119. Following Milestone 1.1.119 issue: #4181
flux removed this from the flux's TODO list project 2023-12-22 20:43:49 +00:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: your-land/bugtracker#3401
No description provided.