did you know that "technically updated" was the original name for minecraft 1.13, before it got changed to "update aquatic"? (disclaimer: i pulled this from memory. might not be correct.)
the actual update
today we rejoice because collectionservice replicates to the client. yay!!!! now i can actually get started on scripting the client events.
but before i do that i need to figure out which interactions need proximity prompts and which ones need clickdetectors. i would've placed prompts on everything but that might make the screen very cluttered, which is something i do not want, especially on a very setting-driven lore game like this. i want my players to pay attention to the world i built dammit!!!
so far here's what i have:
- zooming in to posters should have click detectors. not a big fan of having a prompt on the wall.
- opening cabinets (if i even want to add that) should have click detectors. this is because there are a lot of them. now i just have to decide if i want it to be on the server or on the client. i guess the stuff inside of the cabinets count as lore items, so ideally other players shouldn't interfere when you're opening them.
- tooltips and other lore items that open a ui on the screen (like computers or books) should have proximity prompts, otherwise it might not be obvious what you're clicking on.
- room doors use proximity prompts, period.
- other miscellaneous doors will be decided when they're added, but they'll be based on size, probably. closet doors might have proximity prompts.
- light switches are difficult to decide because it's a very major interaction, but it also doesn't really mean anything and can even just be disruptive if a player turns the lights on and off repeatedly. so it'll probably be a client-side thing.
- particle emitters (like water in sinks and showers) will also probably depend. i haven't decided yet.
so now i have to learn all the technical client server stuff. yay!!!!
now i'm just figuring out if it would be better to have all the tag management in one script, which is a whole other level of difficult. or maybe not. i just gotta repeat the whole code for every tag i want to use, which hopefully shouldn't be too difficult, since i'm just connecting the thing that's supposed to happen when you click the object to the respective click detector.
but honestly, on second thought, i get tired thinking of it. so you know what? i'm putting the image zoom script directly in the viewimage gui. what could possibly go wrong? it's easy enough. i totally didn't forget that stuff takes time to load on the client. i totally remembered to wait for child. definitely. (sarcasm aside, that is the only problem i encountered when coding it, so all's good! i guess!)
plans
at this point the most major thing left to do is (yknow) actually write the lore and do the refs. wonderful....