As you'll have noticed from the May 13th change log, I have spent most of the last week or two going through just about every single event in every single file with a fine toothed comb...optimising and tweaking triggers, tweaking mtth values, making changes and tweaks to modifiers, and also revising some of the effects (and scaling the vast majority of the very old events that were scripted before scaling was possible).
None of this precludes me having missed something that is either out of whack, or excessive, or too "mild" or is just plain not WAD, so this thread is where I would like you to report any issues that you have with any of the events.
I am already aware of the bug where some events are not correctly displaying the effects that actually occur when you read the roll-over for the action button, so you don't need to report that one to me. I am also aware of some people's desire to be able to turn off the message notification for some events -- and that isn't going to happen because the coding and event revisions necessary would be prohibitively time-consuming. Also please don't post reports about spelling errors or grammar erros in the event text -- that's a project that we'll get to once we have reached "event lockdown" and the files become static (i.e. won't change in the middle of us working on them). But anything else that you'd like me to revisit should be posted here.
When posting please (if at all possible) give me the event ID and the file in which it's located (I know, I could look it up but you'd be saving me a bunch of time). If you can't do that for some reason (i.e. you don't know how to find it or you're not sure) then please tell me exactly what the event capation text (not the action-button text, but the text at the top of the event box) says. And when I say "exactly", I mean exactly since I will copy your text and then look it up in the event_text.csv and extra_text.csv files. If you have even one letter, space, or punctuation mark (or typo
) wrong then I won't be able to find it quickly.
DO NOT post the entire event code (which can be a pain to scroll through and takes long to load when I'm browsing if it's a long event). If you want to highlight some portion, just paste a few lines of code and I'll be able to find it quickly. Otherwise, give me a detailed description of what you want me to look at, or what was happening that makes you feel that the event is bugged (or should have some other restrictions, or whatever).
For each report that you post here and that contains the requested information, I will review the event. Once I have done so I will edit your post to add my response to it. I'll be using this colour text so it's easy to spot. That way you will know that I've seen and reviewed it, and also it will let other people know what the status is. That also means that I expect (well...request) that you read through this thread before posting so I won't have duplicate reports. Also, if you want to highlight something in colour, please don't use limegreen since it will get too confusing.
To make it easier for all of us, I will "process" these requests/reports in order, so whichever post has my most recent editted-in response is whatever issue I have finished with and the next one is the one that I will be working on next.
Please DO NOT use this thread for new event suggestions. This thread is only for fixes/tweaks to existing events. Also, please DO NOT report issues that you have experienced with an event in ANY previous beta patch. I will ONLY address issues with current patch reports since 90% of the events have been altered in some small way or another.
Thanks!
C.
None of this precludes me having missed something that is either out of whack, or excessive, or too "mild" or is just plain not WAD, so this thread is where I would like you to report any issues that you have with any of the events.
I am already aware of the bug where some events are not correctly displaying the effects that actually occur when you read the roll-over for the action button, so you don't need to report that one to me. I am also aware of some people's desire to be able to turn off the message notification for some events -- and that isn't going to happen because the coding and event revisions necessary would be prohibitively time-consuming. Also please don't post reports about spelling errors or grammar erros in the event text -- that's a project that we'll get to once we have reached "event lockdown" and the files become static (i.e. won't change in the middle of us working on them). But anything else that you'd like me to revisit should be posted here.
When posting please (if at all possible) give me the event ID and the file in which it's located (I know, I could look it up but you'd be saving me a bunch of time). If you can't do that for some reason (i.e. you don't know how to find it or you're not sure) then please tell me exactly what the event capation text (not the action-button text, but the text at the top of the event box) says. And when I say "exactly", I mean exactly since I will copy your text and then look it up in the event_text.csv and extra_text.csv files. If you have even one letter, space, or punctuation mark (or typo
DO NOT post the entire event code (which can be a pain to scroll through and takes long to load when I'm browsing if it's a long event). If you want to highlight some portion, just paste a few lines of code and I'll be able to find it quickly. Otherwise, give me a detailed description of what you want me to look at, or what was happening that makes you feel that the event is bugged (or should have some other restrictions, or whatever).
For each report that you post here and that contains the requested information, I will review the event. Once I have done so I will edit your post to add my response to it. I'll be using this colour text so it's easy to spot. That way you will know that I've seen and reviewed it, and also it will let other people know what the status is. That also means that I expect (well...request) that you read through this thread before posting so I won't have duplicate reports. Also, if you want to highlight something in colour, please don't use limegreen since it will get too confusing.
To make it easier for all of us, I will "process" these requests/reports in order, so whichever post has my most recent editted-in response is whatever issue I have finished with and the next one is the one that I will be working on next.
Please DO NOT use this thread for new event suggestions. This thread is only for fixes/tweaks to existing events. Also, please DO NOT report issues that you have experienced with an event in ANY previous beta patch. I will ONLY address issues with current patch reports since 90% of the events have been altered in some small way or another.
Thanks!
C.
Last edited: