Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
I am getting following errors when trying to compile oxce 3.0 in visual studiio 2015... any idea what's wrong?sh**, probably bug in VS. I will think how I could avoid it.
I will most probably take this into my fork.I have one suggestion that save me couple of days of work:
Currently I am in process of merging it with oxce3.0... which will take "forever" since I got a conflict basically on every single file
After it's done, I fully agree with accuracy drop, makes sense.
#script defined per item
items:
- type: STR_WEAPON_WITH_MELEE
scripts:
reactionWeaponAction: |
if eq action action_hit; #when you hit with this weapon enemy can react to it.
return 100;
else;
return reaction_chance;
end;
#script defined for all items
extended:
scripts:
offset: 1.0
reactionWeaponAction: |
if eq action action_hit; #all items used as melee will case enemies to react.
return 100;
else;
return reaction_chance; #return old reaction chance
end;
someScriptCode: |
if OPERATION A B; #OPERATION can be: `lt` - less, `le` - less equal, `gt` - greater, `ge` - greater equal, `eq` - equal, `neq` - not equal
#some code 1
else OPERATION A B; #`else` can have same condition as first `if`.
#some code 2
else OPERATION A B; #you can repeat `else` with test multiple times.
#some code 3
else;
#final case, can be skipped.
end;
reactionWeaponAction: |
var int shade; #definition of new variable that can be used by script.
BattleUnit.getTileShade action_unit shade; #getting shade of tile that unit is standing on.
if gt shade 10; #shade of tile is greater than 10.
div reaction_chance 2; #now is two time less chance to react.
end;
div distance 16; #distance between units is in vexels, dividing by 16 give us distance in tiles.
if gt distance 10; #distance is greater than 10 tiles.
sub reaction_chance 30; #subtracting
end;
return reaction_chance;
Now if acting unit is in dark place (unit lighting count!) and 10 tiles away, then enemy units will have only 20% chance tosomeScriptCode: |
var int var_name;
`var` mean that we create new variable. `int` is type of it, in this case this is number.someScriptCode: |
var int answer_to_every_thing 42; #42 is starting value of this variable.
set answer_to_every_thing 13; #it was 42 but now is 13.
We have other types than `int`. They are pointers to object from OpenXcom engine.someScriptCode: |
var int unit_size;
var ptr BattleUnit unit; #read only pointer to battle unit, this mean unit that you can see in battlescape.
var ptr RuleArmor unit_armor; #read only pointer to armor that unit can use and what is defined in `armors` node.
set unit action_unit; #now `unit` and `action_unit` represents same unit.
BattleUnit.getRuleArmor unit unit_armor; #we get pointer to armor of that unit.
unit.getRuleArmor unit_armor; #shortcut of previous operation.
unit_armor.getSize unit_size; #now we have size of unit armor in variable `unit_size`.
One point to avoid "exploits" is that this should be considered even with the facility "being build", otherwise you could potentially chain the constructions and surpass the limitation. I imagine this complicates thingsIn case of OXC "harder" is test for finished buildings :> From game engine you create new thing when you place it on grid. Its simply deactivated until construction is finished.
Give both the same prevention condition and also make them both cause the condition?Then it should be "unique" instead of "forbid".
I didn't want to make this sound "small"... I'm sure you went through hell merging all this... just wanted to say that functionality-wise, there are only 3 features a modder can notice, player will notice even less.Right this is another way how measure changes. And each give different answer
In this release, it is definitely your new features that deserve the most attention, not the vanilla stuff.
There were only less than 2 months of OXC dev merged in 3.0, so there's not many changes.SoldierDiaries was developed bit more time than 2 months and I merge 500 of 800 commit that difference between OXCE and OXC. This mean that time between merge points are not accurate to measure how much changes goes in (numbers of commits could be screwed too based how many changes go in per commit).
Worth mentioning are only three:
1. SupSuper: merged SoldierDiaries
2. Warboy: modularize unit stat adjustment, using TFTD formula: https://github.com/SupSuper/OpenXcom/commit/5c317ce82dcfdd06d487b9991f56d9b3013e8f99
3. Warboy: make damage range a mod instead of an option: https://github.com/SupSuper/OpenXcom/commit/e98da3a56079a4a450e50fca835e2f8d21ce4a49
