Known issues: Difference between revisions
From Dragon Realm Wiki
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
** <strike>This appears to be an issue not with the advancement system, but a disparity between query_level() and the leveling system. Compare <code>call [user];query_level</code> (currently broken) with the results from <code>call /adm/daemon/level_d;level_system;/std/user#[instance_number]</code> (works fine). The majority of the code relies on the efun query_level, so it needs to be understood why query_level is returning the wrong value.</strike> | ** <strike>This appears to be an issue not with the advancement system, but a disparity between query_level() and the leveling system. Compare <code>call [user];query_level</code> (currently broken) with the results from <code>call /adm/daemon/level_d;level_system;/std/user#[instance_number]</code> (works fine). The majority of the code relies on the efun query_level, so it needs to be understood why query_level is returning the wrong value.</strike> | ||
** Issue lies in stat_d (and skills_d) not being able to modify their EUID to UID_ADVANCE. Need to ensure mud driver supports this. | ** Issue lies in stat_d (and skills_d) not being able to modify their EUID to UID_ADVANCE. Need to ensure mud driver supports this. | ||
** Inability to seteuid likely stems from valid_seteuid() in master.c, which pulls permissions from privs.db (where the appropriate permissions are already defined). Looks like privs.db isn't being loaded properly. | |||
* Player skills do not seem to be taken into account during combat. Regardless of how high the skill is raised, it acts as if it is 1. | * Player skills do not seem to be taken into account during combat. Regardless of how high the skill is raised, it acts as if it is 1. | ||
Revision as of 18:21, 7 July 2020
Critical Issues
- Players do not appear to be able to level.
This appears to be an issue not with the advancement system, but a disparity between query_level() and the leveling system. Comparecall [user];query_level(currently broken) with the results fromcall /adm/daemon/level_d;level_system;/std/user#[instance_number](works fine). The majority of the code relies on the efun query_level, so it needs to be understood why query_level is returning the wrong value.- Issue lies in stat_d (and skills_d) not being able to modify their EUID to UID_ADVANCE. Need to ensure mud driver supports this.
- Inability to seteuid likely stems from valid_seteuid() in master.c, which pulls permissions from privs.db (where the appropriate permissions are already defined). Looks like privs.db isn't being loaded properly.
- Player skills do not seem to be taken into account during combat. Regardless of how high the skill is raised, it acts as if it is 1.
Non-Critical Issues
General
- Hunger does not appear to have any impact.
Hell
Guard Shades are not weilding their weapons.- That spear is one-handed. Updated force command in gshade.c to only wield in right hand.
Workarounds In Place
- Colleens store had an issue with the FOOD variable defined in lanark.h. Worked around this issue by replacing instances of FOOD with "/d/tradewinds/lanark/objs/food/".
