SkyFrost.Base.Models Metadata about an uploaded asset chunk Index of the chunk of the whole asset. 0 indexed Opaque key representing this chunk, identifying it appropriately with given asset backend. E.g. in case of Cloudflare this will be the ETag of given part The signature of the asset, uniquely identifying the asset that is being uploaded. This is a hash of given asset. Identifier of the variant of this asset (if a variant is being uploaded) Unique ID of the upload job Owner of the upload - this is the user/group who is responsible for uploading this asset. Typically this is the one who upserted a record that requires upload of this asset The size of this entire asset Size of each chunk in bytes (except last, which can be smaller) Number of chunks that this upload is composed of Current state of this upload Opaque key identifying the upload with the target system. E.g. in case of CloudFlare, this is the UploadId generated by the S3 API Api endpoint where to upload the individual chunks Indicates that the upload is direct in a single part (no chunks) and it's technically completed the moment the upload of the file finishes - the asset is ready to use right away. This allows for speedier uploads with smaller files, which also use fewer requests. Maximum number of parallel uploads that are supported/allowed List of all the uploaded chunks of the asset. ID that uniquely identifies this configuration The owner of the given configuration. Either User or Group. Configuration file for the build itself DB signature of the image file for a custom splashscreen Unity Engine with the Mono runtime Unity Engine with the Mono runtime and profiling and debugging enabled Unity Engine compiled with IL2CPP using the Release Configuration Unity Engine compiled with IL2CPP using the Master Configuration Headless build using the older .NET Framework runtime Headless build using the modern .NET runtime (.NET Core, .NET 5 and so on...) Unity SDK corresponding to this build Specific type of the build of the product Represents an unique build of our application. This doesn't contain any actual files of given application or platform specific version, but rather is a summary of changes done in this release. To get actual executables or files related to this build, the BuildVariant for specific application is used. The application this build is of. This allows us to use the same build system for multiple applications that do not update in sync Version number of the given build. This uniquely identifies the build and generally corresponds to the UTC time it was built on. This is used for the old build versioning scheme before we switched to the date based one Any description/summary of this build. This is optional too, mostly for builds that are planned to become public releases, but can be used for internal notes and goals of this build as well. Optional associated graphic with this build. Can be used for main release builds for promoting them and giving them a bit more flair in the launcher when browsing List of changes in this build relative to the previous one in given branch. List of any known issues with this build. Mostly for informative purposes. Any other notes for this build, if applicable Unique name of the branch that this build corresponds to. Branches are typically used for features and changes that are developed in parallel and later merged into the main one. Each branch has its own history of changes and separates those from mixing with changes being done in parallel. When a branch gets merged into another one, this also allows to create a full summary of those changes. Name of the branch that got merged into this build. This is used to generate the summary of changes - e.g. if feature is being developed in parallel and then gets merged into the main one, the list of changes done on that branch is put together for the release, so it doesn't have to duplicate those again. A new functionality A change to existing functionality or behavior Performance improvement to reduce resource usage Change, bugfix or addition specifically improving the security of the platform Bugfix that corrects behavior of a feature An unique id of the change. This allows the change to be uniquely identified and referred to Description of the change. Type of the change. This is used to group the changes in release logs. This is used to mark changes that are work in progress and do not represent final state This change is specific to the branch it's one and won't be shown when the branch is merged into another. E.g. this can be used for bugfixes for in-development features - when those features are released to the main branch, it's not necessary to list all bugs that happened during the development, but they're still useful for testing within the branch. Any GitHub/Moderation/other issues that this change is based on or related to Any users who contributed to this change in the build with actual code changes and implementations Any users based on whose reports and feedback was this change made List of build platforms that this change affects. E.g. bugfixes that are Windows/Linux/Android specific If the list is missing (null or empty), the change affects any platform. Any platforms from which this change is excluded. This can be used for features that would conflict with the rules/guidelines of given platform, so when the changelog is pushed there, the changes are not included with it. Doesn't have a valid reference References a specific version number. It won't update to another one until it's changed Uses build referenced by another channel. Allows to automatically track another channel with custom configuration Always uses the latest build in a given branch Doesn't have a valid reference Refers to a specific configuration by its unique ID Tracks another channel's configuration Unique ID of the channel. Each channel gets assigned a unique ID that can be used to refer to it The owner of the given channel. Either User or Group. The application this channel is for. This specifies how does this channel reference which build to use This is the unique identifier of which build to use. Format is dependent on the reference type This specifies the format the the ConfigurationId, determining how it's referenced. This is unique identifier of the configuration to use for this channel. Configuration can change the default settings, auto-init worlds, dash and other aspects of the App experience to create customized builds. It's dependent on the configuration reference type Signature (hash) of the file. Used for the DB lookup. Null if the entry represents a folder. Size of given file in bytes. Path of given file / folder in the installed build. Includes filename. The given DB asset will be placed at this location. An additional note for a build. Can be a known issue or just any note that doesn't fit other criteria Id that uniquely identifies this node and allows it to be referenced from other systems Actual content of the note Printable username of given user UserID Discord Handle GitHub Username The build doesn't exist and won't be built. The build is scheduled to be built, but isn't picked up by the system yet This build is currently being built This build was sucessfullly built Failed to build, e.g. due to an error in the build process Uniquely identifying id of the variant. This should be the same for variants that represent identical build variants (same platform, version and so on) Current status of the build Installable files representing this build Computes a unique ID string that identifies this variant IMPORTANT!!! Make sure that new additions to the data model will preserve the ID string for the old versions. that way existing build variants do not suddenly change their ID Descriptor identifying the properties and parameters for this particular variant Version number that this variant corresponds to. Version numbers uniquely identify builds. Same as version number, but in string form Specific platform that this build will run on Gets a unique identifier that for this particular variant. The descriptor can be built from this ID string The issue is only referenced, but no action is taken The issue is closed by the change referencing it. This is typically when the issue is resolved The issue is updated, but kept open. This can be used when there's multiple changes needed to fully resolve issue This is when we're not sure whether the change resolves the issue and requires the submitting user to check The number of the issue in given issue system The issue/ticket tracking system that this corresponds to Any action to be taken for the given issue This contains basic metadata of the session without any private information, except for the URL's which can be used to resolve the SessionID This data is never directly shared and only used to compute session statistics. ID of this session ID of the user hosting this session Number of users joined to this session, including active and inactive Number of users in the session who are actually active (present) ID of the user session of the user hosting this session Access level of this session Indicates if this session is hidden from listing List of the URLs that this session is available at. This is necessary to be able to resolve SessionID into the URL's This represents a comment posted by user to any applicable entity in the product. Allowing to create discussions for worlds, items, user/group profiles, builds (and individual features), posts and other stuff. The owner of this comment is the entity that the comment is posted on. This can be nearly anything: - Record (using composite OwnerId:RecordId) - User (their profile) - Group (their profile) - Post - Build - Build Change Unique ID identifying the comment Timestamp of when the comment was originally posted UserID of the user who posted this comment. Optional ID of a comment that this comment is a reply to. Null otherwise Actual Content of this comment Default preference Users > Universe's > Platform > Fallback Prefer the universe's entities/facets over the user's Universe's > Users > Platform > Fallback Only load the Universe's Entities/Facets, Do not allow the user's to load or the platform's to load. Universe's > Fallback Advanced options to configure a Client. These options should be specified/stored in a JSON file and passed on startup with the -config command line argument. JSONSchema for this file, used for external users to validate and test this file. A list of World URLs which can be opened in Unsafe mode with the "OpenUnsafe" command line argument Configuration options for the controllers of this App Client. This will later be moved into in-game settings, as it doesn't make sanse as per-build configuration. Optionally, specifies which universe this Headless Server will be in. Optionally, specifies the relay connection preference. Controls the loading of Facets and EntityInterfaces, when in a universe. When in a universe controls the order of loading for EntityInterfaces, it tries each possible source in order moving on if the prior one fails. See for the exact order of loading. When true and within a valid universe, will use the Universe's Dash Facets instead of the user's. When true, only uses the public universe dash and not the private one, useful in more public demonstration universes, where logging in is optional. See for more information. When true and within a valid Universe, will overide Cloud and Local home loading to use a universe's versions. The homes loaded with this setting, will be read-only and they will not affect your non-universe homes. Specifies proxy settings to be utilized. Can override whether all local IPs are announced as part of session data or not. Announcing all local IP's is particularly helpful for larger corporate/university networks with flat hierarchy. On those networks the LAN broadcast might not reach the entire network, therefore local IP's won't be discovered by all clients. If the client simply includes all the known IP's with the session data, this allows direct connections within the network, which helps improve connectivity. By default, this is implicitly enabled when UniverseId is set - this is used as an indicator that Resonite is being used within some kind of organization. By explicitly setting this to false, this behavior can be disabled. Alternatively this can also be set to true when there's no UniverseId, which will enable this behavior. This allows overriding whether any hosted sessions will be broadcasted on the LAN via UDP broadcast. LAN broadcasting allows clients on the same network to discover local sessions and connected to them, without requiring to go through other mechanisms. However on some networks this might cause a lot of network noise, so this can be used to disable this. This setting will override all other settings - e.g. user settings. When set to true, the intro tutorial sequence will always be skipped. This skips the initial setup as well as the tutorial world that user has to go through on the first launch. This setting will override all other conditions and ensure that the tutorial is always skipped. When set to true, the cloud home will never be automatically loaded after logging in. This overrides any other settings and can be used to ensure that this client will never load the cloud home on its own. A list of worlds/sessions to start/create when this App Client Starts. A list of rules/ids/urls to use to automatically join sessions when this client starts. When true, will hide most standard UI from the user. This option is usually used in combination with or to enable for Kiosk/Dedicated experiences that don't need our UI Disables, the Desktop viewing functionality. Does not disable Desktop Input/Desktop Mode. Configures the available login methods for the App. It is recommended to ommit this from your configuration files unless you really need it. It is used in rare circumstances to control the login flow even more. A list of paths which the App can browse in the FileBrowser. Set to an empty array to disable the FileBrowser. When set, overrides VoiceSettings.MutePersistence, and mutes your microphone at startup. It is recommended to use the settings system over this in most cases. But this can be useful in corporate scenarios, where corporate security wants to enforce this as a policy. When set, prevents the checking of and the registering of Application protocols within the registry. We recommend leaving this off. Registering Application protocols on your computer makes it easy to join and share sessions with users. When true, ALL platform interfaces won't be initialized This is mostly useful for standalone utilities, like the standard asset uploader, which doesn't need to interface with any platform interfaces. We do not recommend enabling this option for regular app use.

When enabled it will prevent the following features from working: Clipboard Based Operations Screenshot Operations Any Steam Functionality Any Discord Functionality If privacy is your goal, then see A list of Platform Interfaces which should be disallowed by this App. Used primarily for Privacy related reasons, you can use this to completely disable Discord and Steam support. For example: ["Discord", "Steam"] would disable both. For the Allowlist version of this see To disable ALL interfaces without using any lists While using both options, is possible, It is not recommended due to potential confusion. A list of Platform Interfaces which should be allowed by this App. Used primarily for Privacy related reasons, you can use this to explicitly opt-in to new PlatformInterface related functionality. For example: ["Windows"] would just keep Clipboard related functionality enabled and disallow any new platform interfaces that might be added in the future. For the Blocklist version of this see . To disable ALL interfaces you may use []. To disable ALL interfaces without using any lists . While using both options, is possible, It is not recommended due to potential confusion Configuration options for a Client's input devices. Adds a deadzone to the triggers of all controllers used by this client. Adds a deadzone to the joysticks of all controllers used by this client. LNL Specific Configuration for this copy of Resonite Whether to autodetect proxy settings using Internet Explorer's settings. Defaults to false. Whether to bypass the proxy on local domains. Defaults to true. List of domains to bypass the proxy with. HTTP/S proxy to use for all web requests. Determines the source of the proxy server's credentials. Valid options are: DefaultSystemCache NetworkCache UsernamePassword Defaults to the system cache. Proxy server's username. Only used with UsernamePassword credential stores. Proxy server's password. Only used with UsernamePassword credential stores. Is this proxy configuration valid? For now this is absic, but could be more complex in the future. Should we test this proxy for you? Set to true if is set. Is using this proxy required/mandatory for Resonite? True if this configuration is compatible with our AutoDetect feature This may become more complex in future, it original skipped AutoDetecting a proxy if an address and port were supplied, but this broke a client. Configuration for a session which should be automatically joined by this client. This uses a number of checks and searches to find a matching session. The URL property is used first if specified which also ignores all other filters. A direct session URL to join. When specified all other checks will be ignored. { "url": "ever-session:///S-U-ProbablePrime:CheeseLand" } A session ID to join, use "*" to use the other rules to find a session to join. { "sessionId":"S-U-ProbablePrime:CheeseLand" } When set to true, will only join LAN sessions. When set to true, will only join Headless sessions. When set, will only join sessions within this Universe. When set to true, it will automatically focus this session if it is found. When set to true, will wait for an active Resonite User session before trying this auto-start session Use this in cases where the auto-start session, might only be accessible after logging in. Used by Resonite to ensure that we only process this once. Save this world to the Local Machine of the Headless Server. Save this world to the cloud user this Headless Server is logged into. These options are used to configure a startup world from a JSON configuration file. There are two ways that these are used: Startup Configuration Files Used in: autoStartWorlds within the Startup Configuration Files Headless Configuration Files Used in: startWorlds within the Headless Configuration Files. Do see as there are extra options. When set to false, this will disable this world entry from starting. This allows you to keep a world entry in your configuration file, while also disabling it. It allows for easy configuration swapping. The name of the session as shown in the World/Session Browser An optional custom session id for this session. This custom session id must be in the format <userID>:<customText>: userID This must be the userid of the account that is hosting this session. It cannot be anyone elses. custom text customText can only contain alphanumeric characters, "-" (dash) and "_" (underscore) but can be anything you'd like. The ID it is always prefixed by "S-" e.g. S-U-ProbablePrime:Cheese-Land. It can be used with regular session connection strings and nodes. U-ProbablePrime:Cheese-Land An optional description of this session, displayed within the world/session browser. The maximum number of users, allowed to join this session. This defaults to 32. The Access Level for this session please see for more information. Determines whether custom join verifier should be enabled in this session Determines if this session should be hidden from the world/session browser or not. A list of tags, to assist with searching or discovering sessions. cheese,world,game Determines if this session is friendly for mobile/quest users. When provided with a world URL this will load this world for the session. You cannot use this with resrec:///U-ProbablePrime/R-1234-1234-1234 When provided and valid, this will load the specified world preset into the session. The options here, match the options you have when you start a normal session within the App. You cannot use this with . Preset Name Preset Description Grid A flat grid plane world with a standard skybox Platform A standard, "Earth-Like" skybox with a white cylinder platform to stand on. Blank Empty world with minimal contents. Overrides the world id for this session allowing it to be grouped and displayed with other sessions with this world id. Use this if you're hosting a specialized version of a public world, but you still want it to be grouped with the normal ones (and prevent people from starting sessions of the specialized one). It is in the form of a record id. So see for more information on formatting. "overrideCorrespondingWorldId": { "recordId" : "R-xyz", "ownerId" : "U-Owner/G-Owner" } Optional, If specified it will force this session to run on a specific network port. If specified ResoniteLink will be enabled for this world at startup. Optional, If specified it will force ResoniteLink to run on a specific network port. Optional, If specified will keep the original roles as saved in the world. When provided with a list of username and permission pairs it will grant those users the listed permissions when they join. Permissions are the standard permission sets: "Admin", "Builder", "Moderator", "Guest", "Spectator". ... "defaultUserRoles":[ { "User": "Admin" } ] ... An optional name of a cloud variable to use to determine the role of this user. See our wiki article for more information. An optional name of a cloud variable to use to determine if this user is allowed in the session. See our wiki article for more information. An optional name of a cloud variable to use to determine if this user is denied access to the session. See our wiki article for more information. An optional name of a cloud variable to use to determine if this user is denied access to the session. See our wiki article for more information. The name of a cloud variable whose value will be used, When a user is denied access by this message will be displayed to them if present. See our wiki article for more information. Configures the number of minutes that a user can be away(shelled out) from a world before they are kicked. Setting this to -1 disables this option. Provides a list of Parent Session Ids for this session. See our wiki for more info. Users within this list will automatically be invited to this world when it starts. ... "autoInviteUsernames": [ ] ... When receiving an invite request, headless will forward it to all users within this list to handle. ... "inviteRequestHandlerUsernames": [ ] ... An automatic message sent to the users on the list along with their invite. Controls who saves this world when it is saved. See, for more information. Headless only If this is set(>0) and the world is empty, it will restart regularly using the value to determine the number of seconds between restarts. Headless only If this is set(>0), it will restart regularly using the value to determine the number of seconds between restarts. Headless only If set to true will save this world on exit. If this is set(>0), it will automatically save using the value to determine the number of seconds between saves. Headless only If set to true, will prevent an empty(or filled with away users) world from running a full update cycle regularily. Headless only When set to true, will wait for an active Resonite User session before loading this auto-start world. Use this in cases where the auto-start world, might be owned by a particular user or group and so not normally accessible without a user being logged in. Used by Resonite to ensure that we only process this once. This class represets a configuration file that should be automatically installed at a location. This allow for registration/login to add additional configuration files relevant to the particular user. Relative path at which the file should be installed The content of the file - the actual configuration itself The unique ID of the Discord user. Discord's documentation for more details. The ID of the owner on this installation of the platform for this customer. How many groups is the user allowed to create Unique id of this entity (for a given OwnerId). Owner of this entity. Typically user or a group The funding amount of this event in the specified currency The currency that the amount is in Timestamp of when the funding event was stored into database. This is usually after the funding event itself has occured and is for bookeeping reasons Time when the funding event starts - this is usually from a 3rd party source, when the user pays the support service This is when this funding event expires (typically a month) and along with it all the granted perks Whether the funding event has been manually invalidated (should always be considered expired) The entitlements that this funding event grants during its duration The name of the tier (if available) of the funding event Any additional note from the source, mostly useful for bookeeping and debugging Timestamp when this was last computed These are aggregate numbers of all of the services Patreon funding stats Stripe funding stats These numbers are calculated only from the currently active support at the time of calculation of these stats This includes all of the valid funding events over the whole history, serving as a total amount of support that was received Stats for all of the tiers Individual stats for each tier The sum of all the funds in USD - this is based on the tier Average amount of support in USD over all the events The sum of all of these in each of the currencies Total number of unique supporters The external timestamp of when the payment occured The number of cents that the tier is at at the time of the funding event Patreon specific ID of the user that is source of this event Patreon specific ID of the tier that this event stemmed from The unique ID of Stripe's Customer object that is associated with all other Stripe records for the user. See Stripe's documentation for more details. Whether the Stripe Customer is part of the live dataset (not for test mode). See Stripe's documentation for more details. The ID of the owner on this installation of the platform for this customer. The ID of the Stripe Customer object that this funding event was created for. A customer can technically have multiple subscriptions, but Stripe allows us to limit them to one per customer. See Stripe's documentation for more details. The ID of the Stripe Subscription object that this funding event was created for. A single subscription lasts for as long as the customer continues making payments on it, and has multiple invoices created as a result of it. See Stripe's documentation for more details. The ID of the Stripe Invoice object that this funding event was created for. Multiple invoices exist over time per subscription, but each one should always be tied to a unique funding event. Generally, a single invoice exists for each billing period. See Stripe's documentation for more details. The raw supporter tier ID that the user has paid for, supplied via metadata on Stripe's Product object The ID of the Stripe Event object that this funding event was created as a response to. The event object holds all of the information that was sent to us via webhook, but is only guaranteed to be available for fetching after the fact for 30 days. This can be useful for debugging and support cases. See Stripe's documentation for more details. Whether this funding event was created as a result of a live (not test mode) Stripe event. Responding to test mode events can be useful for development, testing, and training purposes. A url to a page that provides access to Privacy Policy, Terms of Use etc. The name of the studio/company making this Platform, in short form YDMS The name of the studio/company making this Platform, in long form. Yellow Dog Man Studios Checks if a given OwnerID is the owner of this Platform Profile OwnerID to check true for owner, false for not owner Used for records that exist Outside of the inventory, such as worlds saved using "World Path" Validates a given URL to see if it matches this Platform's specification for a record uri. RecordUri to check true for a valid record uri, false for invalid Validates a given URL to see if it matches this Platform's specification for a session uri SessionUri to check true for a valid session uri, false for invalid Character limit for a record's name Character limit for a record's description Used to determine the session access level for a session. This session cannot be joined without an invite. This session can only be joined by users on the same LAN. Contacts(Friends) of the world host can join this session. Contacts(Friends) of the world host and anyone who has already joined can join this session. Users who have an account and are logged in can join this session. Anyone can join the session. Use instead. Use instead. Base quota type is only counted when there are no other quota types present Normal quota type is counted as usual and grouped This indicates that the quota source is quota shared by another user/group Unlimited storage. This is typically used for group members Opaque unique identifier of this quota source. Can be potentially used for deduplication by systems that automatically grant storage quota (e.g. based on purchase) to make sure it doesn't get double-granted How many bytes is this quota source worth When does this storage quota expire and will be removed. If null, it'll never expire. When does this storage quota activate. It will not be counted if it has no activation date. When was this quota source created. This is purely for informational and doesn't affect activation. Group that this quota source belongs to. If there are multiple sources within same group overlapping, they are not summed up, only the biggest source is used Indicates the broad category type of this quota Indicates how much can this storage be shared Display name of this quota source. This is purely for user and doesn't affect functionality Display description for this quota source. This can contain any details about how this quota source came to be. Indicates if this quota source has expired Indicates if this quota source is now active Who is the quota being shared with (another user or group). Id of the Storage isn't necessary, because that's only needed for sharing with a member of a group, which isn't possible to do, since they only have portion of the quota of the group Ratio (from 0.0 to 1.0) of the total quota to share with the target Maximum number of bytes to share with the target. When ratio is set 1.0 this allows always sharing a fixed number of bytes. How many bytes are being currently shared with the target This is computed automatically and should not be assigned. Id of the owner of this storage. If it's user, it's their UserId, same as OwnerId. If it's a group, it's the group Id, same as OwnerId If it's a group member, it's their user Id, with OwnerId being the group id Owner of this storage data. Can be user or group How many bytes are currently used. Calculated from asset usages from pinned records. How much storage does the owner have. Calculated from the quota sources and subtracted by quota shares How much storage would the owner have if none of the quota shares were in effect How much storage the owner has that's available for sharing with other users Indicates how many bytes of the full storage are currently being shared Sources of the quota bytes. These are actually authoritative sources and the QuotaBytes is always calculated from these. Who is the owner's quota shared with. This allows sharing own storage quota with others Base64 encoded RSA SHA-256 signature, which can be used to verify the Id and Timestamp of this thumbnail info for upload on the endpoint (Cloudflare) without having to contact the Azure API for the unsigned data. This is the URL where the thumbnail should be uploaded to and where it can be later fetched from This is the string that the Signature will be generated on. These parameters are sensitive. Id determines the name of the thumbnail (which is generated to be unique by the API) and the timestamp is used to limit scope for how long this upload is valid, to ensure that users can't just request a thumbnail and upload it days later, after it already would've been deleted. Those two parameters must not change. Others the upload endpoint (Cloudflare) won't care about Binary version of the SignatureString for signing. for the signed version. This signs this thumbnail information with a private key, allowing the Id and Timestamp to be verified by the Cloudflare endpoint on upload, without having to contact the Azure API The primary group for this universe. Replaces Platform group in Universe specific features. The general group that the information is being broadcasted to List of ID's to which the information should be broadcasted to, when applicable. This is only valid for certain types of groups User's password that is being used to login into the account or to set new password Recovery code which can be used to bypass the password requirement and set new password Use a session token to login Defines a badge that can be displayed on the user's name and on their profile Unique ID (per Owner) of the badge definition. This ID is used alongside OwnerId to reference the badge Owner of this badge definition. This can be user or a group Indicates if this badge is enabled. Disabled badges will not show on user's profile or their nameplate, even if included. This adds a mechanism that allows globally disabling badges while preserving their data - e.g. badges disabled due to Patreon subscription expiring, or badges that end up deprecated. URL for the asset that represents the badge. This will depend on the type of badge. For Static2D, this is the URL of the texture Type of the badge asset For Static2D badges. This will make the badge use point filtering, which is important for pixel art Name of this badge Description of this badge List of badges that the user has currently on display Basic status information for a registration. This is used to communicate the status of a registration with a client after it has submitted a registration request since they're queued. Unique identifier for the entity being registered Secret token for the registration (to check status) Current state of the registration Error encountered while processing the registration, if any. This should be populated when State is . Whether is Whether is Whether is or Potential states of a registration The registration is waiting to be processed The registration is being processed The registration was completed successfully The registration was aborted due to an error and will not be reattempted Patreon subscription support metadata Stripe subscription support metadata Subscription-based support metadata Whether the user currently has an active subscription Total number of months the user has been supporting Total monetary value of the user's support, in cents Most recent tier value, in cents Highest tier value the user ever supported for, in cents Lowest tier value the user ever supported for, in cents First time the user supported Last time the user supported Whether the user has ever supported Whether the user has ever supported Sanitizes , , , and Metadata for a user's support for the project String to display for the user's account type Color to display for the user's account type Priority for the account type Is the supporter data currently active If supporter badge should be shown for this supporter Sanitizes data for API output Compares this metadata's priority to another's Value of the old credential - username, email and such When it was changed to something different Optional description of the source that led to the credential being changed Whether the user has ever supported the project with a subscription Checks whether the user has any supporter metadata of a specific type and optionally matching a given predicate Represents an individual session for a user who is logged in. Lasts until the Token has expired, or invalidated. User ID of the Logged In User Token for this session Timestamp for when this session and token were created Timestamp for when this session and token expire Hash of the SecretMachineId used to create this session Salt used to produce the SecretMachineId hash True, if the user has elected for this Login Session to be "Remembered" in app. Indicates that this token is bound to specific machine, meaning that the token needs to be hashed with the secret machine ID and UID, to produce raw token. URL that needs to be opened to finalize the logout. This is typically used with external authentication services Determines if the logout URL needs to be opened client side (typically opening in user's web browser) The type of login (password, OAuth, SAML 2.0 ...) that this session was created from This is incremented each time a new user session is created from another one (for RememberMe logins) On the main Universe, this is reserved for Froox. For others it might be many people. A Map of event names to User tags. This is used for the command /addeventbadge and /removeeventbadge Converts a JSON string value into an Enum Value, if any issues occur the value is set to the provided default Value. In our old infrastructure, we had some additional Enum values in some cases, during Migration to new infrastructures these were deleted, and so to properly de-serialize them for conversion or analysis we need to have a stand in to avoid Errors. Originally from: https://gist.github.com/gubenkoved/999eb73e227b7063a67a50401578c3a7?permalink_comment_id=3699666#gistcomment-3699666 As this classes "ConverterType" is null, this method will be called when there needs to be a converter created. This allows us to inject the defaultValue into the construction of the converter. Again see: https://github.com/dotnet/runtime/issues/73984 and: https://github.com/dotnet/runtime/blob/main/src/libraries/System.Text.Json/src/System/Text/Json/Serialization/Metadata/DefaultJsonTypeInfoResolver.Converters.cs#L173 Port Range represents a list of ports available to use for networking. It can be used to restrict the port usage of an application. OnStartup: var success = _portRange.Try((int port) => _client.Start(port)); if (!success) { throw new Exception("Failed to start LNL_Connection: Please check that the system has a port available. We're using: " + _portRange); } OnStop: range.Free(port); It makes no attempt to discover if other applications/processes are using a port. It will just try it anyway. Maximum value for this range Minimum value for this range The length of this range Returns each port value in the range which allows for an easy for loop. foreach (int i in range.AvailablePorts) {} gets you an automatic for loop. As under the hood this is entirely Enumerable based, it is quite efficient. Creates a new port range with a specified minimum and maximum value. minimum value for this range maximum value for this range Does the range contain this value? True if the value is within the range, false if not. Same as but also marks port as used. Next available port or 0 for no available port. Returns the next available port or 0 if there are no available ports Next available port or 0 for no available port. 0 means "any available" port, and so it is used as the fallback here as it allows. Things to continue trying to work, without this port range's involvement. Gets if a port is in use or not by this port range Port number to check true if this port is in use, false if it is not. Explicitly mark a port as used, so it doesn't appear in the range Avoid using this where possible and rely on . Its intended for scenarios where we detect that a certain port is used or unavailable for another reason such as firewalls. Marks a port that was used as free Port to free up true if the port was freed, false if it was not used to begin with. Returns a nicely formatted string detailing this range Create a new port range, from min inclusive to max inclusive. inclusive minimum port for this range. inclusive maximum port this range. For each port in this range, call the startFunction with that port. startFunction should try to use the port and then return a boolean indicating success. This method, is aimed to make things very simple for consumers but it does take away all of the control. A function that is called with each port in this port range. It should return true if it was able to use a given port. true if a port was successful used and allocated, false otherwise Creates an Iterator over which only includes elements not found in . Type of the enumerable First set, with items to return. Second set with items to exclude An enumerable that includes elements from the first set, not found in the second Produces an that includes elements from the first set that are not found in the second. Type of the Enumerable First set, with items to return Second set, with items to exclude An enumerable that includes elements from the first set, not found in the second This indicates that a given entity is sensitive and should not be printed out to logs and console