#WyrmOS - Lectern Network Crafting Manager

2393 messages · Page 3 of 3 (latest)

young nacelle
#

Hmmm... Can you use an interact turret on an Owl? They chunkload, by the way.

#

Create pulls delayed-computation tricks instead.

fluid wigeon
#

Player name on a paper, whatever items I want to ship, hit send to player. I don't know actually about owls

#

Could do the warps thing as well, beam it into your chunks and let it pick up

young nacelle
#

They take letters or packages. Packages have 8 slots? maybe 6.

#

I don't think you can name them with spells to set the address because it's a special UI.

fluid wigeon
#

Actually don't know what happens if I beam a toss spell into an unloaded chunk, does it stay there until loaded?

#

Aww. Have to stick with spell mail then

#

Could have a hub at spawn with ender chests (non vanilla kind) I suppose

#

Beam to your PO box instead, to make sure the arrival is loaded

#

Hermit mail was nice. But spellmail....

#

For a server mail system though, that would probably be best with most of that infrastructure at spawn chunks

#

Which the same system could be built there easily. Mail arrives at the receiving station, in the form of a shulker with named paper and items. Box gets placed, name paper powers a display case, pops a prism into place for a few seconds, shulker gets popped and sent via toss to the destination chest

#

Prism pops back in, unlocks the system and allows the next shulker in the queue to process

#

Before we had lecterns, I used a blink rune to send items to my home storage. If it wasn't loaded, it was fine, because the item entities still got teleported. And then when the area loaded again, a pickup rune where they landed vacuumed up all the items to be sorted

#

I should test what happens with toss spells into unloaded chunks

fluid wigeon
#

For generalized WyrmOS, probably enough to say a mail system would basically just be a setup to route toss spells through the correct prism based on a named paper. Whether that ends up going through warp portals, sensitive pickup runes, or mailboxes isn't as important

#

Could set a return line subnet up on all processors, instead of directly returning to primary storage, go to a return network that defaults to primary if no other input is called. Or if a mailbox paper is included in the item input, it sends it to that destination

#

But probably better to simply have mail be it's own command instead of linking into every processor return

fluid wigeon
#

Quick and dirty spirit altar addition to wyrmOS:

Middle of the screen lectern is linked to the altar and pedestals. In that order so the first item tries the altar first.

To the right of that lectern is the indigo item line with a display case watching cyan commands for "Spirit Altar". Turret pulls everything from Items when given the command.

Above the center lectern is a debug turret with display case "Clear Spirit Altar" turret sends the toss amp 5 spell up through the prism to the top lectern.

Top lectern is on purple Primary and has an allay in a jar to catch spirit altar output and send to storage

#

Bottom left display case is looking for the count of the air spaces in the altar+pedestals. Specifically 13 seems the magic number. 8 spirits, 4 pedestals, one altar =13. If there's less than 13, it turns on, dropper hopper circuit stores that value as an item I can look for later on for a debug network

#

Currently unwired to anything. Gotta decide the specifics of that

#

But workflow is basically:

Get all the items I need for the craft, place them all on the item tab, first non spirit item needs to be the altar item.

Go to command tab and hit Spirit Altar

#

If I do exact counts, then that's it. If I just send random numbers because I don't feel like counting, then I can hit Clear

fluid wigeon
#

Been thinking. Which is dangerous.

I could further abstract the controller from the subsystems. Most of the subsystems seem to only have 2 or 3 commands of interest. At the moment I just have each one as its own item to look for. "Start Apparatus" "Start Apparatus Batch" "Clear Apparatus" "Start Smelt" "Start spirit Altar" "Clear Spirit Altar"

#

And the thing is... It makes it hard to read in the lectern tab. Since items are continuously cycling each time I send a command, nothing is ever in the same place in the UI. Muscle memory can't form, and I end up having to read tool tips or use the search bar. Some things I have as different colors or different items (purple glass doors for apparatus, rune wood door for spirit altar). Which helps...

#

But I wonder if it would be beneficial instead to design a standard subsystem interface that is basically a black box schematic that outputs signals on A, B, or C wires. So instead of looking for a "start Apparatus". It instead has readers for each command as generic "1", "2", "3" and pulses the selected line when "Apparatus" is called

#

In fact since I've been reading way too much Storage Tech Discord encoded stuff, a command to binary and binary to command decoder might be a good idea

#

User interface side, id select "start single" "start batch" and maybe a couple other commands as needed. Have a module that converts that enum into an array of binary codes that get decoded by the subsystem

#

Binary because I need at least 3 commands I think. But with two bits, that's already 4 possible. If I go with 3 bits, then that's 8 possible commands

#

And really I guess, I could set it so that calling an address with no command bits sends a clear command. Which would be just triggering a toss turret to drain everything from that subsystem

#

But the goal here is that I wouldn't need to add a new item to the system on every function I want to add. I don't need to name 3 items and add them to the command tab for sending to the smelter, or adding a system where I can tell it to process x cycles of something. I can just plop down a com receiver schematic, bind the lecterns and be done

#

And then the only thing added to the command tab is a single item for that subsystem address item

#

Commands themselves can be a set of banners that visually represent options better than figuring out which of the 3 witch wood doors are starting a thunderstorm instead of clearing rain

#

No particular order:

Single
Batch
Clear
Get Status

#

I suppose cloudshaper, or some others would certainly benefit from more specific information

#

Maybe also have commands for generic
Run A
Run B
Run C

#

Though really making it "Single/A" "Batch/B" is probably the better call

#

Does require you to know what A and B represent though

#

So. design:

Comparators in subtract mode reading each bit. Subtract the subsystem address bit. So basically nobody sends a signal until the address comes in telling that system to run a command. That's easy enough. Im trying to think of how I could design this to work nicely with schematics though. Which means very few wand links

#

Ideally I'd be able to pull this command receiver off with a single lectern linking to the command network and I guess a source jar

#

Because right now I can't really make schematics of anything because they need so many links to be useful

#

Link this lectern to primary, this lectern to commands, this lectern to items. This display case to commands and set it to look for this item. This other display case looking for this item

#

Then again, a decoder isn't exactly small either. And I don't really have a great solution for transmitting those bits besides a display case for each bit

#

Seems like the most compact might actually be 3 items. 4 if you count air..

Clear is when you send nothing.
A is sending a stackable item as the command index
B is sending a 16 stackable like a snowball
C is sending an unstackable

#

There's 4 commands. Without needing anything more than reading a comparator level on a pedestal that gets an item when a command is sent to that address.. that would still need some form of redcoder to unary to trigger one of the 4 output lines

#

That's only 0,1,3,15 though. So could probably be decently compact. If I really wanted to complicate the module, I could treat those as separate bits even and get 16 commands

#

I don't want to build an item sorter to make sure the bits are in the right place though

hidden mesa
#

i just wanna say this is far beyond my comprehension but goddamn good work

fluid wigeon
#

Thank you. My goal is to make it as easy to modularize and reproduce as possible

#

Ideally I could start a new world and not long after getting materials for a small lectern network, I'd be able to add WyrmOS with a couple modules

fluid wigeon
#

I like the idea of the binary code. But I don't think it will be practical. Id either have to set up display cases for each bit, and link those display cases to a network. Or else pull the command bits from the command network and return them back to it somehow. And with that, I'd still need to sort them to make sure the right bit goes to the right place

#

And that all just gets bigger and bigger for a command receiver module. Or extra links and display cases each time

#

So as much as I like the concept of it. I think just having it look for an enum value instead makes the most sense. I wouldn't need all the bits anyway if it's just a smelter where basically the only thing it needs is a "go" which can be done with just the smelt command itself. No extra data, because there aren't other commands

#

And to be fair. I'm not using traditional redstone techniques here for most of this. Having a module where specific blocks are the outputs for if a given command is sent isn't actually as useful as simply a single display case and lectern next to a turret

#

I think I really just need to refine the command TX module and primary hub for the input and command storages

#

Id bet I could fit the entire brain of the system within a 4x4x4. 3x3x3 maybe, but that's cutting it close because of lectern adjacency

fluid wigeon
#

Mock up in bedrock/pocket. Powering lecterns makes them not pull from adjacent.

4 lecterns: in no particular order because it doesn't actually matter. Primary, item Input, Commands, Recipes.

Recipe storage itself can fit just about anywhere in here. Dropper is aimed up at a barrel here, but would be a repo catalog. The comparator out is powering a barrel, but that would be a repo for item input's storage. Recipe lectern would be any extra space. I have the dropper and redstone sitting on blocks here, but could easily be recipe or command storage

So 3x3x4 and that's it

#

Redstone blocks under the lecterns so they don't pull from anything ever.

#

Yeah that's the wyrm OS brain. In fact, flip the dropper back to facing down, and have the command storage be under the dropper, comparator, and first repeater. That's 108 commands. Plenty. The barrels on the right can instead be recipe storage. None of the inventories are next to a lectern. Could move the recipe barrels to just the back and open up the blocks behind the block above the lecterns, for color coding too.

So then adding a new system is linking the command rx cases to the command line. Item processing to the item line (triggered by the command line). Recipes exists for if I've got recipe batching. Figured I can wrap that up in this module as well

fluid wigeon
#

I suppose another approach would be the thought on having the sub acknowledge the command instead of the repeater delay

#

Another arrangement. But I don't like the visible repeater there in the middle

#

I could drop it down a block. But then it's not 3x3x4. It's 3x4x4

#

Though I guess by redstone standards it already is because of the support blocka

#

I do like this one though. Color coded and no lecterns next to each other

fluid wigeon
#

I think I can simplify and compact the batcher too

feral pier
#

designing in pocket edition is crazy dedication

fluid wigeon
#

I have my phone with me. I don't have a Java client with Ars with me

fluid wigeon
#

Batcher doodle. Left is existing slice. Right removes observers, sticky piston, and noteblock. Swaps to torches instead

fluid wigeon
#

Probably some rail system that would work. But I don't know if they'll be more compact since while it uses observers, id need to prevent the double pulsing, and I'm struggling on finding a good rising edge that won't make this bigger

fluid wigeon
#

yeah so much simpler

regal rune
#

Epic

fluid wigeon
#

though the chests there would be lecterns

regal rune
#

ic

fluid wigeon
#

Would need to test though loading and unloading if the redstone torch causes the top turrets to fire without items in the filters.. that might be a thing

fluid wigeon
#

Could do it more compact with bulbs now that I think about it more. Using the bulb changing state as a rising edge detector. Observer watching it instead of comparator. I don't care about the current state, just the change of state

#

Or dispenser with powder snow bucket. The extra block space might help even. Comparator from pedestal into the block like now. Dispenser of snow or bulb above that. Observer could direct power the first interact turret.

#

Doesn't really compact that much I suppose. But very clean and no longer a constant powered torch on one of the turrets

#

What I really need to look at though is simplifying the shulker unloader. I'm still not happy with it

fluid wigeon
#

i suppose dropper/hopper as a rising edge is the same as dispenser/snow. but gives a longer signal. A. cant use observer on that then without double pulses. B. not using observers might be good

#

but adds hoppers to worry about then

fluid wigeon
#

I've been thinking

#

Which is dangerous

#

At the moment, I'm not happy with my item tab. Caching issues are resulting in item orders being mixed up

#

I need to do some testing with multiple storage blocks used together.

I've got my main network, it needs to connect to a named inventory (or several inventories) called "Input".

I wonder if I can name decorated pots. This guarantees only a single item type. If I have Input be a couple pots and then a repo, does the lectern first try to go on cached data? Or if everything is empty, does it still follow standard linking order?

#

I'm still working on ideas for modularizing the main control hub into a small standardized footprint. And trying to decide the architecture for the input tab. Single repo or chest are susceptible to the issues with caching messing with item order. Which is causing apparatus recipes to fail

fluid wigeon
#

I wonder.. if I can sort out this input issue. If it might make sense to combine input and command tabs.

#

I suppose the command itself is a single item. At the moment, that uses a dropper on a delay. But it could just as easily be a pedestal and hopper, or turret. Would just need to ensure filtering works to keep that pedestal clear for the command

#

It would still be a separate network though I think to keep things clear. I need the data to go to subsystems for display cases to read, but I don't want the item to be pulled by the turrets

#

Though that was the original thought months ago anyway.. it's not out of the question, but would require separate handling

young nacelle
#

Testing with decorated pots in 1.21 shows they lose their name when placed by player. Haven't tried other methods, yet.

fluid wigeon
#

Hmm. Then probably can't take a projectile name spell. That complicates things

#

Fillers are one bad option. I can easily slap deny scrolls on stuff

young nacelle
#

I do have a patchfeature request to name pedestals or platforms.

fluid wigeon
#

Id want to avoid hoppers. That was my original fix with the apparatus early on. But not sustainable for more expansion. I don't want to wait for a hopper to load items for smelting stacks at a time

#

Hopper cart is faster. But that's a lot bigger, and still effectively limited to hopper rates ultimately without the weird cart splitting things where the cart sits on 4 hoppers

#

Also I hadn't even considered if pedestals could be named lol

#

That's an issue with that plan lol

#

I'm overall very happy with the system in practice. Couple things I don't like though:

  • The main brain is spread out. I want it compact and easy to rebuild.
  • Apparatus batcher is huge. I want to play with serial batching for the apparatus. I'm already limited to hopper speeds effectively anyway, so doing it in parallel isn't giving me anything. I could just process one item at a time at hopper speed and be just as fast at a fraction of the size.
  • I would love a standard drop in controller for all systems. I don't know if I really need much besides the display case though
  • Button panel concept works great, but lacks the fixed locations that make a button panel useful
fluid wigeon
#

I do still need to design a good expandable stock system for things like smelting

#

Though really manually sending stacks at a time is probably fine

#

And a master lock out switch

river pewter
#

hay zieg i am working on a smart crafting system based on creates stock system and books as recipe holders its based on Redstone Requeters that when used with smart observers decet the books to send the items to the reqried locations

fluid wigeon
#

I really need to dig in to create logistics. The system looks really fun

rough pebble
#

Can someone link to the top of this thread? Want to backread everything about it

fluid wigeon
#

The idea changed part way through

#

Current scope^

river pewter
#

becase the system of create logistics unlike wyrms deposits as in order of arrival so one reqestrer is for the apratous and one is for the other items

fluid wigeon
#

Can always request the batch and do the splitting logistics on site

river pewter
#

no i tried that with filters and other things but addons and other recipes having items that go in first for one recipe and secondary for a second it fails but heres my storage system/ command system

fluid wigeon
#

Item ordering has been a thorn in my side as well

#

The caching of lecterns keeps messing up item order when I drop them into the tab

river pewter
#

good to know and becase of how the system has to be set up i need a lot set up i am on verson 6 of the system

#

hay z did you look at infinite mana regen v becase i plan to build a system based on it

fluid wigeon
#

The standard on that is just any item production you can scale without killing your server. Toss them into a touch rune sensitive pickup and have a void jar set for that item

#

As usual, set up some redstone so it only runs when needed

#

Lectern access, enchanter eye, or any other wireless redstone can handle that

river pewter
fluid wigeon
#

Huh. So the projectile causes the player to "eat" the jelly?

#

The rune sensitive propagate projectile is brilliant and I'll be stealing that

river pewter
#

ya that is a good the infuse takes one the property of they jellys effect if it passes threw with infuse

fluid wigeon
#

But the "projectile using the player look vector" it's insanely useful

#

Like. There's tons of vanilla sorcery using deflected wind charges to detect player look vectors

#

But using that rune/projectile system, that's like 3 blocks

#

Could have an eye that simply depowers a rune, which then activates by the chicken, firing a spell at whatever direction you want. Look north and right click the eye, so it fires a projectile at a sensor there to teleport home. South to get to spawn, up to go to the end, whatever

#

That's brilliant

#

So much simpler than the other system

#

Oh. Need to send that to the arrow cannon thread

river pewter
#

the way i plant to use this reqires 1 create addon called moble packages it adds a portable stock ticker so you can reomtly accous creates stock system and i plan to use that with turrets to create a warp gate system

fluid wigeon
#

I've got a drafted idea for a warp system via lectern remote access, but haven't built it yet. Basically taking the tab/button command system from this topic and using that to pick destinations. When the player makes the selection (pulling a scroll and placing it back in) it activates an exchange rune to warp that player to the warp chamber, and then their head is in another blink rune to the destination

#

Since blink runes will use an adjacent inventory, it's basically just pulling the scroll from storage and placing it in a dropper next to the rune to set the destination.

When an item is in the dropper, a comparator reads that, fires a separate dropper to activate the exchange rune, pulling the player, and then the player head activates the blink rune.

After 2 seconds the dropper fires to send the scroll back to storage

#

But that rune sensitive prop projectile. Absolutely going to use that

#

Need a way to keep the chicken in place that's not just surrounding it with blocks.

#

Maybe just an item in an upward dropper actually. Rune sensitive propagate projectile redstone signal reset reset pickup maybe

#

Eye powers the dropper, triggers the spell, fires in the direction being faced, reset makes the rune the caster again to then pick up and place back in the dropper

#

Else dropper on a side, hopper under it.

I'm thinking for something like a screen cursor here. Able to detect that the player looked 45 left, right, up, down

river pewter
#

ya thats a good idea and projectile(propagete self)infuse on a turrit is my idea with redstone triger

fluid wigeon
#

Turret can't propagate to self

#

With runes, it knows who set the spell, so propagate self works. Turrets don't know who placed or set them

regal rune
#

which is why the permanent rune with the chicken on it is needed

#

wait

#

there

#

"perminate " lol

#

sorry continue

river pewter
#

good damit droper it is i put it in to a portal on the block of the rune

fluid wigeon
#

My issue with my existing tab item selection/button system is the lack of muscle memory, if I have a bunch of similar items that do different things, they end up in different orders.

With a look vector detector, everything is in the same place

regal rune
#

skill based inventory management system

#

also Look vector detector? can you elaborate slightly?

fluid wigeon
#

Rune sensitive propagate projectile effectively fires a projectile where the player is looking

regal rune
#

ah ok so in that context

fluid wigeon
#

They had to account for that with the chicken mana Regen by surrounding it with prisms

regal rune
#

I understand now

fluid wigeon
#

But if you don't constrain the projectile, you now have an invisible selector screen from anywhere

river pewter
#

not my style its why i use atleast 2 items in for a storage system z

regal rune
#

touch screen
have a pinging system then look at the direction you want to go

fluid wigeon
#

Vanilla systems involve bouncing a breeze wind charge with a player-shot arrow, to detect different look directions. Else creeking

#

But with runes, you could fire once on demand instead of eternally looking for the player direction

regal rune
#

indeed

fluid wigeon
#

Heh. It's basically building a system like the botania manufacturer halo

regal rune
#

exept far more technicall

fluid wigeon
#

Invisible selector screen around you.

Could easily integrate this into my existing system. For non-item commands like rain

#

6 commands for cardinal and up/down.

Need to test reliability for 45 off cardinal, and diagonal up/down

#

26 commands would be plenty

#

Too bad the cloudshaper ritual is so slow. Can't angrily shout at the sky to make a thunderstorm

#

Could trivially double the commands if you build it to accept multiple clicks at one location. Two hits at the same spot to activate something else

#

I wonder if the eye can directly take a projectile propagate projectile

#

Have the spell fire through the scry crystal, hit a player head or something in the center, and then change direction

#

Ooh. Even without that... Multiple runes with this system opens up a fun realm of ideas like weapon turrets on an airship or something like that

#

Cannons on the side of a ship that all fire where the player is looking

#

Probably just use armor stands instead of chickens

#

Need to test the eye/scry crystal using projectile propagate projectile at an armor stand.

Would greatly simplify this

#

Can go the route of unlocking a rune that has an armor stand in it. But direct crystal would be so much simpler

regal rune
#

use the selector screen to shift weapon systems?
so like I have 5 "turrets" each with a diff spell I look to position 1 then again to target one
first selects the type second the target

river pewter
fluid wigeon
#

I'm just thinking an array of turrets that all fire together the same direction

fluid wigeon
#

It takes like 15 seconds to actually start the storm

#

I want to shout at the sky and have it be immediate

#

Which...

Actually I could do

#

You can pause the ritual just before it starts, so the command is instant then...

regal rune
fluid wigeon
#

Dammit .. now I need to redesign that weather machine. I don't like how slow it is

regal rune
fluid wigeon
#

But I could queue up all 3 types, command unlocks it to activate, then sets up the next one and locks it

#

Yeah

#

Not as compact. My current 3 in one is like 3x4x5..

But instant is much better

river pewter
#

good idea z i like it

regal rune
#

wyrmOS wizard gang
we love making great ideas

fluid wigeon
#

During design I ran into issues with it locking before it could finish. Had to make sure it was able to run

#

Would just need to get the timing. That's easy enough

river pewter
#

and your fergeting you have create

regal rune
#

in this context we want to keep it to bas ars iirc
but yes create would help out alot here

river pewter
#

i use create redstone in alot of my projects

fluid wigeon
#

Same. But the overall goal here is to use ars for infrastructure that interfaces with other mods for base control

#

Still need to redesign the brain to be a module that's super compact and able to slot into any base

#

The item ordering issue is throwing off those plans though

#

also me getting distracted by nightingale for the past two months

regal rune
#

oh so thats where you were

fluid wigeon
#

I've almost beaten it

regal rune
#

respectable

fluid wigeon
#

Made me

regal rune
#

a knife

fluid wigeon
#

Couldn't get the shirt the right green. That fiber is the lightest solid color green without going to the bug yellow silk

#

The knife (right hand) throws fireballs, the throwing knives held up are just throwing knives

#

They don't have a main hand tool that's dedicated for magic. Every main hand tool can have spells applied to them. And everything is custom depending on the materials used to make them

regal rune
#

Ic why you might like it then

fluid wigeon
#

The shirt/vest/tie is actually different materials, but there's a whole glamour system to change material appearance and even the actual outfit appearance to anything you already unlocked

#

Anyway. Almost beaten it I think. But it's really good so been completely out of the loop on a lot of stuff

regal rune
#

i understand
there are only so many hours in the day

river pewter
#

i actully only can work on weekends or in rare cases weeks but the reasen is i am stilll in highschool

fluid wigeon
#

Morning before kids wake up

river pewter
#

your a dad zeig thats cool i spent

#

but any ideas on a curcit desighns

fluid wigeon
#

For the jelly infuser?

I'd say the same thing they've got there. How long does the effect last?

#

The chicken is sitting on a rune, a simple improvement there is to swap to an armor stand, no AI there.

The rune could be locked by powering an adjacent block. Slow down the clock by unlocking it at the same time as the effect would run out. so it's not constantly draining source

#

I assume the large block of prisms is just to make sure everything goes the right direction. If you wanted multiple jellies used, either build multiple systems or run the clock faster, while having a prism/sticky piston system at the output to change what direction it goes

#

Pierce on the projectile might also just make it work with a line of jelly

#

Prisms can be moved with pistons, and an observer will pulse when spells go through the prism

#

So you could set a line of prisms that move after sending a spell down their path

#

Observer watching a prism that then 1-ticks a sticky piston (or I guess a regular piston to push it). When all jellies are used, it triggers a reset that pushes them all back in place

river pewter
#

thanks zeig

river pewter
#

hay zeig i have an idea scryers eyes cout as the playercasting a spell right

river pewter
#

i hope i does becase of its use in replaceing the rune

fluid wigeon
river pewter
#

if it does i will make the infuser work easily and simply

river pewter
#

zeig have you seen ars zero because its a diffrent spellcasting toolset

river pewter
#

becase the staffs seem cool to use

fluid wigeon
#

Haven't seen it yet

river pewter
#

its in addons look at it

#

its cool and usefull

river pewter
#

so i tried it and it word with infuse but do not use telefast on a create tank it crashes

river pewter
#

Exploring Ars Nouveau featuring INFINITE health regen and mana regen as well as insta-killing mobs, and the reactive enchantment!

If you have any questions about this video, or any minecraft related questions, feel free to join the discord and ask in my #minecraft-qa section!

Ars Spellcrafting 1
https://youtu.be/AwcPpOjBM0E?si=EWfkzca7UOcFMnQ...

▶ Play video
cyan summit
#

@fluid wigeon You’re genuinely so smart idk how your head can fit your massive brain.

Literally implementing AE2 auto-crafting and bussing, without AE2. I would never have even thought of, let alone attempted such an ambitious concept using just Ars and vanilla block.

fluid wigeon
#

I watch a lot of tango. He implements a lot of signaling and bussing with vanilla. We've got it relatively easy with modded

#

Actually a lot is inspired by mattbatwings and computational redstone, mixed with storage tech

fluid wigeon
#

So yeah an eye with projectile, propagate projectile just straight up works as a player look vector detector

#

No armor stand needed. Touch works as well, but the projectile origin is higher then.

Projectile makes the propagated projectile originate at the center of the block of the crystal. While touch seems to target the top of the block above the crystal (crystal aimed upwards)

#

One block, instant look vector controller

river pewter
#

zeig look at ars zeros circlet its a handless spellbook alterante

river pewter
#

also a big tango fan you seen his plans for decked out III becase its of the charts

fluid wigeon
#

His communication bus line from Decked out 2 was a big inspiration on this project. I look forward to seeing what he does on 3

river pewter
#

so am i might use ars and create to make a dungion

#

also i would like ask would you try it out

river pewter
#

so i've been thinking of doing this for months and am now going to do it

river pewter
#

its going to be a base for my modpack arcana whitch will have a costom world with it in verson 2.0

fluid wigeon
#

Sounds like fun. I can't guarantee I'll play it. Mostly because I'm behind on about 30 other things as well lol

river pewter
#

also #1432008462929236071 is getting added to my modpack becase of it

#

use and more spell casting items

regal rune
#

ars zero is epic

river pewter
#

i agree its so usefull aspecily when its curcet if fixed to show spells

#

we can fanily have handless spellcasting

river pewter
#

zeig when is your next video

river pewter
#

i have an idea for the system upgrade with costom gateways

#

have you seen the scroll holder from ars control

echo marlin
#

Huh, I wonder if there's any interesting automation to do with a Planarium getting re-named by various turrets.

fluid wigeon
#

They're all individual dimensions, the jars themselves serve no real purpose beyond giving a name to the contents and the ability to sneak right click to enter

#

So you could build a swapper easily enough I suppose. But generally the jar itself can be just as easily accessed with a stabilized portal anywhere else

fluid wigeon
stuck mauve
#

just read about this, this seems kinda insane

#

i can see some simpler things like having a section that just moves everying out of it into a furnace or something

#

maybe an infuser array for putting in source gems from storage for essence

#

and 1 for lapis/amethyst to make source gems

#

but the idea of having it for moving items in to activate redstone machines in nuts

#

i see the similarity with something like decked out like you said

#

having the storage output immediatly into a line of filters that trigger redstone wires seems like the best start, redirecting the paper back to storage, 1 section for commands and another for activating them

#

would work best with wireless restone things like create, tho you were trying to keep it to base ars

#

could set up a lot of smart base features

#

lights, on and off switches for farms

#

maybe one that's set up to teleport you to preset locations anywhere you have access to storage without using your own spells or a portal, preset turret setup with a blink spell

#

if youre fancy maybe a section that outputs into a shulkerbox loader?

#

or whatever other output things i cant think of

hidden mesa
#

I mean yeah the whole point is to have it be something insane

#

it is explicitly a monument to hubris

stuck mauve
#

true

#

the idea of having the commands mobily set up autocrafting setups for a wixie, that's insane

river pewter
hidden mesa
#

wait how is this related to WyrmOS

regal rune
#

🤷

river pewter
#

You hock it up to it as an addon

fluid wigeon
#

👨‍🍳

fluid wigeon
#

Working on redesigning the main brain so it's a simple drop-in to any storage system

#

Still not quite satisfied with the command processing (cyan wool on the left)

#

And I don't like the use of starbuncles for the item input. That lectern caching is killing me when item order matters

#

Apparatus one-off crafts specifically get mixed up. Batching with the recipe handler works fine, since those don't have lectern cache issues with the current design (I also want to rebuild that though).

But caching makes it so that if I send 3 items via lectern, then an external process pulls those items out, the cache tells the lectern that the next item goes in slot 3 instead of 1

#

So then item order gets inverted unless the whole system unloads

#

Could do something weird like inserting a single item and removing it after each command... Don't really like that idea.. but it could mean no entities (buncles)

#

Dropper into a lectern and a filter I guess? But then again it would need to be on the primary network since that's the one that I'm inserting through, so that's the cache I need to wipe

#

And that gets weird anyway then, since a filter bumps the priority for that item

fluid wigeon
#

Design requirements for WyrmOS Controller:

  • Single compact schematic containing all infrastructure. Ideally less than 5x5x5 total.

  • Ideally no living entities. Mages aren't known for being safe with splash damage.

  • Primary Net: main user access point. Named tabs for Command entry and Item Handler and Overflow. Additional named tabs for other subsystems are outside the primary controller.

  • Item Handler: materials to be processed by commands. The main issue here is item ordering. Caching is breaking item ordering at the moment. Two buncles works it seems, since they'll pull faster than the player would input generally. Hoppers are way too slow. Turrets are an option I suppose

  • Command Entry: command items get pulled from command storage and placed into the command handler (dropper). After a short delay, the dropper fires and returns the command to storage

  • Overflow: safety named storage connected after all primary storage is connected. Before Commands or Items get linked up. Monitored and connected to an alarm. Nothing should ever go in here. That means your primary storage is full

river pewter
#

cool but thats going to take a wihle

fluid wigeon
#

It's all built. Just in separate parts. I'm just wanting to compact it into a single module

river pewter
#

Good now just doing that

river pewter
#

zeig watched your newest video good idea with the pacts

river pewter
#

MY NEW ARS AUTO APPARUOS

fluid wigeon
#

I love it! What are the brown boxes with the ghost platforms in them?

#

Makes me think of old thaumcraft transvector interface

river pewter
#

it's from a mod called entanged i also made an spirt alter verson just remove 4 of the entanged blocks

regal rune
#

I wonder zieg
have you ever played around with the mana and artifice constructs?

river pewter
#

Does rune blink act like an enderpeal chamber

fluid wigeon
#

Rune exchange is more like an ender pearl, if something triggers it, then it warps you to it

#

Rune blink is a teleport pad, to send you somewhere else

river pewter
#

Good to know thanks zeig

river pewter
#

zeig an idea when you use wololo on a source jar it chages the sources color

fluid wigeon
#

I have my source generation floating above my base, and changed the relay colors to match the 4 elements so it has beams of power going through colored crystals

hidden mesa
#

hell yeah???

fluid wigeon
#

need to find a more up to date pic

river pewter
#

no i mean like the source in the jar is that something you could do

fluid wigeon
#

Oh, it's not currently a thing. I'm not code, I just see what's possible with existing mechanics

river pewter
#

Could you suggest it

fluid wigeon
#

WyrmWarp hub:

two booths for you and a friend.

each player has their own lectern (not pictured, doesnt need to be anywhere in particular). which sees the top dropper and the main warp scroll storage. open up a scry eye or warp index to that lectern network, pull the warp scroll you want and place it back in. it'll pull from the scroll storage and send to the top dropper.

when the top dropper has an item, comparator detects it, powers the block, which has dust under it, powering the block next to the bottom dropper. sending a junk item into the bottom rune (touch rune sensitive exchange). Which then swaps places with the player whose teleport booth it is. when the player arrives, their body is then triggering the top rune (touch rune filter:Player blink) which then immediately teleports them a second time to the warp scroll destination.

the observer detects the bottom rune fire and recharge, which pulses (two times, but thats fine) and triggers the top dropper to send the scroll to the middle chest, which is then pulled back to scroll storage by the middle lectern

#

still working out how to add this into my main base networks so that it doesnt teleport me any time i send any warp scroll into storage. might just leave it isolated

#

exchange works across dimensions btw. so this works to teleport you from literally anywhere to any destination you have a scroll for

regal rune
#

noiiiicee

#

I wonder Zeig
have you ever used the mod Mana and Artifice (1.20.1)? specifically the constructs
I bet you would really enjoy them.

fluid wigeon
#

I haven't. Kind of by design. M&A is from mithion, original author of Ars Magicka. Which I'm a huge fan of, and was sort of what made Bailey start Ars Nouveau in the first place. M&A came out about the same time as AN, and we didn't want to be thought of as ripping them off, so I intentionally haven't touched their mod, so I don't subconsciously take inspiration when giving my thoughts and ideas to Bailey

regal rune
#

checks out actually
I will say that after about 5 years though the only similarities between the mods is that they clearly had some inspiration from ars magicka after that there is literally zero similarities in any and all of the aspects and mechanics of either mod

#

though its likely a good thing that you dont take inspiration from mna
gaining craftables from non automatable rituals at early teirs is not something I or my therapist wants to see brought over

hidden mesa
#

Reminds me of the good ol' days with AM1, where you had the 'light magic' gathering rituals that would work just, passively, and auto-craft without using the materials on anything 'less expensive than a diamond', which is where we got into the EE2 conversions.

fluid wigeon
#

I had a ton of fun with AM2, built a full network of all 3 power systems and distributed through the base

regal rune
#

ive never actually used ars's predecessor, but for it to have spawned mods like this one
it must have been legendary

hidden mesa
#

AM1 was...hm.

#

Well, I will say you had to raise your 'mage level' by spending EXP, which lead me and my friend to construct the 'bee wiggler', which was a chamber filled with forestry bees that had a passive XP gain as long as they were Out Harvesting, and then a hover device designed to float you into a sphere of that.

#

to /get/ your spells, it was a bit like Irons--you'd raid a bunch of structures over and over again until you had everything.

#

AM2 added the grammatical spell creation like AM1 had, but you paid for your spell with materials upfront, and you had to grind essences by killing specific elemental bosses over and over again.

#

IE, you crafted glyphs, you spent the glyphs, you crafted the glyphs again for your new spell.

fluid wigeon
#

And then Earth armor made you basically immune to damage

umbral hull
#

hi

#

just wanted to know if this is a complete thing like a show off or if this is still being worked on for a full functioning first release

#

and if it is full functional/finished can somebody send a world download or a schematic and maybe some other instructions bc i didnt feel like going from the top thrue 2,3k messages

fluid wigeon
#

It's still in development. I am also working on some simplifications and modularizations, so it could be dropped into any base to allow automation and wireless controls

umbral hull
#

ah okay

river pewter
#

This is great

regal rune
#

indeed\

river pewter
#

so zeig i am building an auto armory and i want to show what armor i have on by telporting the armor stand to a place in the center any ideas

fluid wigeon
#

You'll need two basic systems. Teleporter and breaker. Simple harm pickup should work for that.

You'd need to filter the results back to the right place then.

Alternative is to leave them as entities and swap around with exchange instead

#

Teleport and break is conceptually simple, but again, redispesing the armor and making sure it goes to the right holding cell is the complicated part.

When you want to swap what's in the center, you break the current middle one, pick it up, and then trigger the blink at the new selection

#

I suppose another option is doing like doc did with his armor trim setup. With an Ars twist.

  • Blink the selected armor to the center.
  • That selection also unlocks a blink rune under the floor, or perhaps just swaps scrolls for that rune.
  • When you want a new stand, piston open the floor, allowing the current one to fall through.
  • Either have one of many runes unlocked, so it'll warp to the correct place, or swap scrolls so it'll blink to the right place. Either option works.
  • Trigger the next armor to blink into position
#

Has the risk of getting out of sync. Needing to track which scroll/rune is active

#

But probably easiest to build

#
  1. Select the new display
  2. Trigger the floor
  3. Observer to detect the rune trigger, basically the same circuit as my teleport booth, honestly. Return the scroll and armor to the correct holding cell.
  4. Blink the new stand and new scroll to the correct places. Simple dropper into a chest next to a lectern linked to the rune's chest would work simple enough
river pewter
#

TanTanksks

fluid wigeon
#

Had a random thought. At the moment, my command handler is basically checking a dropper to see if it has a command.

Another option I suppose I could do is the opposite, simply check the repo for the absence of a command

#

Because then, it's the act of me pulling the item out that starts it.

#

I suppose one issue with that might be for the teleporter though, since I do specifically need the warp scroll to be in the dropper

#

That does open the possibility for full duplex transmit and receive though. Responses from subsystems can just pull out a command message. Basically like circuits that pull a signal to ground

#

In which case, it's super trivial to build in failsafe checks. If a system is triggered, have it pull out the ACK message to indicate it acknowledged the command

#

They then just need to drop the replies back to the command network after a second or two

#

It would mean the main OS brain would greatly be reduced, since then it's just command storage, no moving things around. Connection order wouldn't matter, no delay to return to storage

#

And since there wouldn't be any dropper timing to ensure display cases have enough time to read, I would never have to worry about multiple commands being sent at the same time. I don't have to make sure the dropper is empty

#

Though the main issue I see as I think about this is if my main network gets unloaded, everything will read a zero, and think it should trigger

#

I suppose a common master control item is an option. Nothing runs if that is not there

#

If the base is offline, unloaded, or I simply flip the lever, then nothing runs. Each subsystem needs to see that the main control is there before reading any of the other message display cases

#

That does somewhat limit me on the subsystem design though, since each command reader at the sub would need to also be reading the main line

#

And of course the other drawback of needing to flip all my existing display cases to invert signal

fluid wigeon
#

To be honest, other than ACK responses, I don't actually need reply messages off the top of my head.

If a sub system needs something, generally that should have already triggered another system anyway because of being low on something

#

I do still like that older idea of remote reconfiguring of a lectern to be able to see what is currently going on at a sub though. Quick tab over to the apparatus to see what's up there

#

But in a larger base, that quickly becomes a system of redesigning the internet. Needing to know that to connect to the smelter, I need to link up several lecterns

#

I suppose the reply messages works for that though..

Say I have a big tree of remote Lectern connections; primary lecterns at each sub system, and connections back along the branches back to a console lectern at base.

If the smelter (with two inventories, input and output, named, so they're different tabs) needs to branch back through 5 lecterns to get to the console, I could send the command to link the smelter. That one also would send the command to link the next lectern in the chain back up through the hierarchy. Similar to a default gateway

#

Oh hmmm... Almost.

Because the linking needs to go the other way.

So if I have a tree as this pic

#

To link the console to j, id need to first set J. J would be a display case at G to use an advanced dominion wand on it (bound to j)

When G gets that signal, it sends its name to the command line, which sets F. F sets B. B sets A. For clean user interface, the console is always set to A

#

Oh here's a fun idea. I wonder if an interact spell would work instead of a dispenser with an advanced dominion wand.

So each node watches for its children and itself to be triggered. Self calls are after a half second delay circuit. Calls to a node child also trigger a self call after a delay

G sees "Call J", fires, and queues up a "Call G". J sees "Call J" and waits, then triggers. The "Call G" is triggered.

"Call G" is put on the line, this triggers F, then G, and places the "call F" message

#

There's only ever one dominion wand, just being passed around on a dedicated lectern

#

But that seems infinitely expandable and much easier than some lookup table saying "for J, go AB, BF, FG, GJ"

fluid wigeon
#

Each node of course then needs like 6 lectern networks lol

fluid wigeon
#

Turning a lectern into a web browser

fluid wigeon
#

Thinking out loud as usual:

If I do active low, then that means every display case needs two display cases. One to check that the base is online, and one to check for the actual message it is looking for.

I can make that AND gate decently compact, it's just that it adds up, doubling the display case requirements

#

But it means I don't need any timing or logic in the main controller. And then I can build in a system instead that beeps when a message is acknowledged.

Pull the command, wait til a beep, drop it back in

fluid wigeon
#

Next rubber duck:

Been thinking about serial communication protocols in Minecraft for sending data between different areas. Because that's fun for some reason.

Real world SPI communication uses a clock line, MOSI (main out, sub in), MISO (main in, sub out), and chip select lines, one per sub.

Real world I2C just has clock and data. And each message includes an address for who needs to listen. Real world this works by whoever is talking pulls the signal to ground, so it's bi directional with one wire. Minecraft repeaters are one direction, so that would need modified.

Could do something where you'd combine them a bit. SPI chip select is separate wires for each device. I2C packs that addressing into the message itself.

The simplest would be a SPI with a hex chip select line that is simply set to a value for 16 addresses, and remove the clock line. Only the device that is selected allows whatever incoming data to go to its shift register

#

In redstone terms:

16 possible destinations, and however many bits of data you want. Let's say you have 4 farms at 8 different districts. You could use 5 bits in the message. Farm 8, 4, 2, 1. And a read/write bit. Probably need a start bit as well, so it knows when the message starts

Set the chip select to district 2 (hex signal strength 2), and then transmit 1, x,x,x,x, 1. For (start, farm 8,4,2,1, read).

The farm controller would reply with what farms are currently running (let's say 8 and 4 are running). So it replies back on the MISO line with 11100. (Start, 8,4,2,1) And the main control would set those values to show that those two farms are currently running

#

Overly complicated redstone, because why not

#

In the context of WyrmOS, my use of items is both the address and the instructions. One item means "fire a turret that starts the apparatus"

#

And with subsystems being custom redstone per build, it probably doesn't make sense to have generic bit-based instructions, which get read if the address is called up.

An example would be items representing bits 8,4,2,1 and then an item for each subsystem.

If "start" was message 0001, then the message bits would be set, and when the address item is called, that unlocks reading the message at that address. So 5 display cases, the first 4 get unlocked by the address item

#

But since something like a smelter really doesn't need any more instructions besides "fire the turret to pull from the item network, and start smelting". It wouldn't make much sense to bother with a full 16 possible messages

#

Ramblings of a mad man

#

You could definitely get overcomplicated by making new commands like "take the single item from the input network, and smelt 5 stacks worth of it"

#

But ultimately, from a user perspective, you'd still want that to be only a few clicks. Not manually setting the message bits. So it would still be a physical lookup table for the "pull stacks of this single item" command. And at that point, it's easier to just grab the 5 stacks of sand, and place it in the item tab, and hit start

#

The only reason you'd really benefit from serial or parallel messaging would be for things like computational redstone. And for the lectern based messaging, it's just easier and faster for single items to be the message and address

#

Even in vanilla encoded storage tech there's really only a few message types.

"Unlock a slice with this address" for sending items to storage.
"Pull shulkers from bulk storage from this address" for restocking your easier access stuff.

ripe bison
#

I don't get any of it

#

I just remembered i'm french , that's why

regal rune
fluid wigeon
fluid wigeon
#

I will say one big annoyance I have is that the lectern tab as a button panel is constantly rearranging. It's hard to find the item I want if the tab has several things with the same base item

#

IRL button panels and user interfaces don't move around. You can get the muscle memory for where specific buttons are

#

Not to mention being able to read labels without explicitly mousing over it to see the name

river pewter
#

zeig idea turit with projectile name as the spell for phlactorys

glacial hawk
#

some people scare me

#

zieg is one of them