Announcement

Collapse
No announcement yet.

Any way to stop Kismet variables from renumbering when a variable is added, deleted, or copied?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Any way to stop Kismet variables from renumbering when a variable is added, deleted, or copied?

    This is wreaking havoc on my saved games. Every time I add a new Kismet variable, or delete or copy one, the existing variables get renumbered (eg. SeqVar_Bool_5 becomes SeqVar_Bool_6 or similar). This is problematic because the saved game records SeqVar_Bool_5's value, and then uses that to determine whether a door should be unlocked, but then if I change something and then load the game, SeqVar_Bool_5's value gets written, but in the Kismet sequence, it's now a different variable.

    Is there any way to prevent Kismet variables from renumbering?

    For now I'm just going to try transitioning all of my game progress to custom data structures (like quests and journal entries). But if I could stop the variable renumbering, that would save me a lot of headaches.
    Check out Himeko Sutori, the upcoming tactical RPG where you control armies of over 100 unique characters.

    #2
    If I find the trick I will tell it to you lol, for now we have to deal with it..... I think no idea
    Some cool unreal projects you may like!


    Developer of GOTA - Survivalism Gladiatorial game Buy the game google gladiators of the arena steam https://store.steampowered.com/app/7..._Of_The_Arena/

    Download the demo Download the demo
    external link Dropbox DropBox

    Become a c++ Professional now C++ Networking Tutorial

    Comment


      #3
      Seen it done before.. May have even gotten it to work myself a few times, but its been a while...
      Ctrl-C the new var to notepad before tweaking it & pasting it back into the freshly loaded level....
      ....Or...
      Modify the underlying Kismet level source file contents so that the existing numbering remains...

      Comment

      Working...
      X