@dexrn

Implemented settings, and made transport configurable!

Here’s it listening on multiple TCP ports
Now to implement websocket

(array part of config:)

{"$type":"TCP","interface":"0.0.0.0","port":6141},
{"$type":"TCP","interface":"0.0.0.0","port":6142},
{"$type":"TCP","interface":"0.0.0.0","port":6143},
{"$type":"TCP","interface":"0.0.0.0","port":6144},
{"$type":"TCP","interface":"0.0.0.0","port":6145},
{"$type":"TCP","interface":"0.0.0.0","port":6146},
{"$type":"TCP","interface":"0.0.0.0","port":6147},
{"$type":"TCP","interface":"0.0.0.0","port":6148}

Coming in the next full update will also be UI modes

This is so that the UI is optimized for every device and their input methods

This is the Mobile one, and the main page will (when its finished) have all remotes including non-connected ones and a button to add more remotes and such.

Working on settings…!

After this there will be configuration on the serverside and then after that, audio streaming!

New logo!

(credits at end)
I intend to make the logo customizable by allowing you to change the color of various elements, and choose between different logos (since no other software ive seen does this)
Maybe even change the color of the scanner display when someone is talking even…

Thanks to Unomelon for the base, which I used to draw the scanner.

Check out Unomelon here: https://bsky.app/profile/unomelon.bsky.social, and his very cool game Allumeria here: https://allumeria.com/ (wasnt asked to add this but I think the game is really cool and am somewhat active in the community)

Finally committed the latest Shiki changes, will release UniScan’s next commit tomorrow.

Have been working on more Shiki refactors and a nice language system for servers in UniScan to provide language strings without being able to overwrite client language strings

Reworked most of the TaskPipelineBuilder with many more accepting delegate types and have done some cleanup since

Tomorrow I will finish up releasing the next Shiki version and then I think I will be able to release the next UniScan commit and then keep working for an alpha release.

Mine V3 WIP soon!

Working on a nicer api for JOS, now fields can be directly deserialized into a native class.

JOS is a project made primarily for reading and writing MineV3, which is serialized via ObjectOutputStream in the vanilla game.
However, this will work for ANY object outputted by ObjectOutputStream once finished, and will output in the same format as well.

https://github.com/team-lodestone/JavaObjectStreams

Ported it to Beta 1.2_02-20110517 (the deobfuscated dev build)

With two companion mods I wrote, it makes the game use the zone format, and doesn’t force the player into SecretMode inside TitleScreen.init.

Making a logo for NotSoSecret and then a post will be made about the two other mods incase anyone wants to use it on b1.2_02-20110517, then this project will be pretty much complete.

NOTE: slight flashing lights warning cuz of Notch’s rotting ScreenSizeCalculator code

(had to compress to upload here, to see full quality: https://www.youtube.com/watch?v=rOqPT0zQ4dg)

Marker file works

added a little warning screen

It works™️

getting yelled at by starpheus because I haven’t made devlog yet

spent all nighter last night refactoring shiki’s modulemanagement project
and then today I refactored lots of shiki’s taskpipeline project, as well as some work being done on Shiki’s Result and family

(shiki is the side project library with most of it’s code originating from UniScan, and UniScan heavily depends on it)

Now the browser initialization is much cleaner (but not perfect of course)
(first screenshot is new, second is old)

Removed HostEnvironment because we usually only grab the parts from DI anyway

For funzies, here’s the dev build running inside a rooted Oculus Quest 2 (thanks to my friend for testing this)

This is also a good test of the netcode over a long distance (they’re in Malaysia while I’m in the US)

Getting close to committing this all alongside Shiki and such…
Long cleanup process.

Here’s a showcase of my Uniden SDS100 scanning, with UniScan showing the details in real time!

I programmed in some garbage test channels so you won’t see any channels talking in this video.

Everything shown here is sent by the server and updated by the server…

Still somewhat far from complete as I have to figure out more stuff (mainly more stuff for the client to deal with, like hiding state display textblock on null bindings and more UI features/styling).

Okayyy so I was able to actually completely gut DeviceState and now it’s actually just a class which is also used to serialize individual states.
This also means I can nuke reflection from the serialization process since I can just make IDeviceState forced to inherit IStateSerializer which will be much more dynamic!!!

This means literally any states can be sent to the client and as long as the server or the module has the UI to render the states, it will work.
This also allows states to be diffed and only the changed parts to be sent

Second screenshot shows the UI sent by the server, note that the Volume: 0 is actually all being handled on the client via binding strings (where the server only sends the client the device states and the binding strings will look up those states itself)

And now we can finally start seeing the fruits of our labor

IT FINALLY WORKS
The UI shit I built on the server now syncs to the client correctly, and the flow isn’t actually too bad!

Although this will be improved by also having a registry…registry…(yeah I know it’s weird) on the client so that UI elements can have values bind to them, and all the server has to do is send the client data to those registries

Went on a small side-tangent.
Icons!

(dw still working on the SSR device stuff)

Sorry, haven’t been super active due to life.
Fixed a few bugs in the meantime and implemented most of the SSR binding stuff, but it’s far from finished, hell I haven’t even gotten to test it yet.

Will be gone for a bit tomorrow, and the next day I will be at a different house for a few days albeit with my computer.

While I didn’t get to scanner state displaying yet, I did refactor the classes that handle how remotes connect, disconnect, etc so that it’s not spread around the codebase.

This fixes a few bugs related to state management due to how originally these viewmodels were constructed separately of eachother.

Tomorrow I will be gone for a few hrs but should be back soon enough to hopefully make some more refactors and/or start on the remote display.

Pictured is the new disconnect button in the remote on the sidebar