feature_wishlist - ryzom/ryzomcore GitHub Wiki
title: Feature Wishlist description: published: true date: 2023-03-01T05:20:18.894Z tags: editor: markdown dateCreated: 2022-03-11T00:17:05.862Z
Feature adds, possible stretch goals, anything.
Approved items get a black star.
Always add to the end of the list, please.
Generate the CRC32 of every filename that’s indexed by CPath, so that all filenames can be referenced as a uint32. For future usage. Or a 64-bit hash.
Object state uint32 used by client to, for example, have proper dynamic doors, playable radios, and other interactive items. // Already have this. Just need to add new AI entity types, which can be a hassle currently!!
Streaming sound source from live stream. (Optional. When playing multiple creatures with same stream, client must manage itself which item should be playing the stream to optimize bandwidth.)
Advanced NPC AI, ‘Sims style’, NPCs which act more like players, with logically generated missions for players to aid their personal goals. This includes fully autonomous NPC tribes, etc.
★ Pesistent sessions. Two methods, one loads scenarios on the fly, and shuts down the session when no more players are active inside it, after a certain timeout. The second will be provided at a monthly fee, and keeps the session alive even when no players are inside it (it will still go down during patches, or in case the server crashes, etc). (A persistent scenario with a fixed session ID would allow providing support for proper persistent player missions, etcetera!!!)
★ Allow game masters to add teleportation points from one session directly into another, as well as allow the creation of hidden sessions which can be access through this method.
(WOULD BE VERY NICE) Persistent storage of ring scenario parameters (using a specific component)! (Part of persistent sessions)
Custom loading screen for your scenario.
New ingame GUI style
★ Basic lobby (mainland), to be further enhanced down the road. Basically a sort of village that we build and add new content to
★ Separate body colour from race. Character creation basically select base body (currently HOM, HOF), and then select appropriate face type (HOM_FY, HOM_ZO, etc), allowing for further new body types. (Optionally also use default skel instead of rescaled race skeletons? No.)
Improve the colour palette for assets (armor, hair and skin colours)
Support for icons inside text. Similar to currently colors done by @{FFFF}, we can do @{ICO:textureFile}.
Replacement of smileys with emoticons server-side. Depending on subscription of player they can use different emoticon sets.
Runtime spawning of entities. Essentially this boils down to giving the AM sufficient rights to run user-friendly event commands.
User provided script components (as well as a sort of storefront thingy to share them). This works (the components), and I have already written a load of utility code to handle this. Only need to put in a proper method for handling user component translation (currently using an ugly hack).