1.1.118 #3401
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#3401
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?
new mods/features:
major updates needing integration:
slab_wood_8
x_bows #3684bugfixes ready for QA:
other:
Yes, shooting with bows feels like under powered, I used it to attack balrog (to distract mostly)
This is a must. You don't know how many ladders I had to use
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.
oh wow, it looks like we've divered quite a lot from upstream. what features does it have that we want?
diff
oof, i don't like the look of that (distinct
self
andselfObj
) :\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?
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.
created an issue for discussing this: #3685
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 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.
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.
alright, i'll move the most urgent things to 1.1.117.1
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/ choppy to the 1.1.118 milestone
added a number of issues that will be resolved by the sandwiches update
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.
added a number of loose yl_commons updates, which had commits between other things which were formally on the 1.1.118 milestone.
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.
playeranim doesn't seem to work well w/ the 5.7-beta client:
cf.
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
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:
I would say
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.
what outstanding issues are there w/ moreblocks?
Add
to minetest conf due to #4156
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
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:
Add to minetest.conf
I also simply pulled all the worldmods and restarted. Let's test :D
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
restore old tutorial shapeless recipe following fix #4034
Add to minetest.conf
https://github.com/minetest-mods/mesecons/blob/master/settingtypes.txt#L33
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
Add to minetest.conf
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
Add to world.mt:
Change in world.mt:
Update failed due to #4259
We went back to 1.1.117.1
The issue is reproducible on the testserver
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