These are my hackmud scripts! Later there will be a proper structure to this project, including maybe minifiers, but for now there is only the raw scripts.
- _q.qrv2 - A QR decoder with errasure correction support.
- _q.love - A WIP solver. It is focused on npc solving.
The love solver is meant to be a general purpose solver for any tier of locks.
The main script, love, is just a frontend for the liblove libraries. This
kind of setup is shamelessly stolen from n00bish.
This might be a moot point since the solver is open source, but since it requires some script slots to use, there might end up being some publically hosted version which some people use rather than run their own. For that purpose, there should be an option to add a charge per unlock feature, that require some sort of payment for each solve.
This would be something the hoster of the script would have to turn on and it should
support all the common escrow features, like escrow, pay.pal and jade.vita.
For the two latter one would need to assess the danger of one or two of these scripts
either going away or going rouge.
Currently the solver doesn't have any idea if the previous state no longer matches the one currenty present. This will be tricky to get right, since I'm aiming for a low call overhead on my solver, but a basic first version could just call function once first and see if the output matches the last output exactly. If it does, we can assume that nothing has changed.
The current implementation of some of the lock solve methods would not stand up
against active defences. The noticeable examples are acc_nt and sn_w_glock.
The passion harvester is meant to be a general purpose harvester for all
corp tiers. The main script passion is just a frontend for the libpassion
libraries.
Make a huristics for recognize what kind of corp we are looking at.
There are some special commands that can be given to T1 corps.
Write the parts that checks if a location is a location and if it is a npc loc or not. The npc check can be tricked, but it will help filter out any clearly non npc names from the lists.
joy is going to be a suite of upgrade tools. Sorting, minmaxing, selling, recording
and so on. It may also feature market searching tools.
I haven't even started writing this yet :P
Something that would minmax my inventory.
This could also work by taking a set of requirements and then optimizing a solution, given those requirements.
Something that could sell stuff automatically.
Something to index the market and store some stats.
This would make sure that you have the best items / listings ratio possible.
This would be done by juggling items in inventory.
Charm is going to be my math library.
I haven't started this one :P
grace will be my DB entry. The idea is that all db traffic should go
through this, not matter what. This way, revisioning and other stuff should be much
easier. It will also remove the possibility of messing up.
I'm not sure if this is a good idea or not, considering the latency on even a single db call. I will have to examine this closly later.
Haven't started on this one.
I need to integrate this into other scripts. This will have to happen over time.
care is the missing console.log, but better. On creation it gives you a run_id and
an object, which you can use to store output in the db. You can set parameters like
"buffered" for buffered output before saving and more.
This logger will also have several levels, that you can filter on in each run.
Might also include timing possibilties, but this is not confirmed. It will also be able to check if it is being called as a scriptor or not.
Haven't even started this.
risky is a dream. A dream about writing a RISC-V emulator in js. Things I want to add to it:
-
128-bit support
-
All standard extensions.
-
Ability to call scriptors.