Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Aliases for Pipes #1311

Closed
Holocus opened this issue Feb 10, 2023 · 3 comments
Closed

Aliases for Pipes #1311

Holocus opened this issue Feb 10, 2023 · 3 comments
Labels
status:invalid This does not describe a request or bug with CraftBook type:feature-request Request for something new

Comments

@Holocus
Copy link

Holocus commented Feb 10, 2023

The Problem

I'm really fond of the Pipe function but it's getting increasingly difficult to make neat due to the limited size of filters being able to fit on a signpost.
It would be absolutely amazing if it was possible to make a simple list file in the plugin folder with aliases for items.
For example
Alias.txt
[Woodslabs]
126,126:1,126:2,126:3,126:4,126,5,minecraft:petrified_oak_slab
[Saplings]
6,6:1,6:2,6:3,6:4,6:5

etc etc
and then on the pipesign just use:
[Pipe]
#Woodslabs
to filter all the items listed under [Woodslabs] in the file.
with this we could streamline the piping and make it neater and compact!

A Solution

Have the option to make a text file in the pluginfolder and add our own list of aliases for the pipe function to also look for when doing it's filtering logic on the content for example:
Alias.txt
[Woodslabs]
126,126:1,126:2,126:3,126:4,126,5,minecraft:petrified_oak_slab
[Saplings]
6,6:1,6:2,6:3,6:4,6:5

Alternatives

Right now it's limited to how much text can be fitted onto a sign how many items could be filtered into a chest. with a doublechest and two pistons it can fit double the amount, but with the newer items not having ID's but long names like minecraft_petrified_oak_slab won't even be able to fit a signpost at all.

Anything Else?

No response

@Holocus Holocus added status:pending Pending acceptance or closure. type:feature-request Request for something new labels Feb 10, 2023
@me4502
Copy link
Member

me4502 commented Feb 11, 2023

You can already use variables to create aliases for anything anywhere

@me4502 me4502 added status:invalid This does not describe a request or bug with CraftBook and removed status:pending Pending acceptance or closure. labels Feb 11, 2023
@me4502 me4502 closed this as not planned Won't fix, can't repro, duplicate, stale Feb 11, 2023
@Holocus
Copy link
Author

Holocus commented Feb 11, 2023

I'm sorry what? and if so, how would I do that for the purpose I'm looking for?

@me4502
Copy link
Member

me4502 commented Feb 11, 2023

It's covered on the docs. Use the discord for support

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:invalid This does not describe a request or bug with CraftBook type:feature-request Request for something new
Projects
None yet
Development

No branches or pull requests

2 participants