A game by Core-Series
Apr 16 2024
ShadeCores will officially launch on April 24 at 17:00 CEST
Mar 14 2024
Website of ShadeCores is being prepared to become public sometime during March 14.
Jan 26 2024
ShadeCores private test-phase will start today there select people with invites will be able to login and test out the game.
Changelog
<< Back to FAQ
Features -Floor saving system
Views: 145
A world map that is affected by players and their actions is a receipt for a more alive world map!
affections that last past the server-saves!
ShadeCores are running with a map-saving system that allow the map to save certain edits done by players.
The edits can almost be anything from items added to certain places, to open doors, wall torches that's lit or not, items hiding in boxes, book cases or even unexpected containers invisible to the naked eye.
You could be placing an item on the map right before a server-save.
To find it still being there when you login after the server-save!
Now for the technical stuffs
In CipSoft's there's similar systems, however they're somewhat handicapped, with certain places that doesn't reset until updates which back in the day meant that some areas could get trashed and stay trashed for up to half a year before being cleaned up.
In ShadeCores we designed the system little differently, to make it more alive and more compliant with updates/changes and staying fluid with how the game and players act out.
Same as CipSoft's, we too have "no-save zones", zones that always refresh the map upon a server-save.
In cities within city walls or limits.
However, we have a system that refresh each tile if nothing have modified it for 3 days, meaning that forgotten stuff will be refreshed automatically and the game will "auto-clean" itself over time.
This allow us to use as little "no-save zones" as possible, making sure that big parts of the map can save items and stay "alive" without being reset on daily basis.
This system is also designed to grant us ability to launch updates and map edits, without the need of refreshing the whole map, but the game will itself detect if there's been an update, and if it's necessary to refresh the area or not. (maybe the tiles in question was deleted, or maybe the area have become a lake suddenly).
in CipSoft's, large parts of the world is covered in "no-save zones", including almost entire Rookgaard island.
In ShadeCores, thanks to the 3-days timeout to refresh if no interactions have happened, we don't need much more than having cities covered with no-save zones, with exception of a few areas that may need a daily reset due to the nature of the area, like some quests or places that's not meant to stay open/closed for days.
affections that last past the server-saves!
ShadeCores are running with a map-saving system that allow the map to save certain edits done by players.
The edits can almost be anything from items added to certain places, to open doors, wall torches that's lit or not, items hiding in boxes, book cases or even unexpected containers invisible to the naked eye.
To find it still being there when you login after the server-save!
Now for the technical stuffs
In CipSoft's there's similar systems, however they're somewhat handicapped, with certain places that doesn't reset until updates which back in the day meant that some areas could get trashed and stay trashed for up to half a year before being cleaned up.
In ShadeCores we designed the system little differently, to make it more alive and more compliant with updates/changes and staying fluid with how the game and players act out.
Same as CipSoft's, we too have "no-save zones", zones that always refresh the map upon a server-save.
In cities within city walls or limits.
However, we have a system that refresh each tile if nothing have modified it for 3 days, meaning that forgotten stuff will be refreshed automatically and the game will "auto-clean" itself over time.
This allow us to use as little "no-save zones" as possible, making sure that big parts of the map can save items and stay "alive" without being reset on daily basis.
This system is also designed to grant us ability to launch updates and map edits, without the need of refreshing the whole map, but the game will itself detect if there's been an update, and if it's necessary to refresh the area or not. (maybe the tiles in question was deleted, or maybe the area have become a lake suddenly).
in CipSoft's, large parts of the world is covered in "no-save zones", including almost entire Rookgaard island.
In ShadeCores, thanks to the 3-days timeout to refresh if no interactions have happened, we don't need much more than having cities covered with no-save zones, with exception of a few areas that may need a daily reset due to the nature of the area, like some quests or places that's not meant to stay open/closed for days.
