View Issue Details

IDProjectCategoryView StatusLast Update
0000171Medieval EngineersBugpublic2022-04-08 19:22
Reporterd-dubs Assigned Toequinox  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionduplicate 
PlatformWindowsOS10 2004OS Version10.0.19041
Product Version0.7.2 
Fixed in Version0.7.3.968CF8 
Summary0000171: Torches start in off state on login
Description

Unmodded game using [DS] instance hosted locally or on 3rd party provider. When joining the game, player sees most torches in off state, while other players continue to see torches in their current state (on or off - depending on recent in-game activity/manual toggling). Logging out of the server and logging back into the instance causes most torches to be set in off-state again for that player. This re-log action does not affect the state of the torches for other players remaining on the server/instance during the single player re-log event.

As a workaround, introducing the mod, "Automated Torches" (https://steamcommunity.com/sharedfiles/filedetails/?id=1668780689), allows the torches to automatically turn on when the sun goes down and turn off when the sun rises, with respect to locality on the planet. Additionally, this allows the Medieval Master to change the sun position when someone joins the server at "night" to set the sun, then restore the sun to it's nighttime position. This action effectively turns on all the torches for the player who recently joined. This action also affects all players already in the instance.

Steps To Reproduce
  1. Create a generic world in a server instance of ME 0.7.4
  2. Add a variety of torches to a building structure, in the neighborhood of 30 torches realistically set apart from each other
  3. Turn them ALL on (set the local time to night-time for added visibility to the torches)
  4. Log out of the instance
  5. Log back into the instance
  6. Note that a number of the torches are not in their on state
  7. Turn on the torches that appear off / unlit
  8. Log out of the instance
  9. Log back into the instance
  10. Note that a number of the torches are not in their on state
Additional Information

The torches that are off after re-logging may be in the on-state but do not have a fire lit and do not emit light. Instead it may be that the data value state for the off-torch is recorded as off and renders as visibly off.

TagsServer, Session

Relationships

duplicate of 0000157 resolvedequinox All toggled placed objects (Mainly all light sources)  

Activities

equinox

2022-04-08 15:46

administrator   #~0000087

Same root cause as 0000157

Issue History

Date Modified Username Field Change
2022-04-08 13:58 d-dubs New Issue
2022-04-08 13:58 d-dubs Tag Attached: Server
2022-04-08 13:58 d-dubs Tag Attached: Session
2022-04-08 14:38 equinox Product Version 0.7.4 (unreleased) => 0.7.2
2022-04-08 14:38 equinox Target Version => 0.7.3.968CF8
2022-04-08 15:39 equinox Assigned To => equinox
2022-04-08 15:39 equinox Status new => assigned
2022-04-08 15:45 equinox Status assigned => in progress
2022-04-08 15:46 equinox Status in progress => closed
2022-04-08 15:46 equinox Resolution open => duplicate
2022-04-08 15:46 equinox Note Added: 0000087
2022-04-08 15:46 equinox Relationship added duplicate of 0000157
2022-04-08 19:22 equinox Fixed in Version => 0.7.3.968CF8
2022-04-08 19:22 equinox Target Version 0.7.3.968CF8 =>