@EMPLOYED STAFF TOOL
We made another update to the @employed tool, so that it has some colors so that certain information is easier to discern for GMs at a glance.
We made another update to the @employed tool, so that it has some colors so that certain information is easier to discern for GMs at a glance.
There was a bug when you attempted to choke out robots. This has been resolved and returned to the original intended behavior.
It is no longer possible to perform an install on a disconnected player. This is to comply to the no screwing around with sleepers policy that we have, and after discussion between staff. Installs with NPCs are not touched.
This admin-facing verb now asks if the job is corporate of service.
I did some clean up on the code for the ambient witnesses for the WJF. We had two delays, now it has one. Shouldn't have any dramatic changes for players, but for coders the code is more clean.
We have improved the logic behind the delay in WJF report response to crimes, taking into account factors such as the population in the area of the crime and also adding a layer of randomness to the amount of time an emergency call would take to be reported.
It shouldn't be vastly different from what it was before, but there will be cases where it feels either slower or faster.
The 25,000U e-memory were already created in the past, but not available. We have made it available, alongside the newly-created 5K and 10K e-memories.
We have made it so that photos now take up 25,000U. They were previously taking up a whole lot of space and it was impossible to store more than 2 in an e-note.
This new file size should be better for this kind of stuff.
Please report any issues!
This is mostly a coder-facing system which allows one to check the permissions of the user for different operations through In-Game logic. We pass strings like "rwm" (read, write, manage) and it determines if the user has the appropriate permissions. This is useful if we want to expand on the system of permissions in the future. Also allows for cascading logic between children of the e-enote if any in the future.
Data Vaults serve as devices with an e-memory attached where information can be stored (all the information an e-note allows), with different permissions for users to use and manage it. They can be used as repositories for data for corporations and groups, boards, etcetera. Right now, we are still discussing the places where we will implement these new types.
With Data Vaults, groups of characters have write permission, while anyone can read it. They are pretty much public e-memories with the permission system modified.
They inherit from the e-note filesystem and the commands from the e-note for use.
Admin can define vault managers which have write and manage permissions on these, depending on the board.
We have separated delete permissions for e-notes and data vaults. By default, managers can't delete files unless they are admin. This should momentarily remove any worries of griefing while we code a more flexible solution.
This now allows super-managers to add permissions for any person and also for individual characters, effectively allowing any combination of data vaults. This is a major change, since it allows admin to decide that a data vault can by default be read and written by anyone, determine who can read, delete, manage data vaults, etc. It basically allows any combination of permissions!
We have enabled work keys as basis for permissions. This means that terminal factions can be labelled for special permissions in specific data vaults. For example, if a bar has a terminal, it has a work key and it means that we can set all employees of that terminal to have write permissions in a specific data vault.
This is not SIC keys. These are values that help us determine who belongs to what group or sub-group within a faction.
We have begun porting some functions to a more modular filesystem arrangement. In this case, we separated the function that recognizes a filesystem in e-notes, and made it so that it can take an e-note or an e-memory and return the filesystem. This should help adhere the system to follow modularity practices, allowing us to expand the system and implement the filesystem in more systems in the future if we wanted to, rather than duplicate code.
We had this verb for the e-note; it has now been ported to a new general-purpose utilities package, a change that should help make the system more modular and without duplicate code.
The logic for the size of a photograph has been updated into a generic utils package. Previously, we had to update two different locations to determine this. This is no longer the case.
Moved most of the logic for converting a photo to a file to a compartmentalized verb, which means that it should be much simpler to extend logic that converts photographs into files in the future, and also separates concerns.
It is now possible to scan a wide arrangement of documents like flyers, newspapers and resumes with an e-note scanner. You can just scan them with the e-note like you did with the photos before and it will scan into a document. Let us know how this works and if there's anything to improve in the feedback thread.
This change is at the apex of all the previous changes to the backend of how scanning stuff works with e-notes, which has been made more flexible.
Previously, scanning didn't check permissions as everything else. In theory, this means that someone could've scanned a document with a scanner attached to the data-vault, to bypass write permissions. No longer the case.
Letters are different from the aforementioned documents, and they operate with a different system as well. We have added logic to scan letters with e-note e-scanners now.
To allow for GMs to monitor data vaults (such as in the case of using them for reports or what ever), we have created a variable that determines if data vaults are being monitored. If they are, they will be sent as part of the GM mailing list.
There was an issue preventing our GMs from properly authorizing players on these. It has been resolved.
We have enabled a flag that determines if a vault will create a note on the admin-side. This will allow for vaults that can be used for reports and other things.
We have enabled a flag that determines if a vault will create a note on the admin-side. This will allow for vaults that can be used for reports and other things.
I created a new property on e-notes (and all of its subchilds, like data vaults) which will determine the extensions and modes that it allows. This should allow for extending the functionality in the children without having to duplicate code.
I created a new property on e-notes (and all of its subchilds, like data vaults) which will determine the extensions and modes that it allows. This should allow for extending the functionality in the children without having to duplicate code.
When you opened images on e-notes, it would show the screen displaying the image twice. This has been removed.
A new property has been added that determines what is displayed before rendering the content on an e-note and its derivatives. By default this is the "The PRI e-note 7 displays:" text that shows at the top. For derivatives, this can now be changed to offer a customized and immersive experience.
Scanning now adheres to allowed extensions and modes. Therefore, it can only scan things that are allowed on the device.
You now have the cp command which allows you to copy files in e-notes and other devices. This should also allow you to move files from different e-memories with devices that allow more than one e-memory!
Previously, after the game told you you were done showering / drying, it would still take 5 additional seconds. Now, when it tells you, you will be done with it.
An installable digital frame that allows you to display photographs on it. It uses the same filesystem as e-notes and allows you to browse files with the same syntax of e-notes to choose which image to open. You can only open images, nothing else. Upon looking at it, you can see the image just like you would with a pinned photograph.
This object is in theory a children of the data vaults, but heavily modified for such a purpose.
While we had analysis for the nature of the wounds, we have added a new check for manner of death. This is a superficial analysis of the state of the corpse to determine not only what wounds the person had on them, but also the manner in which the corpse finally lost their life.
Following along with the changes to the scanner, you can now scan graffiti with your e-note's scanner.
(Edited by Neon at 10:51 pm on 6/22/2023)
You can now search existing open, public bugs to see if there is an existing bug report before filing your @bug.
For example:
* @bugs progia
* @bugs sniper
