Jump to content

sullyvanj93

Premium Member
  • Posts

    388
  • Joined

  • Last visited

Nexus Mods Profile

About sullyvanj93

Profile Fields

  • Discord ID
    sullyvanj93
  • Country
    United States
  • Currently Playing
    New Vegas, RDR2, Project Zomboid
  • Favourite Game
    New Vegas

Recent Profile Visitors

8256 profile views

sullyvanj93's Achievements

Rising Star

Rising Star (9/14)

  • Dedicated Rare
  • First Post
  • Collaborator Rare
  • Week One Done
  • One Month Later

Recent Badges

3

Reputation

  1. If everything in the script is firing, but the line is not being said, then that's where the disconnect is. Are there any conditions of the dialogue line that are not being met? Is the dialogue line marked "say once"? Everything pointing to the correct place within that dialogue quest?
  2. Actually, wahoo5 would fire after the game attempted to say his line, but whether it did or not would not have any affect on the outcome of the Print command. You could put the Wahoo5 print command within the Result Script of the dialogue line itself to see if he is truly saying his line or not? Or just record a test line yourself as a placeholder to see if it comes through in game. The fact that wahoo3 is firing is a good sign, that the script itself seems to be doing what you want it to with the event handler reading your killer properly. I would suggest changing how the wahoos are placed, however. Have additional IF checks, so you know if each piece is firing correctly. Something like this: Set rKiller to aaJimmyCompanionREF.GetKiller Print $wahoo1 If rKiller.GetIsCreatureType 6 == 1 Print $wahoo2 Set aaJimmyCompanionREF.bJimmyKilledByRobots to 1 if aaJimmyCompanionREF.bJimmyKilledByRobots == 1 Print $wahoo3 Set aaJimmyCompanionREF.Say aaJimmyKilledByRobots TO 1 (try to keep the same command format, for your own sanity, and any bystanders as well. Doesn't matter which one, but keep to one if possible) if aaJimmyCompanionREF.Say aaJimmyKilledByRobots == 1 Print $wahoo4 EndIf endif endif END
  3. Something that has helped me OH SO VERY MUCH when figuring out which part of my script isn't working right is adding in PrintC commands within the different chains you're setting up. Try something like Begin OnDeath printC "Is Dead" *rest of script* and see if the printC command fires correctly, listing your "Is Dead" message in the in-game console. If that's firing, that means the script is recognizing that the NPC did in fact die, and you can move on to the next block, maybe an IF variable. If it didn't print your command after the initial OnDeath, I would say your script isn't attached to the NPC correctly somehow. You can even add a handful of them at once, so it's not quite so tedious of trial and error. Figuring out which part of the script seems to be hanging up can be vital for diagnosing and treating your issues.
  4. Oh man, don't tell Arcade this. Even Ed-E makes him uncomfortable The process would be pretty easy. Just have a separate robot creature be enabled based on the conversation choice, and make it at basic (it only listens to Arcade) or in-depth (full companion capabilities) as you'd like. And you could recycle most of the dialogue that is already in game. Check out the Willow companion, and specifically her dog JT. That might give you some ideas here.
  5. Trust us, with those specs and that load order, you will continue to have issues. Your system is not built for that high of performance, and all of those mods add to the strain.
  6. gotta be sneaky enough to observe them in their natural habitat without them doing the combat callouts, because those are obviously just growls and screams.
  7. The clothing itself, I don't see being an issue. I know of a few other custom companions that do that easy enough. But I believe he was wanting to change the models/textures of the super mutants themselves, like the different faces/colors, etc. That would be a bit more difficult.
  8. When you are adding/removing from inventory, you shouldn't use the reference, but the editor ID itself. Try VFSSergio instead, see if that resolves all of your issues.
  9. Cheers to the remaster. Doubtful, but I'll always be foolishly optimistic that it's coming!
  10. Fallout New Vegas mods will only work for PC. Some of the newer titled games can allow for consoles to interact with and use mods, but unfortunately, New Vegas is a bit dated for that. If you're new to modding, and you want to set your computer up for a solid playthrough, I would recommend using a Mod Manager, as that will be a lot easier than manually doing it your first time round. You may even take a look at modding guide, such as Viva New Vegas, as it will outline everything step by step. Pay attention, don't skip anything, and you're going to have a great playthrough. Or there are also a ton of Youtube tutorials out there, if you'd like to come at it in pieces.
  11. Do you have a certain issue you're wanting someone to try to help you tackle on here? Just asking to have an experienced scripter on retainer to help with a load of questions as they pop up isn't really a realistic ask. The best way to learn a vast skillset like scripting is to reverse-engineer other similar mods that are doing what you're wanting to accomplish, and trying something similar on your own. The Geck WIKI is also surprisingly helpful for specific tasks. Or again, if there's a specific obstacle you're trying to push through, there's a few folks here on the forums that would love to lend you a hand and point you in the right direction, should it be a quick q&a type scenario.
  12. Ah yes, great idea! Online tutorials are great, but reverse engineering other mods will take you far! Best of luck, and feel free to reach out to the community if there are specific pieces you're needing assistance with!
  13. Sounds like a fun idea! A couple things to consider: Firstly, don't mess with global variables. You'll want to create a new "quest" for the player's insanity and the "voices" they hear, and have a quest variable monitoring the "insanity level". Much easier that way. Second, it's actually quite difficult to have bad karma in the game, unless you're really trying at it. Stealing and murdering entire settlements seem to be offset by being even remotely decent in the questlines and killing a few evil characters. New Vegas really wasn't as black-and-white as FO3 (to its credit), so it might be more difficult than you think to use that as such a big contributing factor. And lastly, while it's not an overly tall order you're asking for, you'll find that most veteran scripters are going to be working on their own things, are tied up with other big projects, or have simply moved on to games that weren't released more than a decade ago. Even if you find some that are wanting to assist you in this, you'll likely need to come to the table with much more than just an idea to show that their work won't be in vain. If you're able to do a good chunk of the dialogue, have the events timed/initiated how you'd like, and only need some help with a few of the more difficult scripts to finish up, I'm thinking you'll have a much easier time recruiting someone to your team. For more basic scripts when you're first getting started, I may recommend a bit of back and forth with an AI Chatbot, as it can help you format the scripts properly and get you to start understanding the basics. You'd be surprised at how helpful they can be, so long as you feed it prompts effectively.
  14. with how much work and time it took to have any sort of dual wield, I'm gonna go out on a limb and say "not a snowball's chance"
  15. Hey guys! I've been digging and digging and striking out. I'm needing a very simple "coughing" animation to play alongside a dialogue line. Loose Idle, I believe is the term. I know there has to be some examples of NPCs coughing (hopefully nothing too dramatic, like coughing to their death, although I might be able how to figure out how to crop it down if that's the only option). Anyone know what animation I might be able to use here? Thanks in advance!
×
×
  • Create New...