Greetings.
A lot of modders are really upset of variable's issue that has came from recent patch. The problem is that some previous variable's possibilities don't work properly after 2.0. What I mean - earlier we were allowed to use such expressions:
Now the 2nd row doesn't work at all and 4th is incorrect. This has a huge impact on our mods as now this is much harder to make complex estimations and operations. Of course, maybe we're able to find some hint or trick to solve this issues, but it really slows down the performance of the mods. For example, how it looks now to copy the value from one var to another:
It's ugly, eh? And in this case it's very hard to write some code to deal with decimals.
So, we are really want to know, will pdx devs fix this issues in the next patches? And when. I've recently posted a bug report for this problem but it seems like it's not processed yet. I'm not complaining about that, because I understand that dev team have a lot of other crucial issues, especially around general gameplay stuff. But I want to emphasize again, that this is really important for modding community. This issues make the modding process really terrible for any complex and interesting idea and potentially decreasing the amount of good stuff for the game. @Wiz , @Jamor , @candyalien , maybe you can help us or tell something that will return our hope and moral.
P.S., this is not only my thoughts, other modders are really interested in solving this.
@ExNihil , @Waesche , @Caligula Caesar , @ViolentBeetle , @Shaggo and others.
To everyone: feel free to support this thread.
A lot of modders are really upset of variable's issue that has came from recent patch. The problem is that some previous variable's possibilities don't work properly after 2.0. What I mean - earlier we were allowed to use such expressions:
Code:
set_variable = { which = var1 value = 100 }
set_variable = { which = var2 value = var1 }
set_variable = { which = var3 value = 10 }
change_variable = { which = var3 value = var1 }
Code:
# replacing set_variable = { which = var2 value = var1 }
while = {
count = var1
change_variable = { which = var2 value = 1 }
}
So, we are really want to know, will pdx devs fix this issues in the next patches? And when. I've recently posted a bug report for this problem but it seems like it's not processed yet. I'm not complaining about that, because I understand that dev team have a lot of other crucial issues, especially around general gameplay stuff. But I want to emphasize again, that this is really important for modding community. This issues make the modding process really terrible for any complex and interesting idea and potentially decreasing the amount of good stuff for the game. @Wiz , @Jamor , @candyalien , maybe you can help us or tell something that will return our hope and moral.
P.S., this is not only my thoughts, other modders are really interested in solving this.
@ExNihil , @Waesche , @Caligula Caesar , @ViolentBeetle , @Shaggo and others.
To everyone: feel free to support this thread.
Last edited: