kromey

Hello everyone! Sorry for the long absence, and lack of any update in... ugh, much longer than I want to think about right now. I can see that this thread is still immensely popular, and that there's still a lot of interest in this mod. This is awesome, and I thank you all, but it makes this announcement that much more difficult. Here's the short version: Lichdom is not dead. I still have every intention of finishing it and releasing my vision of what a lich should be to all of you lovely folks. It is, however, comatose. I simply lack the time right now to work on this mod, or to even play Skyrim at all. Real life has gotten in the way so much more than I could have ever anticipated, as well as new games have come across my desktop that are robbing so much of my attention right now. And while it pains me to have to say this -- hence why I've put this off for frankly way too long -- I have to shelve this project for now. All is not lost, however! I had always intended to make Lichdom a fully open source project, to welcome collaboration and even forking of the project for those whose ideas are different from my own. All this announcement really means is that I'm officially releasing the Lichdom source sooner than anticipated. Anyone who wants to pick up the development is welcome to do so, provided the following conditions are met: Properly credit my work. I've put a lot of effort into this mod, and I didn't do it so someone else could come along and steal it. So play nice. Properly credit my testers. They've put a lot of effort into this mod as well, and they deserve just as much acknowledgement in the final product as I do, if not more. They are, in no particular order: jonmsawyer, Shadowjin, oblivionhot, PieLighter, dudeinmask, CorperationPop Do not call your mod "Lichdom". What you produce will invariably be different from what I will eventually -- yes, it will happen -- release. You are welcome to say in your description that your mod is based on Lichdom, or is a fork of Lichdom, or any such similar language, so long as it is clear in both description and title that it is not Lichdom. I prefer to avoid any potential confusion between my eventual release and the work of others.Everything I've done to date is on my Github page. Hopefully some other modder out there -- maybe even one more skilled than I -- will pick this up and deliver to y'all a mod that satisfies. Regardless of whether or not that happens, I do intend to return to this mod when I find the time and motivation to do so. Ironically, I'm posting this announcement just as I'm beginning to see the glimmer of hope that real life may soon get out of my way again, that the time when I can return to working on this mod may finally be on the horizon. But frankly this announcement is months overdue, and as I can make no promise as to when I'll again have the time to work on this, I cannot justify not posting it. Thank you all for your support over these last many months, and your continued faith in me even when I had disappeared and given you no reason to believe this project still lived. And I'm sorry I'm not back with better news.

The lore's actually contradictory on this point, with -- as you point out -- Celedaen saying the phylactery is inconsequential after the transference, but lich lore citing it as their weakness. One way of reconciling the two is to point out the Celedaen himself chastised his own ignorance and foolishness in a subsequent entry in that same journal; maybe, while he was wrong about how to obtain the secrets, he was also wrong about the significance of the phylactery? Another way of reconciling it is to recognize that there are different types of liches with TES lore, and that Celedaen's method of obtaining lichdom (getting the secrets via divine revelation) and Artun's method (good old fashioned (magical) science) are different, so quite likely while they achieve similar results there will be differences. To put it another way, is a vampire a vampire? Well, no, actually -- one turned via Sanguinare Vampiris (Skyrim) has different abilities and different weakness than one turned via Porphyric Hemophilia (Oblivion). Or consider any of the host of other undead creatures throughout TES, each of which has several different variations even within the same game. Surely liches are no different in this regard, and there are different types of liches with different abilities and different weaknesses?

Oh that's a cool idea!! Unfortunately it's too late in the game to add that now, but that would be an awesome extra for Ancient Liches in the subsequent update! No one needs to worry about this mod vanishing. As PieLighter has said, there's already too much there for me to drop it now. And I have planned from the very beginning to make this mod completely open source -- if for any reason I am ever forced to drop it completely, I can promise you that everything I've done up to that point will be released for someone else to pick it up and continue it. I'm not publishing my source just yet because, frankly, it's a fugly mess that's just too embarrassing to put out there just yet -- have to clean it up before I do that (and have to do that anyway if I have any hope of keeping it maintained!). :P

To make a unique forge a la the Skyforge, simply duplicate a forge and then add a new, unique keyword to it (note that forges have a keyword like CraftForge or something, and then the Skyforge has an additional keyword CraftForgeSkyforge; you'd create a new one to add to your forge, like CraftForgeFrenchiesAwesomeForge). Then, in the recipes for your crafting recipes that can only be made at this one unique forge, the crafting table keyword would be changed to your unique one (just like how the Nord Hero recipes specify CraftForgeSkyforge). Oh, and if you want your unique forge to not permit normal crafting, simply remove the regular CraftForge keyword from it. If you additionally want these recipes available only after completion of some quest, have said quest grant the player a new perk (that is not added to the perk trees and therefore invisible), something like FrenchiesAwesomeCraftingPerk. Then, your recipes have an additional condition added to them that depend upon the player having this perk -- in exactly the same way as e.g. Dragon Scale armor requires the Dragon Smithing perk. *Note: It should be obvious, but the "keywords" above are not the exact keywords in use in the CK, and are here for illustrative purposes only -- hopefully the meaning is clear, and the real keywords obvious enough once you look for them.

Hey guys! This mod is not dead! Unfortunately, work is just absolutely insane right now, and when I'm done with 50-60+ hour weeks I just have neither the energy nor the motivation to then fire up the CK. Sadly, I have to say that the mod's current status is on hold. But not, I repeat NOT dead! I cannot estimate when I'll next have time to work on it, let alone when my testers can expect the next Alpha, and I certainly cannot even begin to guess when I'll have the public beta or general release out. What I can promise you is that I will see this project through to the end -- and by "end" I mean a fully functional release that you can all download and enjoy to your heart's content! I've already put too much work into this, I will not let this project die, not without on hell of a big fight, I promise you that!

What about this? When he dies, after you teleport him but before you resurrect him: Self.RemoveAllItems(HoldingCellChest, True, True)This takes everything out of his inventory and places it into HoldingCellChest, which should be an empty chest you place in his holding cell (be sure it and the holding cell don't respawn). Then, when you summon him, just before you teleport him to your location: Self.RemoveAllItems() ;Just empty his current inventory (should ditch that stupid bow) HoldingCellChest.RemoveAllItems(Self, True, True)This puts everything you stashed on him earlier back in his inventory. (Note that this means you should put any items you want him to initially have on him in the chest, not on his person. And I have no idea how this will interact with outfits -- probably need that to be in the chest as well.) Now, all that being said, I suspect the reason his inventory is resetting is because he and/or his holding cell are respawning. Make sure neither respawns. I don't think Resurrect() is supposed to reset inventory, so I suspect something else is doing that.

Sorry, but you'll have to use a script. It won't hurt compatibility to do so, though, just attach a new script to your object with an OnContainerChanged event: if the new container is the player, apply the effect; otherwise if the old container was the player, remove the effect. The effect itself should be an ability, applied via AddSpell and removed via RemoveSpell.

If you want to attach this script to your NPC, first you need to change that first line to have it extend Actor instead of ActiveMagicEffect. Then drop the OnEffectStart event altogether. This leaves you with just the Summon function. If you put it in the same script as the one with your OnDying() event, all you have to do is call it -- passing in your marker as the akSummoner argument, and self as akSummon.

To make it trigger on your NPC's death, use either the OnDeath or, my favorite, the OnDying event (OnDeath at least used to have some problems wherein it would not always fire -- no idea if those have been fixed, but I still stick to OnDying). This would have course have to be in a script on your NPC. For better visuals, you may want to consider using Utility.Wait, so that your NPC can die, you can see his corpse for a second or two, and then he gets teleported away. Or not -- up to you. Resurrection is easy, too: just call Resurrect on your actor. After you teleport him away to his holding cell, of course -- could even use Utility.Wait again just to be sure, if you wanted to. I haven't looked at that teleport spell tutorial, but there shouldn't be any issue with using it to teleport an NPC rather than the player. And, yes, you'd most likely teleport him to a markerREF in his cell. Or you could just use the same teleport -- shiny visuals and all -- you already use to summon him to the PC to instead "summon" him to a markerREF in his holding cell. So you'd attach a script to your NPC that looks something roughly like this: ObjectReference Property HoldingCellMarker Auto Event OnDying() Utility.Wait(2.0) ;give the PC time for a dramatic "NOOOOOOO!" upon the NPC's death YourShinyTeleportSpell(HoldingCellMarker) ;presumes that the passed-in argument is where you are teleporting to Utility.Wait(2.0) ;Wait a couple of seconds to make sure you don't accidentally rez too early Self.Resurrect() EndEvent(Note: Consider this to be pseudo-code, not an actual script, although it should be rather close.)

Nah, grand jury's different, we only say whether or not the state's got enough to take felony charges to trial, we don't decide guilty/innocent. And I think they'd get a little suspicious of I claimed to know the defendant in 12 distinct cases!! :P

Status update: Unfortunately I was called into grand jury duty, which sucked up the last two days and I've been unable to make the progress this week I needed to to get Alpha 4 to my testers this weekend. I've now got confirmed tickets and will be flying out bloody early Sunday morning, and returning late the following Saturday, so it's sadly going to mean a significant delay before much further progress is made. My testers have also turned up a couple of issues that, if confirmed, may take a fair bit of time in and of themselves to fix, further extending the delay. Right now I'm just playing things by ear, but I think end of March is still a fair target -- probably before that, really.

Maybe different tailors selling different tiers of goods? E.g. one specializes in expensive clothing, while another in more practical working clothing (e.g. miner's outfit, blacksmith apron, etc.). Competition is always good, too -- who says there has to be only one baker selling sweetrolls? In the real world competition is the norm (how many competing pizza joints do you have near you?), which is something generally lacking in Skyrim. Also, I like lots of different inns/taverns. Each with their own distinct atmosphere (a dark seedy one that my assassin/thief characters would favor; a bright, cheerful, well-to-do place that my Arch-Mage would prefer; etc.). Also would be nice to have one each of a "just inn" and "just tavern" -- not all such places cater to both sets of needs! (Probably "just taverns" would be more common...) Another option to consider is a training center, where you can find a few assorted trainers. Could even go fancy and have one place a gymnasium (focusing on combat skills), one place a wannabe Winterhold College (focusing on magic skills), and hidden back in some dark corner a few shifty-looking types who can teach you the tricks of the assassin's and thief's trades. Having too many trainers in one area (i.e. in one city) might be considered OP by some, though, as in vanilla you pretty much have to travel far and wide to find all the trainers you want. (On the other hand, these are probably the same one who might consider having so many merchants in one place OP, so maybe you just want to ignore them. :wink: )

Status update: It's getting exciting, folks!! I just sent Alpha 3 to my testers, and this version finally has a fully-functional quest to find the secrets to becoming a lich, one that will take you to the furthest corners of Skyrim and -- at least it has for me -- show you interesting places you've not yet seen in the game! Using the Radiant Quest system means that I wasn't restricted only to places I know, and it was actually a lot faster to do it this way (because I suck at navigating in 3D editors); it also means that no two games will be alike! With this major piece now in place, there's only a few more big pieces and a small handful of minor to-do items yet to cross off my list; I hope to have Alpha 4 to my testers this weekend, and soon after that I should be able to finally publish the open beta! A quick note, though: I will be traveling next week for work, and even though I'll likely have a lot of down time after work hours, I won't have access to my Skyrim computer. This means that if Alpha 4 is even a day later than I plan (and so far they've all been 1-3 days late), it will be delayed at least a full week, and either way the public beta is most likely at least 2-3 weeks away still. Still, I think it's looking good to release version 1.0 by the end of March!

I'm giving up providing an estimate on release -- things keep popping up that require being addressed first, or that slow down development and I get behind where I thought I would be. That said, though, it is getting close to being done, so it'll be out Soon*! *"Soon" is a Registered Trademark of 3D Realms, developer of Duke Nukem Forever. Good way to express it is saying "It'll get released once it's ready" :biggrin: Also, I am hugely sorry for the lack of participication on beta.. I've had couple of IRL things that keep me reserved quite well, and when I'm finally on my own PC, skyrim is not the first thing I want to think about. (Even if I do spend alot of my free time on Nexus..) No worries, I know all too well how life can get in the way, and it's part of the reason I accepted as many testers as I did -- I don't really need 6 people looking for bugs, but having 6 means that if 4 can't for any reason I've still got 2. :)

I'm giving up providing an estimate on release -- things keep popping up that require being addressed first, or that slow down development and I get behind where I thought I would be. That said, though, it is getting close to being done, so it'll be out Soon*! *"Soon" is a Registered Trademark of 3D Realms, developer of Duke Nukem Forever.

If you force the current weather when the player leaves the trigger, your weather will never change because you have an override in effect. The reason the weather changes to something else when you release the override is because (I imagine, anyway) weather "patterns" continue to run behind the scenes, they're just "hidden" until you release the override. No way around that, not without, in effect, creating your own entirely new weather engine.

Mother pus bucket!! Never mind. My own stupid fault. I was inside my test cell (my own version of qasmoke) when I read the notes that updated the global variables, and apparently quest markers don't update on the map when you're inside an interior cell that isn't connected to the outside world... :confused: For the record, the conditions on quest targets work perfectly -- change the variable and the quest markers appear immediately, no problem.

I'm assuming this is building on your previous weather script? Why was ReleaseOverride() (or whatever the specific call is) not sufficient? I suspect the new ForceActive() call isn't working because you're not releasing the original override first, or because your local variable is falling out of scope (a topic the CK wiki doesn't even seem to mention at all), but we'd need to see the full context of your script to know for sure.

I have a quest where the player is supposed to run around gathering several items from all over Skyrim. However, unless the player happens to read a specific note, no quest markers appear on the map -- and, when the note is read, quest markers then appear. I tried to implement this by using the Conditions on the relevant objective's quest targets. I created a global variable that initially is set to 0, and added a script to the aforementioned note to change that value to to 1 when it's read. I then added a condition to each quest target using GetGlobalValue, checking if it's >= 1. In theory this should make the quest markers appear only once the player has read the note and that variable has been set to 1, right? Unfortunately, no such luck. The quest objective displays correctly and, as expected, has no visible quest markers initially. However, when the note is read and the variable's value is changed (verified via debug notifications), the quest markers still refuse to appear. I'm now thinking that I'll need multiple copies of the same quest objective, one for when the note hasn't been read (with no targets), and one for when the note has been read (with targets). (Actually there will be 4, because there's actually 2 notes which can be read in either order, but I'm simplifying the problem for this post because I can easily extend the solution.) However, this seems rather a dirty hack, especially since there are conditions available on the targets. Any ideas? Is multiple quest objectives the only viable option here, or am I simply missing something with the conditions on the quest targets?

Yeah, that one's a known bug (although I forgot where I read that, and quick checking doesn't turn up a reference). One option to get around is to use ModAV in OnEffectStart to penalize the damage resistance, and then manually fix it again via ModAV in OnEffectEnd (i.e. using a script instead of the non-scripted approach). Of course, modifying Light/HeavyArmor, if that indeed works correctly as your testing apparently shows, might be better anyway, as it wouldn't have any effect on an unarmored opponent (which, frankly, to me, is how it should be anyway). (I'm going to have to keep this in mind, I've got plans for a mod much later on that was going to use this type of approach via a weapon property.)

One option to consider is to simply allow Breezehome to be bought. You could do this "unofficially" via console commands by waiting until you had the appropriate amount of gold, then removing it from yourself while granting yourself the key. Wouldn't be able to upgrade the home via talking to the steward, but that might fit your "everyman" style better anyway. I'm sure you could do something similar in Solitude, but to be honest all my characters live in Whiterun (in Breezehome) and just visit the other cities when necessary (and don't tend to stick around longer than necessary).

Heh. I think what he means is that in your enchantment's Magic Effect, instead of applying any particular effect (you could select the Script archetype and just not assign any script) you use the Perk To Apply field to apply a perk. This perk would grant the BladesAbDragon ability (or whatever other enchantment you're trying to apply via a means it wouldn't normally allow, e.g. armor being unwilling to work properly with weapon enchantments).

Major facepalm here. :facepalm: Look closely at the Fragment01Location alias. Look especially at its conditions. Compare those carefully to the ones the tutorial uses. See it? I was using the condition functions HasRefType and HasKeyword; I needed to be using LocationHasRefType and LocationHasKeyword. Y'know, just like the CK tutorial says. :rolleyes: I guess I need to be more careful when I RTFM... The good news is that it works now. :dance: The quest auto-starts, my global variables used in text replacement in the quest objective are being evaluated now, and for the record the aforementioned Debug.Notification line outputs "Fragment 1 is in [Locat" (I assume it got truncated trying to say "[Location]" or something like that) when the alias fills successfully. And, we now know that using console commands to start/progress a quest indeed does force a quest to start even when non-optional aliases fail to fill! Thanks for the help anyway, SinderionsBones, and like I already mentioned you preemptively solved my headache trying to figure out why the text replacement in my quest note wasn't working. :P

That looks pretty sweet, lordzaros! Hm, just had a totally crazy thought: Is it possible to put an item in the player's inventory, and force it to be equipped, without it showing up in their inventory? Making a skull "mask" that is forced onto the player when they become a lich could be a quick, easy, albeit rather dirty method of applying a different look to the lich. Or better yet: Since the player will be forced to wear their phylactery while a lich, maybe the mesh could be updated to include both amulet and mask? I have no idea if that would play well with head movements though -- maybe someone up on meshes and such could provide some insight?

@Voltage_Joe: Lichdom is being implemented (at least for now) as a series of abilities, not as a technical race change. The transformation will prohibit the already-undead from becoming a lich (so vampires can't become one), but not werewolves. As for going the other way, becoming a vampire requires contracting a disease; liches are immune to disease, however, so you cannot become a vampire as a lich. On the other hand, becoming a werewolf or a vampire lord is a quest, and as such a lich can achieve those transformations. I have no plans at this time to change any of this; if you feel a werewolf-lich or vampire lord-lich is over-powered, well, don't become both. @ArtMurder: Sounds pretty cool. Unfortunately, I don't think my mod will give you quite the jumping-off point you're looking for here -- you're basically creating a cursed item that imparts several abilities (not all of them beneficial, I'm assuming), whereas I'm creating one heckuva magic spell/quest to do similar. I think what you're looking to do here is pretty dang sweet, I just think you'd be better off starting from scratch (although I'd be happy to offer my help answering questions and suggesting solutions to any problems you may encounter). As for first person/third person, the only time I force one or the other (third-person) is if the player decides to drink the Elixir of Endless Night (try it and find out what happens, if you're curious ;) ), although the game engine does force third-person upon the lich transforming into a nether lich. There's unfortunately no real difference, visually, between being a lich and being... whatever you were before. Becoming a nether lich, the only difference is you become a literal "ghost" of your former glory (i.e. you're reduced to being 75% transparent). So first person will be no different as a lich/nether lich to what you're familiar with now (I myself play in first-person all the time as well); I have no idea how well Joy of Perspective will handle the transparency of a nether lich, but worst case is you'll still be looking down your non-transparent cleavage I'd imagine.