use my moreblocks fork #2915

Open
opened 2022-10-25 00:57:16 +00:00 by flux · 10 comments
Member

because minetest-mods refuses to accept my PR nor discuss what i'd need to do to get it accepted, i've done a hard fork.

https://github.com/fluxionary/minetest-moreblocks

this is an update that will allow for us to hopefully reduce the # of used node IDs immensely.

because minetest-mods refuses to accept my PR nor discuss what i'd need to do to get it accepted, i've done a hard fork. https://github.com/fluxionary/minetest-moreblocks this is an update that will allow for us to hopefully reduce the # of used node IDs immensely.
flux added the
1. kind/enhancement
1. kind/other
4. step/discussion
labels 2022-10-25 00:57:16 +00:00
flux changed title from use my moreblocks PR in order to gain more confidence in the update to use my moreblocks fork 2023-02-02 03:56:29 +00:00
flux added
4. step/ready to QA test
and removed
4. step/discussion
labels 2023-02-02 03:56:53 +00:00

Let's put it on the testserver again. What do we have to do? Simply clone or put some settings?

Let's put it on the testserver again. What do we have to do? Simply clone or put some settings?
Author
Member

Let's put it on the testserver again. What do we have to do? Simply clone or put some settings?

probably the most relevant setting is

stairsplus.in_creative_inventory = false

which changed its name slightly.

we may also want to set

stairsplus.crafting_schemata_enabled = false

which will disable all the craft recipes that people find so obnoxious.

> Let's put it on the testserver again. What do we have to do? Simply clone or put some settings? probably the most relevant setting is ``` stairsplus.in_creative_inventory = false ``` which changed its name slightly. we may also want to set ``` stairsplus.crafting_schemata_enabled = false ``` which will disable all the craft recipes that people find so obnoxious.
flux added this to the 1.1.118 milestone 2023-02-20 01:41:29 +00:00
AliasAlreadyTaken modified the milestone from 1.1.118 to 1.1.119 2023-04-14 05:46:17 +00:00
AliasAlreadyTaken modified the milestone from 1.1.119 to 1.1.120 2023-05-09 11:04:27 +00:00

To get this thing on the road:

  • Add modification date to database scheme
  • WE integration and import of old saved stuff (mts and we)

What else?

To get this thing on the road: * [ ] Add modification date to database scheme * [ ] WE integration and import of old saved stuff (mts and we) What else?
flux added this to the flux's TODO list project 2023-05-11 03:39:40 +00:00
Author
Member

To get this thing on the road:

  • Add modification date to database scheme
  • WE integration and import of old saved stuff (mts and we)

What else?

making a note to make this a high-priority issue.

i assume the first issue is part of your backup procedure, and not something i can help with directly? and the second is creating an automated translation system for schemas to allow importing things w/ aliased node IDs?

> To get this thing on the road: > > * [ ] Add modification date to database scheme > * [ ] WE integration and import of old saved stuff (mts and we) > > What else? making a note to make this a high-priority issue. i assume the first issue is part of your backup procedure, and not something i can help with directly? and the second is creating an automated translation system for schemas to allow importing things w/ aliased node IDs?
flux added the
2. prio/elevated
label 2023-05-11 04:01:22 +00:00
flux added
4. step/at work
and removed
4. step/ready to QA test
labels 2023-05-15 23:32:59 +00:00

This is now on the testserver

This is now on the testserver
Author
Member

whitelist of stairsplus nodes is attached.

whitelist of stairsplus nodes is attached.
AliasAlreadyTaken removed this from the 1.1.120 milestone 2023-08-28 10:37:29 +00:00
flux added a new dependency 2023-11-16 21:14:24 +00:00
Author
Member

note: we don't have to have an a priori list list of whitelisted nodes to make this work. we can install it first and create the whitelist at any point after. my fork has a ton of bugfixes that aren't related to reducing the number of extraneous nodes.

note: we don't have to have an a priori list list of whitelisted nodes to make this work. we can install it first and create the whitelist at any point after. my fork has a ton of bugfixes that aren't related to reducing the number of extraneous nodes.

Let's gather what needs to be done to adopt the fork

  • Database needs to have a modification_date: your-land/bugtracker#4526
  • Deal with Worldedit saves, old backups and anything that might break between versions
  • Upgrade all database blocks to latest version, so we can traverse them with a script
  • Split the fork into smaller parts so that upstream has a chance to review them
  • Tell Alias to stop being a coward! :D

Anything else?

And on top of that: Extensive testing

Let's gather what needs to be done to adopt the fork * [ ] Database needs to have a modification_date: your-land/bugtracker#4526 * [ ] Deal with Worldedit saves, old backups and anything that might break between versions * [ ] Upgrade all database blocks to latest version, so we can traverse them with a script * [ ] Split the fork into smaller parts so that upstream has a chance to review them * [ ] Tell Alias to stop being a coward! :D Anything else? And on top of that: Extensive testing
Author
Member

Split the fork into smaller parts so that upstream has a chance to review them

that's probably not happening and shouldn't block this issue.

> Split the fork into smaller parts so that upstream has a chance to review them that's probably not happening and shouldn't block this issue.
Author
Member

Deal with Worldedit saves, old backups and anything that might break between versions

i converted all the worldedit files at some point in the past (maybe 8 months ago?), though there might be new ones. also i'm not sure where i put that.

> Deal with Worldedit saves, old backups and anything that might break between versions i converted all the worldedit files at some point in the past (maybe 8 months ago?), though there might be new ones. also i'm not sure where i put that.
AliasAlreadyTaken added this to the moreblocks milestone 2024-03-17 12:19:54 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

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