API/Server Changes required for the revamping of the syncshell structure #5

New Issue

cake · 2025-09-15T04:43:09Z

cake commented

2025-09-15 04:43:09 +00:00

Lightless syncshells are very barebones now with storing information; we don't have that much information about it, and want to store more.

NEW IN DATABASE

We should be able to add more information about the syncshells, like Description and an Avatar/Icon, while joining the syncshell with some information about the syncshell, if the owner wants to have this all.

Defaulted to an empty string and no data stored; only add a new row whenever there is a filled field. Will be a separate new table for the database called group_details with fields GID, Description - string, Tags - string, Logo (Base64 encoded, max 256x256. png) - string.

CHANGES OF DATABASE

We should also include creation_date on the syncshell, and for each member, I want to have a joined_by date for users who joined the syncshell. We should be adding an instanceId for binding the syncshell to a plot/instance for showing a syncshell when entering the plot. Also, we should add another two fields for the auto-pruning of the syncshells, which should be a date and the number of days.

Defaulted to the date when this feature will be created/implemented in the server; we will not be guessing when the syncshell is created or when the user has joined the syncshell. Should add an boolean if they joined from finder. Modification on the current table group, group_user

This will be the changes required for the database/api and will require have new endpoint to be accessed.

Lightless syncshells are very barebones now with storing information; we don't have that much information about it, and want to store more. # NEW IN DATABASE We should be able to add more information about the syncshells, like Description and an Avatar/Icon, while joining the syncshell with some information about the syncshell, if the owner wants to have this all. - Defaulted to an empty string and no data stored; only add a new row whenever there is a filled field. Will be a separate new table for the database called group_details with fields GID, Description - string, Tags - string, Logo (Base64 encoded, max 256x256. png) - string. # CHANGES OF DATABASE We should also include creation_date on the syncshell, and for each member, I want to have a joined_by date for users who joined the syncshell. We should be adding an instanceId for binding the syncshell to a plot/instance for showing a syncshell when entering the plot. Also, we should add another two fields for the auto-pruning of the syncshells, which should be a date and the number of days. - Defaulted to the date when this feature will be created/implemented in the server; we will not be guessing when the syncshell is created or when the user has joined the syncshell. Should add an boolean if they joined from finder. Modification on the current table group, group_user This will be the changes required for the database/api and will require have new endpoint to be accessed.

cake self-assigned this 2025-09-15 04:43:09 +00:00

cake added this to the Syncshell Revamp project 2025-09-15 04:43:09 +00:00

cake moved this to Done in Syncshell Revamp on 2025-10-05 14:42:50 +00:00

zura commented

2025-10-08 17:54:08 +00:00

The ability to set tags so people can filter for specific criteria in the shell finder

No custom tags, just a list of tags to choose from.

Such as "Venue"

Then peopl can filter on Venue.

Or if you want to be more specific "Nightclub"

Same idea as the housing placards i guess.

Having the list of tags be pulled from the server is nice cuz then we can easily remove/ add on demand without pushing client updates.

The ability to set tags so people can filter for specific criteria in the shell finder No custom tags, just a list of tags to choose from. Such as "Venue" Then peopl can filter on Venue. Or if you want to be more specific "Nightclub" Same idea as the housing placards i guess. Having the list of tags be pulled from the server is nice cuz then we can easily remove/ add on demand without pushing client updates.

zura commented

2025-10-09 23:24:55 +00:00

Syncshell Profiles:

Let NSFW shells mark themselves as NSFW
In Shellfinder add a toggle "Show Shells marked as NSFW", hide them by default

Syncshell Profiles: Let NSFW shells mark themselves as NSFW In Shellfinder add a toggle "Show Shells marked as NSFW", hide them by default

cake commented

2025-10-15 02:24:18 +00:00

Syncshell Profiles:

Let NSFW shells mark themselves as NSFW
In Shellfinder add a toggle "Show Shells marked as NSFW", hide them by default

NSFW will be added inside the profiles, I forgot about that part.

> Syncshell Profiles: > > Let NSFW shells mark themselves as NSFW > In Shellfinder add a toggle "Show Shells marked as NSFW", hide them by default NSFW will be added inside the profiles, I forgot about that part.

cake commented

2025-10-28 17:30:30 +00:00

Everything has been added for Syncshell profiles. will continue this issue for the other items that haven't been added yet, like Auto-kick features, are require extra columns in the table for the syncshell to store the number of days it will be when people need to be kicked. Join/creation date has been added.

Hotfixes been added for now to fix all functioniality on Profiles: #25, #24 and are on Production running.

Everything has been added for Syncshell profiles. will continue this issue for the other items that haven't been added yet, like Auto-kick features, are require extra columns in the table for the syncshell to store the number of days it will be when people need to be kicked. Join/creation date has been added. Hotfixes been added for now to fix all functioniality on Profiles: #25, #24 and are on Production running.

zura closed this issue

2025-12-31 06:26:58 +00:00

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Lightless-Sync/LightlessServer#5