Jump to content

shishiwashi

Members
  • Posts

    3
  • Joined

  • Last visited

About shishiwashi

Profile Fields

  • Country
    Brazil
  • Currently Playing
    Skyrim
  • Favourite Game
    Pokémon

shishiwashi's Achievements

Newbie

Newbie (1/14)

  • First Post
  • Week One Done
  • One Month Later
  • One Year In

Recent Badges

0

Reputation

  1. I feel the same way. Have not found any short race pretty head/face mod so far.
  2. This is very troublesome. Because of this problem, I'm totally unable to create any quests. I did some tests (custom quests with dialogue) and this problem appeared in a few situations. I don't see any logic here, but maybe if we look carefully at the results together we may find an answer. 1- Whenever a added the GetIsId dialogue condition on actors that are not in the game (AKA actors that are supposed to show up during the game with codes/events and not in the beggining) OR actors from the Dawnstar Sanctuary, the file is broken (it stops showing the log entry of the quest AND the quest markers). Strangely, I had no problem with many other actors. Everything worked fine with a lot of vanilla npcs (inside and outside locations, in the wilds, etc). I thought it could be the voice type, but it isn't (it worked with most voice types, I did not test each one of them). 2- Each time I add an ALIAS that belongs to the list of 'not working npcs' (Dawnstar Sanctuary people or custom NPC's who are not in the game), the file breaks as well. I had no problem at all in any other cases, but of course I haven't tested every NPC in game. My suggestions to deal around with this problem are: Step 0: before everything, start a new quest in a new .esp file. The moment this problem shows up in a quest, the quest becomes BROKEN. Sometimes I was able to recover it, by removing every dialogue conditions and every quest aliases, but sometimes I wasn't. So I suggest you start a new quest. And for safety reasons, inside a new .esp file (although I was able to create working quests inside my old files). Then: 1- Finish creating every dialogue in your quests without adding the GetIsId condition. 2- Finish creating every quest stage of your quest, every objectives and even the quest aliases but DO NOT FILL any quest aliases (leave them empty). 3- Then save the file and create a back up of it. Check if it is working. If you followed the first 2 steps and left every dialogue without the GetIsId conditions and without filled up quest aliases, it should work. 4- After you have your back up, start testing the GetIsId conditions and the quest aliases with different NPC's. Some are going to work and some are not. If we figure out what is making some NPC's break the quest, we might be able to solve to problem. If we don't, at least we'll know which NPC's are 'broken' and cannot be used for dialogues or as quest aliases. If anyone have another solution for this, I ask for help. As I stated before, this has been very troublesome for me.
  3. Man, after a lot of thinking I just figured out a much easier way to do that. By the way, the whole discussion in this topic was very useful for me. Thank you all for that. What I did was: 1- Created two different skeletons: the leader and the horde. 2- Created a Conjure Spell based on the Atronachs Spells to summon the skeleton leader. 3- Added the script you developed on the skeleton leader. 4- Defined the skeleton property on the script as the skeleton horde. Both skeletons were identical. In that way, you can summon the skeleton leader and the script automaticaly summons 3 more skeletons around the skeleton leader. This also fix up the issue of summoning the skeletons too much near the player.
×
×
  • Create New...