1.1.124 #6471

New Issue

Open

opened 2024-03-14 05:47:46 +00:00 by AliasAlreadyTaken · 9 comments

AliasAlreadyTaken commented

2024-03-14 05:47:46 +00:00

Owner

Copy Link

We'll try to do the stuff we didn't do in 1.1.123, most notably:

NPC update
itemframes bugfix

We'll try to do the stuff we didn't do in 1.1.123, most notably: * [x] NPC update * [x] itemframes bugfix

AliasAlreadyTaken added this to the 1.1.124 milestone 2024-03-14 05:47:46 +00:00

AliasAlreadyTaken added the

1. kind/other

label 2024-03-14 05:47:57 +00:00

Jammy commented

2024-03-14 13:38:39 +00:00

Copy Link

In this update the spear should be made stronger(remove attack cooldown?).

Jammy commented

2024-03-14 13:39:38 +00:00

Copy Link

Also, as whosit said, I think we should port spears to Flux's mod and add rainbow/mithril spears in passing.

Jammy commented

2024-03-14 13:42:02 +00:00

Copy Link

Should we switch ingots back to upstream? They have a 64-ingot stack which we don't have yet.

👎 1

whosit commented

2024-03-14 14:01:15 +00:00

Member

Copy Link

Should we switch ingots back to upstream? They have a 64-ingot stack which we don't have yet.

AFAIK this is intentional to save node IDs?
see issue #2281

> Should we switch ingots back to upstream? They have a 64-ingot stack which we don't have yet. AFAIK this is intentional to save node IDs? see issue #2281

AliasAlreadyTaken commented

2024-03-14 14:29:20 +00:00

Author

Owner

Copy Link

@Jammy This is a discussion issue for what's in the update. If you have feature requests or bugs, please open a new issue. If we find it suitable for this update, we'll add it.

flux commented

2024-03-14 22:25:28 +00:00

Member

Copy Link

asking again, any chance we can get my moreblocks/stairsplus fork going? it's in use on other servers and seems stable. #2915

👍 1

AliasAlreadyTaken referenced this issue

2024-03-29 05:55:04 +00:00

1.1.123.2 #6481

AliasAlreadyTaken pinned this 2024-03-29 05:56:07 +00:00

flux commented

2024-03-30 19:51:32 +00:00

Member

Copy Link

going through my lists, my inventory_ores mod mentioned in #2789 would be nice to have. it is low complexity and has a low chance of causing problems.

flux commented

2024-03-30 19:57:52 +00:00

Member

Copy Link

also poke about itemplate #2067

AliasAlreadyTaken added this to the Alias@work project 2024-04-12 20:44:30 +00:00

AliasAlreadyTaken commented

2024-04-18 23:17:06 +00:00

Author

Owner

Copy Link

Signposts removed a colorizer. Check signposts for readability
Add ethereal.sapling_protection_check = true to minetest.conf
Wasn't there some drama around strawberries? Check those
Mail mod migration
Changes in choppy. Check if our changes in xp_redo still work
Employ a vampire to test the node count command in debuggery
Check Oerrkii Model
Add water_life_nospawn = true to minetest.conf
Enable npc_talk_edit in world.mt

* [x] Signposts removed a colorizer. Check signposts for readability * [x] Add `ethereal.sapling_protection_check = true` to minetest.conf * [x] Wasn't there some drama around strawberries? Check those * [x] Mail mod migration * [x] Changes in choppy. Check if our changes in xp_redo still work * [x] Employ a vampire to test the node count command in debuggery * [x] Check Oerrkii Model * [x] Add `water_life_nospawn = true` to minetest.conf * [x] Enable npc_talk_edit in world.mt

AliasAlreadyTaken referenced this issue

2024-04-20 05:16:28 +00:00

1.1.123 #5693

AliasAlreadyTaken self-assigned this 2024-04-26 23:35:16 +00:00

No Branch/Tag Specified

Branches Tags

Labels

Clear labels

1. kind/balancing

Depends on balancing

1. kind/breaking

something that alters or disables an existing game mechanic

1. kind/bug

Something is not working

1. kind/construction

A build needs fixing

1. kind/documentation

Needs proper documentation

1. kind/enhancement

New feature

1. kind/griefing

players despoiling builds or nature

1. kind/invalid

Not a valid report, e.g. created by mistake with no content.

1. kind/meme

issue is mostly a joke

1. kind/node limit

something which works for or against the node limit

1. kind/other

Something not within the other kinds

1. kind/protocol

something concerning how staff should react to player requests, or how players should treat each other

2. prio/controversial

not likely to happen w/out a lot of discussion

2. prio/critical

Very important

2. prio/elevated

something players are eager to have fixed

2. prio/good first issue

the resolution to this is could be done by a new minetest contributor, who doesn't yet understand the mod ecosystem

2. prio/interesting

one of us has real interest in getting this implemented or fixed. however, more research might be needed.

2. prio/low

Not so important

3. source/art

art needs to be created or found for this to exist. includes sound, 3d modelling, and in-game building.

3. source/client

Issue is with the minetest client, or with player client configuration or the technical details of their setup

3. source/engine

Issue is due to a bug or feature of the minetest engine

3. source/ingame

Problem and solution exist in-game, e.g. builds or player moderation

3. source/integration

Two or more nonbuggy mechanics conflict, or our attempts to rectify conflicting mechanics have created a new bug

3. source/lag

A problem which is caused or made worse by lag, due to server processing issues, client processing issues, or network issues

3. source/license

A licensing problem is involved

3. source/mod upstream

Problem is upstream (not engine/client)

Alias has approved this feature, someone should implement it

4. step/at work

Being worked on

4. step/blocked

we plan to do this, but other work has to be finished first

4. step/discussion

issue is under discussion, a solution has not been dictated or agreed upon

4. step/help wanted

Need some help

4. step/needs confirmation

4. step/partially fixed

this is mitigated or partially solved, but more work needs to be done

4. step/question

More information is needed

4. step/ready to deploy

has been QA tested by another person. has no outstanding issues. might be installed on prod, but needs final testing

4. step/ready to QA test

the code is supposedly fixed, but needs to be tested.

4. step/want approval

Someone can quickly implement this if Alias approves the change/feature

5. result/cannot reproduce

5. result/duplicate

This issue or pull request already exists

5. result/fixed

problem is fixed

5. result/maybe

not planned currently, but maybe some day

5. result/wontfix

the reported issue won't be changed, whether it's intentional or not.

ugh/petz

yet another petz bugz.

ugh/QA main

That's something we can only wait and see whether it hapens again: On the main server

ugh/QA NOK

Fix didn't yield the expected results

No Label

1. kind/documentation

2. prio/controversial

2. prio/critical

2. prio/elevated

2. prio/good first issue

3. source/integration

3. source/lag

3. source/license

3. source/mod upstream

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

Milestone

Clear milestone

No items

No Milestone

1.1.124

Projects

Clear projects

No project

Alias@work

Assignees

Clear assignees

No Assignees

AliasAlreadyTaken

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#6471

Reference in New Issue

Repository

your-land/bugtracker

Title

Body

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?