jdevnull
jdevnull
Colus' statement at [https://discord.com/channels/564618629467996170/564621949842751508/1217174615449927842](url) that trap doors should drop you directly into the target node makes sense to me, so here's the code for it. After [https://discord.com/channels/564618629467996170/1216675006164242432](url), what I'm thinking...
In newmatrix.cpp, `matrix_update()` starts from `matrix[1]`, but db.cpp functions start from `matrix[0]`. Is `matrix[0]` an actual host?
Notes on current PR: 1. When attempting to logon to a local subsystem that has a trapdoor, the original code immediately sets the host for the system test to the...
Well, the code chunks seem to do what I want them to do when I tested them separately, but I haven't tested it integrated into the mud. Difficulty is that...
Missed some interactions. When attempting to logon to a subsystem, the code only checks the ACCESS subsystem for encryption instead of where the trap door actually is.
Alright, revised how I approached handling trap doors, so here's the current summary of what this PR does: 1. Each host now has a linked list of entrances. If host...
And a few more changes: 6. Corrected calculation of remaining hacking pool when resisting an attack (esp. so that it doesn't look like a cold ASIST is using pool dice)....
Yeah, this was what I was trying to describe in part 3 of the PR description. That said, we don't actually need to clone the entrance list, since they're going...
I don't believe this is needed, so closing the PR.