Descriptive Problem Summary: in .dms files the marco tag, \... does not seem to work.
Numbered Steps to Reproduce Problem:
1) Download hosting files for Harvest Moon: Trinity Ranch ( http://www.byond.com/games/WildBlood/HarvestMoonTrinityRanch )
2) Choose to run it in Dream daemon (dream seeker will disconnect you)
3) click start
4) press the question mark in a circle, a message will come up that states the macros
5) press the space bar, nothing should happen
6) press the w key, nothing happens
7) Start > my documents > BYOND > MyHub
8) WildBlood > harvestmoontrinityranch > Harvest Moon > open Harvest Moon.rsc in a notepad document
9) notice how both say and whisper have the \... tagging on them ( My bug report awhile back http://www.byond.com/members/ DreamMakers?command=view_tracker_issue&tracker_issue=1300 I was hoping would inturn fix this)
Expected Results: to have \... tagging work properly in .dms files
Actual Results: from what i can tell, nothing happens
Does the problem occur:
Every time? Or how often? every time
In other games? unsure, untested
In other user accounts? unsure, untested
On other computers? yes
When does the problem NOT occur? if you edit the \... out of in front of say and whisper in the rsc file
Did the problem NOT occur in any earlier versions? If so, what was the last version that worked? (Visit http://www.byond.com/download/build to download old versions for testing.) BYOND 3.5
Workarounds: The way we have been getting around this issue the past year and a half or so, is by using a file editor (such as art money) to remove the \... tagging, which would make a text box to appear when you pressed the space or w macro. This worked well until BYOND changed the way the RSC files are read ( I'm not completely certain what you did to them) what this would do is that after editing the \... out, would cause the rsc file to corrupt ( http://www.byond.com/members/ DreamMakers?command=view_tracker_issue&tracker_issue=1560 ). so, in order to deal with this, we kept the host byond version at byond 467, and that worked for a while. The reason I'm posting this now is because, seemingly randomly, when a player uses the edited say, or whisper verbs, it will cause the game to crash ( I have some dream daemon crash information if you guys want to see it, although, i think if the \... problem can be fixed, it will clear up the rest of these issues.)
ID:100500
Aug 17 2010, 4:23 pm
|
|||||||||||||
Resolved
| |||||||||||||
Aug 18 2010, 8:31 am
|
|
Is the server or the client crashing? Your description is unclear. Either way it would be very helpful to have crash details and a set of steps to follow that doesn't involve editing the client's .rsc.
|
Dream Daemon its self is crashing.
BUG: Crashing due to an illegal operation! Tue Aug 17 17:34:22 2010 proc name: say (/mob/Player/verb/say) usr: Johan411 (/mob/Player) src: Johan411 (/mob/Player) call stack: Johan411 (/mob/Player): say("double click") Backtrace for BYOND 467.1069 on Linux: Generated at Tue Aug 17 17:34:22 2010 DreamDaemon [0x8048000, 0x0], [0x8048000, 0x804a8f8] libbyond.so 0x2a1114, 0x2a111d [0xf57fe000, 0xf57fe40c], [0xf57fe000, 0xf57fe40c] libbyond.so 0x2a1114, 0x2a111d libbyond.so [0xb742a000, 0x0], 0x1e85c8 libbyond.so [0xb742a000, 0x0], 0x23c4c7 libbyond.so 0x250214, 0x250300 libbyond.so 0x231cd0, 0x231d49 libbyond.so 0x2339ec, 0x233a71 libbyond.so 0x20d0b0, 0x20d152 libbyond.so [0xb742a000, 0x0], 0x20d97a libbyond.so [0xb742a000, 0x0], 0x20e069 libbyond.so 0x20f178, 0x20f419 libbyond.so 0x253b2c, 0x253b8d libbyond.so 0x28f15c, 0x28f265 libbyond.so [0xb742a000, 0x0], 0x28f793 libbyond.so 0x290f88, 0x291538 DreamDaemon [0x8048000, 0x0], [0x8048000, 0x8049e77] libc.so.6 0x16af0, 0x16bd6 (__libc_start_main) DreamDaemon [0x8048000, 0x0], [0x8048000, 0x8049b81] To help the BYOND developers debug this, please send the above trace as part of a very detailed bug report: http://www.byond.com/members/?command=view_tracker&tracker=1 |
Okay, if I'm understanding this right the problem comes from the fact that you've altered the .rsc and the altered version is being sent to players, not that the players themselves are triggering this as such. So basiclaly it's avoidable by the host not altering the .rsc, which is something you're not supposed to do in the first place.
The crash seems to be difficult to ferret out but if it's caused by screwing with the server's file cache then I'm not so worried about it. I'll see what we can do about the \... macros. |