joemann Posted July 10, 2018 Posted July 10, 2018 One additional question in connection with the command subtract_variable = { which = size_differential which = anus_size }  According to the wiki :  " Commands on variables have a second parameter, which can be reference to another variable in same scope: (set|change|subtract|multiply|divide)_variable = { which = <variable_name> which = <another_variable_name> }" Does this mean that the difference is calculated between the same characters dick and anus size. Obviously this is not what we are looking for.
NoxBestia Posted July 10, 2018 Posted July 10, 2018 3 hours ago, joemann said: Appreciate your help Nox.  I probably don't understand how variables work, but how/where do I use this ? The way I read this, the first line sets size_differential to the value of dick_size, the second line then subtracts anus_size from dick_size. How is this different from subtract_variable = { which = dick_size which = anus_size } ?  My problem is that I do not understand where and how the result of the subtract_variable is then used  If I use the command check_variable = { which = size_differential value i=3 } , will size_differential now just reflect dick_size or will it reflect dick_size minus anus_size because that is the result I am looking for.  First, let's start by ignoring scopes (I'll get to those below). When working with comparisons, you need a new variable or you are changing the old variable. So, in my example, size_differential gets an initial value equal to dick_size. Then the second line subtracts anus_size from this new variable and then sets the new variable to that value. Whereas the line subtract_variable = { which = dick_size which = anus_size } changes the value of dick_size. You don't want that, or every time you have sex you are shrinking your cock! (Well, I am sure that could be useful in a curse scenario...  )  The command check_variable does not change any values at all. It is a true/false check to see if the variable is >= the number in value. Also, your syntax for check_varaible would not work as it is above (i=3 is not valid here).  2 hours ago, joemann said: One additional question in connection with the command subtract_variable = { which = size_differential which = anus_size }  According to the wiki :  " Commands on variables have a second parameter, which can be reference to another variable in same scope: (set|change|subtract|multiply|divide)_variable = { which = which = }" Does this mean that the difference is calculated between the same characters dick and anus size. Obviously this is not what we are looking for. Now, the code as I wrote it does indeed affect the same character. Getting another character involved becomes even more of a challenge and confusing. Also, you don't want to use global variables for this or you can find yourself in for a world of chaos. First you have to decide what character you are going to use to "do the math with". In your case, I suggest the person being fucked. To make things clearer in my own code, I use event_targets in these cases. Here is some example code I just wrote for you: # The following example assumes you have already assigned event targets with the "save_event_target_as = " command. immediate = { event_target:dick_person = { # this makes a new variable (size_differential) in the fucker so we aren't changing any values. # NOTE: If size_differential already exists (because the dick wielder was getting banged earlier) this will reset it to their cock size. set_variable = { which = size_differential which = dick_size } } event_target:anus_person = { # This is how we copy the fucker's cock size into the fuckee. # This is where the variables having the same name between two characters comes in. # All further work will only be changing values for the fuckee. # NOTE: If the bottom already has a size_differential, this will overwrite it with the new value from the top. set_variable = { which = size_differential who = event_target:dick_person } # This line then does the math, changing the size_differential for the bottom ONLY. # In English the line below means: set size_differential equal to the value of "size_differential minus the value of anus_size" subtract_variable = { which = size_differential which = anus_size } # from here you can continue with whatever other code you want to write to do things to the bottom (because we are still in the bottom's scope) } }  Â
joemann Posted July 10, 2018 Posted July 10, 2018 Thanks for your explanation Nox. This really helps advancing my understanding of variables (although I will need to read it again from time to time and practice using it )  I have introduced the event targets in the event that uses impact_evaluation and have included your script in impact_evaluation itself.  Validator has an issue with the immediate command, but if I delete it it also complains about the <who> in set_variable.  However, with or without the immediate if I test the event in game it does not produce the desired effect.  I believe the problem is with the bottom set_variable because in game with a dick_size of 3 (and an anus_size of 1) it returns a size_differential of 0 where you would expect 3.  I include the event and the scripted effect. Did I miss something?  narrative_event = {    id = RSLVisits.250    desc = "RSLVisits250"    picture = visit_male_female_bottom       is_triggered_only = yes # by targeted_ decision    immediate = {          ROOT = { save_event_target_as = dick_person }       FROM = { save_event_target_as = anus_person }          }    option = {          name = rsl_option_hurt            event_target:anus_person = {                      impact_evaluation = yes                      update_anus = yes }                                        }    }    impact_evaluation = {   ROOT = { save_event_target_as = dick_person }  FROM = { save_event_target_as = anus_person }            ROOT = {                              set_variable = { which = global_dick_size which = dick_size }}               if = {        limit = {                                                    check_variable = { which = global_dick_size which = anus_size } # checks that ROOT's dick_size is greater than FROM's anus_size                            }                         }                immediate = {              event_target:dick_person = {                         set_variable = { which = size_differential which = dick_size }                         }                   event_target:anus_person = {                      set_variable = { which = size_differential who = event_target:dick_person }                      subtract_variable = { which = size_differential which = anus_size }                      }              }            # calculate FROM's new size       if = {            limit = {                   is_variable_equal = { which = size_differential value = 6 }            }                random_list = {                          5 = { change_variable = { which = anus_size value = 3 }                set_character_flag = anus_size_increase_3}        35 = { change_variable = { which = anus_size value = 4 }                set_character_flag = anus_size_increase_4 }              45 = { change_variable = { which = anus_size value = 5 }                set_character_flag = anus_size_increase_5 }         15 = { change_variable = { which = anus_size value = 6 }                set_character_flag = anus_size_increase_6 }                               }        }       Â
NoxBestia Posted July 10, 2018 Posted July 10, 2018 56 minutes ago, joemann said: Thanks for your explanation Nox. This really helps advancing my understanding of variables (although I will need to read it again from time to time and practice using it )  I have introduced the event targets in the event that uses impact_evaluation and have included your script in impact_evaluation itself.  Validator has an issue with the immediate command, but if I delete it it also complains about the in set_variable.  However, with or without the immediate if I test the event in game it does not produce the desired effect.  I believe the problem is with the bottom set_variable because in game with a dick_size of 3 (and an anus_size of 1) it returns a size_differential of 0 where you would expect 3.  I include the event and the scripted effect. Did I miss something? <---snip--->       Immediately I can see a lot of errors and problems, but nothing I can't help get you through. It will take me a little time to weed though and fix this, but keep checking back and I'll try to have it posted within the hour. Also, your event references two effect scripts but you only sent me one, so I can't check the second one. For now, I'll assume the second one works, unless you say otherwise after I post corrected code.
NoxBestia Posted July 10, 2018 Posted July 10, 2018 58 minutes ago, joemann said: Thanks for your explanation Nox. This really helps advancing my understanding of variables (although I will need to read it again from time to time and practice using it )   Okay, I think this should work for you. I changed a bit of your formatting so that some things are easier to see. I fixed the missing brackets in the scripted_effect so they balance out. I also completely abandoned the global_dick_size variable as it was redundant in this. I hope it makes sense, but if you have questions, ask away and I'll do my best to explain.  I expect it will be very rare when you have a size differential of 6, considering the standard scale is 0-7 so you may want to lower that value a little, but that is dependant on exactly what you are going for.     narrative_event = { id = RSLVisits.250 desc = "RSLVisits250" picture = visit_male_female_bottom is_triggered_only = yes # by targeted_ decision immediate = { ROOT = { save_event_target_as = dick_person } FROM = { save_event_target_as = anus_person } } option = { name = rsl_option_hurt event_target:anus_person = { impact_evaluation = yes update_anus = yes } } } impact_evaluation = { event_target:dick_person = { set_variable = { which = size_differential which = dick_size } } event_target:anus_person = { set_variable = { which = size_differential who = event_target:dick_person } if = { limit = { check_variable = { which = size_differential which = anus_size } # checks that ROOT's dick_size is greater than FROM's anus_size } subtract_variable = { which = size_differential which = anus_size } # calculate FROM's new size if = { limit = { is_variable_equal = { which = size_differential value = 6 } } random_list = { 5 = { change_variable = { which = anus_size value = 3 } set_character_flag = anus_size_increase_3 } 35 = { change_variable = { which = anus_size value = 4 } set_character_flag = anus_size_increase_4 } 45 = { change_variable = { which = anus_size value = 5 } set_character_flag = anus_size_increase_5 } 15 = { change_variable = { which = anus_size value = 6 } set_character_flag = anus_size_increase_6 } } } } } } Â
ngppgn Posted July 10, 2018 Posted July 10, 2018 Thi k of subtract variable as -= operator of standard languages: the result overrides the first value. That's why you need some dummy variables to store results when chaining operations.
joemann Posted July 10, 2018 Posted July 10, 2018 I'm afraid that after making all the modifications in game <set_variable = { which = size_differential who = event_target:dick_person }> still sets the size_differential to 0 instead of the expected 2  Validator returns two problems: --- Error 1 of 1 --- At <mod>\common\scripted_effects\rsl_ scripted effects1.txt [impact_evaluation\event_target:anus_person\set_variable] (Line 9, column 7): At least 2 instance(s) of a "which" entry are required, but there are only 1 instances.  and  --- Error 1 of 1 --- At <mod>\common\scripted_effects\rsl_ scripted effects1.txt [impact_evaluation\event_target:anus_person\set_variable\who] (Line 9, column 50): Invalid node "who" in scope SetVar (value is: event_target:dick_person)  I include the start and the end of impact_evaluation. (The second script in the event add_anus works for other events so I don't think there are any issues there)  impact_evaluation = {                      event_target:dick_person = {                         set_variable = { which = size_differential which = dick_size }                         }                   event_target:anus_person = {                   set_variable = { which = size_differential who = event_target:dick_person }                   if = {                   limit = {                      check_variable = { which = size_differential which = anus_size } # checks that ROOT's dick_size is greater than FROM's anus_size                                           }                      subtract_variable = { which = size_differential which = anus_size }                                                        # calculate FROM's new size                   if = {                      limit = {                             is_variable_equal = { which = size_differential value = 6 }                      }                            random_list = {                                              5 = { change_variable = { which = anus_size value = 3 }                                  set_character_flag = anus_size_increase_3}                            35 = { change_variable = { which = anus_size value = 4 }                                  set_character_flag = anus_size_increase_4 }                                  45 = { change_variable = { which = anus_size value = 5 }                                  set_character_flag = anus_size_increase_5 }                            15 = { change_variable = { which = anus_size value = 6 }                                  set_character_flag = anus_size_increase_6 }                                   }             }     ### there are a couple of more if blocks, script ends as follows               if = {                      limit = {                            is_variable_equal = { which = size_differential value <1 } ## Could this be the problem?                      }                            change_variable = { which = anus_size value = 0 }                   }                   # We ensure the size doesn't rise above 7                   if = {                      limit = {                         check_variable = { which = anus_size value = 7 }                         }                         set_variable = { which = anus_size value = 7 }                   }                            }          }    }
NoxBestia Posted July 10, 2018 Posted July 10, 2018 48 minutes ago, joemann said: I'm afraid that after making all the modifications in game still sets the size_differential to 0 instead of the expected 2  Validator returns two problems: --- Error 1 of 1 --- At \common\scripted_effects\rsl_ scripted effects1.txt [impact_evaluation\event_target:anus_person\set_variable] (Line 9, column 7): At least 2 instance(s) of a "which" entry are required, but there are only 1 instances.  and  --- Error 1 of 1 --- At \common\scripted_effects\rsl_ scripted effects1.txt [impact_evaluation\event_target:anus_person\set_variable\who] (Line 9, column 50): Invalid node "who" in scope SetVar (value is: event_target:dick_person)  Okay, I forgot about that little limitation. replace the line "set_variable = { which = size_differential who = event_target:dick_person }" with the two lines below:    set_variable = { which = size_differential value = 0 }    change_variable = { which = size_differential who = event_target:dick_person }  The first block of code below what I gave you would have no effect because you are adding zero to a variable. I also am not sure that <1 syntax works with check_variable.  change_variable means add a value to the variable  set_variable means change the current value to a new value  Â
Alaratt Posted July 10, 2018 Posted July 10, 2018 29 minutes ago, NoxBestia said: I also am not sure that <1 syntax works with check_variable. I have not tried using < or > with variables but on the scripting page of the wiki under numeric operators it does actually use the word variable in the description for the lesser or equal section. I always just use the = as greater or equal though.
joemann Posted July 10, 2018 Posted July 10, 2018 OK I made the changes. I have also changed the <1 to = 0. Both do not produce the desired effect. Following up on the first Validator comment, I looked at the wiki again. It states that: " Commands on variables have a second parameter, which can be: A scope (in the form of ROOT/FROM/PREV/THIS) which contains a variable with the same name: (don't know what this means) (set|change|subtract|multiply|divide)_variable = { which = <variable_name> which = <scope> }" Â So I changed <who => to <which = > no result ( although Validator is happy now ) I'll try using FROM now instead of event_target and also go back to your previous code and see if it works with which.
joemann Posted July 10, 2018 Posted July 10, 2018 No luck.  the debugging tool tip contains the following lines which I have put next to the relevant code  event_target:dick_person = {                         set_variable = { which = size_differential which = dick_size } set size_differential to 3 (is correct it corresponds to character's dick_size)                         }                   event_target:anus_person = {                   set_variable = { which = size_differential value = 0 } set size_differential to 0                   change_variable = { which = size_differential which = event_target:dick_person } change size_differential by 0 ( I suppose this should be 3?)                   if = {                                                                                                                   no other lines it then jumps to the add_anus script                     limit = {                      check_variable = { which = size_differential which = anus_size } # checks that ROOT's dick_size is greater than FROM's anus_size                                           }                      subtract_variable = { which = size_differential which = anus_size }  Hopes this helps ? Â
NoxBestia Posted July 10, 2018 Posted July 10, 2018 28 minutes ago, joemann said: OK I made the changes. I have also changed the <1 to = 0. Both do not produce the desired effect. Following up on the first Validator comment, I looked at the wiki again. It states that: " Commands on variables have a second parameter, which can be: A scope (in the form of ROOT/FROM/PREV/THIS) which contains a variable with the same name: (don't know what this means) (set|change|subtract|multiply|divide)_variable = { which = which = }"  So I changed to no result ( although Validator is happy now ) I'll try using FROM now instead of event_target and also go back to your previous code and see if it works with which. Here is some example code directly from CK2 itself rather than the wiki or my memory:     set_variable = { which = transfer_money value = 0 }    change_variable = { which = transfer_money which = province_offer which = event_target:raiding_adventurer } I question the need of the second of the three "which entries" in your code, but I haven't tried to fully trace what is going on it the associated CK2 event I copied the code from.  (Nevermind, you tried this.)    set_variable = { which = size_differential value = 0 }    change_variable = { which = size_differential which = event_target:dick_person }
joemann Posted July 10, 2018 Posted July 10, 2018 Nox, the message you replied to got scrambled , sorry. I had already changed the code as you suggest ( see my last message) with the result described.
NoxBestia Posted July 10, 2018 Posted July 10, 2018 20 minutes ago, joemann said: Nox, the message you replied to got scrambled , sorry. I had already changed the code as you suggest ( see my last message) with the result described. Would you check something else for me? In the event itself add print_scope_effect = yes to the "immediate" block then after running the event make sure that that FROM and ROOT aren't the same person. (The results of the command will be in the game.log file.)  Â
joemann Posted July 10, 2018 Posted July 10, 2018 found this : Â Printing the current scope - [effectimplementation.cpp:18563]: EVENT [1066.9.15]:- This: Duke Robert the Fox [effectimplementation.cpp:18563]: EVENT [1066.9.15]:- Root: Duke Robert the Fox [effectimplementation.cpp:18563]: EVENT [1066.9.15]:- Prev: Duke Robert the Fox [effectimplementation.cpp:18563]: EVENT [1066.9.15]:- PrevPrev: Duke Robert the Fox [effectimplementation.cpp:18563]: EVENT [1066.9.15]:- PrevPrevPrev: Duke Robert the Fox [effectimplementation.cpp:18563]: EVENT [1066.9.15]:- PrevPrevPrevPrev: Duke Robert the Fox [effectimplementation.cpp:18563]: EVENT [1066.9.15]:- From: Duchess Sichelgaita of Apulia [effectimplementation.cpp:18563]: EVENT [1066.9.15]:- FromFrom: Duke Robert the Fox [effectimplementation.cpp:18563]: EVENT [1066.9.15]:- FromFromFrom: Duke Robert the Fox [effectimplementation.cpp:18563]: EVENT [1066.9.15]:- FromFromFromFrom: Duke Robert the Fox [effectimplementation.cpp:18563]: EVENT [1066.9.15]:- Event_target:test_target1: [effectimplementation.cpp:18563]: EVENT [1066.9.15]:- Event_target:test_target2: [effectimplementation.cpp:18563]: EVENT [1066.9.15]:- Event_target:test_target3: Â In the charinfo the event_targets seem to correspond to two different characters
joemann Posted July 10, 2018 Posted July 10, 2018 I'm logging out now. Just want to say thanks for your help. I really appreciate it. Even if it isn't working yet I feel I've learned a lot.
NoxBestia Posted July 10, 2018 Posted July 10, 2018 11 minutes ago, joemann said: found this :  <---snip--->  In the charinfo the event_targets seem to correspond to two different characters Thank you. I wanted to nix that possibility before we continued. I don't really expect the following variant to work, but please give it a try anyway (and if it does work, then I need to figure out why):    change_variable = { which = size_differential which = dick_size which = event_target:dick_person } Â
NoxBestia Posted July 10, 2018 Posted July 10, 2018 25 minutes ago, joemann said: I'm logging out now. Just want to say thanks for your help. I really appreciate it. Even if it isn't working yet I feel I've learned a lot. I made it work (confirmed in game)!  In the end I moved some of the things from the scripted_effect back to the event itself. Here is the code that works:  narrative_event = { id = RSLVisits.250 desc = "RSLVisits250" picture = visit_male_female_bottom is_triggered_only = yes # by targeted_ decision immediate = { ROOT = { save_event_target_as = dick_person set_variable = { which = size_differential which = dick_size } } FROM = { save_event_target_as = anus_person set_variable = { which = size_differential value = 0 } change_variable = { which = size_differential which = event_target:dick_person } } log = "testing RSL code..." print_scope_effect = yes } option = { name = rsl_option_hurt event_target:anus_person = { impact_evaluation = yes #update_anus = yes } } } impact_evaluation = { if = { limit = { check_variable = { which = size_differential which = anus_size } # checks that ROOT's dick_size is greater than FROM's anus_size } subtract_variable = { which = size_differential which = anus_size } # calculate FROM's new size if = { limit = { is_variable_equal = { which = size_differential value = 6 } } random_list = { 5 = { change_variable = { which = anus_size value = 3 } set_character_flag = anus_size_increase_3 } 35 = { change_variable = { which = anus_size value = 4 } set_character_flag = anus_size_increase_4 } 45 = { change_variable = { which = anus_size value = 5 } set_character_flag = anus_size_increase_5 } 15 = { change_variable = { which = anus_size value = 6 } set_character_flag = anus_size_increase_6 } } } } } Â
joemann Posted July 11, 2018 Posted July 11, 2018 I copied the code and tried it and it works for me also. I tried to understand the code but I won't pretend that I do. For example, why does part of it have to go into the event?  Looking at other scripted effects ( those in ALA-Body mod ) I did notice that all of them also start with an if block . Could that be a requirement?  Anyway, thanks again for all your work. Now I am going to see where and how to use this!
NoxBestia Posted July 12, 2018 Posted July 12, 2018 22 hours ago, joemann said: I copied the code and tried it and it works for me also. I tried to understand the code but I won't pretend that I do. For example, why does part of it have to go into the event?  Looking at other scripted effects ( those in ALA-Body mod ) I did notice that all of them also start with an if block . Could that be a requirement?  Anyway, thanks again for all your work. Now I am going to see where and how to use this! CK2's default scripted_effects don't always start with an if, so I am sure that isn't it.   As for why I had to move stuff, my guess was that something in the way scripts are executed changes how it deals with variables between scopes. The modified version that worked has all the variables copied to the "bottom" before kicking off the scripted_effect. The script_effect then only has to work with variables in one character/scope. Â
joemann Posted July 12, 2018 Posted July 12, 2018 Trying to insert the script into existing event chain which already has defined event_targets which are not dick_person or anus_person  Does it make sense to change the event_target name using the following:  event_target:is_rapist = { save_event_target_as = dick_person }  event_target:is_rape_victim = { save_event_target_as = anus_person }  and the continue with the code ?
NoxBestia Posted July 12, 2018 Posted July 12, 2018 1 hour ago, joemann said: Trying to insert the script into existing event chain which already has defined event_targets which are not dick_person or anus_person  Does it make sense to change the event_target name using the following:  event_target:is_rapist = { save_event_target_as = dick_person }  event_target:is_rape_victim = { save_event_target_as = anus_person }  and the continue with the code ? I have successfully done that before, so it should work okay for you. In the save files you will find the event_target name=character_id so there is no real harm or major bloat to the save file. Plus they usually self-cleanup when the event chain is over.
Alaratt Posted July 16, 2018 Posted July 16, 2018 I am having problems with a narrative event. The goal is to get the desc/picture to change depending on traits I have but it does not seem to recognize traits in the trigger of the desc. The options, set up the same way, work just fine. The pictures all look normal and match the interface file just fine and the localization text looks fine too. Are traits not a good thing to use inside a desc trigger? DWR uses this scripting several times, the only thing I am doing different from his examples I have found is the traits.  Spoiler narrative_event = {  id = Ala_Mavis.20  picture = a_placeholder                #     I get this picture everytime instead of the ones inside the desc = { }  title = ala_mavis_introduction  is_triggered_only = yes  desc = {   trigger = {    event_target:ala_mavis_player = {     NOR = {      trait = vampire_ancient      trait = vampire      trait = dhampir      trait = werewolf_ancient      trait = werewolf      trait = werekin     }    }   }   text = Ala_Mavis20.1                       #    I get this text everytime, even though I am testing as a werewolf or a vampire   picture = ala_mavis_intro_01  }  desc = {   trigger = {    event_target:ala_mavis_player = {     OR = {      trait = vampire_ancient      trait = vampire      trait = dhampir     }    }   }   text = Ala_Mavis20.2   picture = ala_mavis_intro_02  }  desc = {   trigger = {    event_target:ala_mavis_player = {     OR = {      trait = werewolf_ancient      trait = werewolf      trait = werekin     }    }   }   text = Ala_Mavis20.3   picture = ala_mavis_intro_03  } #      These work just fine  option = {   # Mavis joins you - your not a vampire   trigger = {    event_target:et_mavis_player = {     NOR = {      trait = vampire_ancient      trait = vampire      trait = dhampir      trait = werewolf_ancient      trait = werewolf      trait = werekin     }    }   }   name = Ala_Mavis20A   event_target:et_mavis_mavis = {    add_trait = kind  # she decides her father is wrong    add_trait = gregarious # her first contact was good    move_character = event_target:et_mavis_player    hidden_tooltip = {     add_trait = ala_disinherited # dont want her inheriting Vlads titles     culture = event_target:et_mavis_player     religion = event_target:et_mavis_player     narrative_event = { id = Ala_Mavis.22 days = 5 }    }   }  }  option = {   # Mavis joins you - you are a vampire   trigger = {    event_target:et_mavis_player = {     OR = {      trait = vampire_ancient      trait = vampire      trait = dhampir     }    }   }   name = Ala_Mavis.20AA   event_target:et_mavis_mavis = {    add_trait = kind  # she decides her father is wrong    add_trait = gregarious # her first contact was good    move_character = event_target:et_mavis_player    hidden_tooltip = {     add_trait = ala_disinherited # dont want her inheriting Vlads titles     culture = event_target:et_mavis_player     religion = event_target:et_mavis_player     narrative_event = { id = Ala_Mavis.24 days = 5 }    }   }  }  option = {   # Mavis joins you - you are a werewolf   trigger = {    event_target:et_mavis_player = {     OR = {      trait = werewolf_ancient      trait = werewolf      trait = werekin     }    }   }   name = Ala_Mavis.20AAA   event_target:et_mavis_mavis = {    add_trait = lunatic  # a vampire trying to live with werewolves is insane    add_trait = trusting    move_character = event_target:et_mavis_player    hidden_tooltip = {     add_trait = ala_disinherited # dont want her inheriting Vlads titles     culture = event_target:et_mavis_player     religion = event_target:et_mavis_player     narrative_event = { id = Ala_Mavis.26 days = 5 }    }   }  }  option = {   # refuse to let Mavis join you/stays home with Vlad   name = Ala_Mavis.20B   event_target:et_mavis_mavis = {    add_trait = cruel # she decides her father has the right ideas    add_trait = shy  # her first contact didnt end well   }   hidden_tooltip = {    event_target:et_mavis_vlad = { recalc_succession = yes } # make sure she can inherit Vlads titles   }  } }  Â
ngppgn Posted July 16, 2018 Posted July 16, 2018 What happens if you remove the picture = placeholder part? As foe the dwscription, which one are gou getting?
Alaratt Posted July 16, 2018 Posted July 16, 2018 1 minute ago, ngppgn said: What happens if you remove the picture = placeholder part? As foe the dwscription, which one are gou getting? the description I get is the one intended for non_vampires/werewolves. I have not tried removing the placeholder image, I read somewhere that any placeholder is needed there even if it isn't going to be used, and this is how Dewguru does it. I guess I could try though.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now