As I have noticed, also with three flags there comes a system with some invisible barriers and gatedoors disappearing upon a given flag being captured. That being said, I hope that KingArthur will reveal the missing information, thereby patching the gap in our knowledge of the NeoGK-augmented Native module.
Login to Account Create an Account
Tutorial: How to create maps with NeoGK
Posted 20 July 2019 - 02:18 AM
I have found the solution on my own, there is no need for KingArthur to reply to this thread, save for a brief commentary about barrier_16m and door_b and maybe other props and their var_no1 and var_no2 values.
- For the flag that will be captured first, the Entry Point is 68,
- for the flag that will be captured second, the Entry Point is 67,
- for the flag that will be captured third, the Entry Point is 66.
There are primarily two props that disappear upon a given flag being captured: barrier_16m and door_b; I do not know about any other ones besides these. However, it is not known to me about their var_no1 and var_no2 and their values that get triggered when a given flag is captured; since I checked those props in Rochester Castle and Minas Tirith I assume and am not entirely sure that for the door_b prop var_no1=1 enables the vanishing of the prop and var_no2=1 or 2 or 3 force the prop to vanish after the respective checkpoints are passed. For the barrier_16m prop in Rochester Castle its properties went as follows: the var_no1=10 and var_no2=1; same prop with such properties was not found in Minas Tirith. Since on the former map there was only one kind of such prop with same properties, I have not enough data to juxtapose with each other and deduce what var_no1 and var_no2 values of the barrier_16m prop enable. For var_no1=10 I have no idea, var_no2=1 maybe forces the prop to disappear after the respective flag is taken.
If making a large scene for siege, it is useful to use the barrier_8m prop and its properties, so that the attackers do not have to walk endlessly from the original spawn point. One has to place it onto terrain that will be walked on the highest amount of times, in order to ensure that said prop will trigger the closest spawns for the attacking team's members.
- var_no1=10 - checkpoint (hereinbelow called "CP") floor 1 - if the attackers step onto this prop with such properties, then their allies spawn from Entry Points 70-79,
- var_no1=11 - CP floor 2 - if the attackers step onto this prop with such properties, then their allies spawn from Entry Points 80-89,
- var_no1=12 - CP floor 3 - if the attackers step onto this prop with such properties, then their allies spawn from Entry Points 90-99.
A person that passes a given CP gets some bonus gold. The order of CPs goes as follows: 1<2<3, therefore they are still effective after the next one is passed, but not stepped onto, according to a not well-written and grammatically incorrect sentence - that was later rephrased by myself - by a NeoGK documentator or developer. The part of my rephrased sentence that is underlined might be neither true nor apt, but that is because of the bad wording of the person responsible for documenting the NeoGK modification, although I used my reasoning and logic skills to the best of my ability and perhaps I captured the essence of said sentence while using better words.
- Elpingouin likes this
I hope that your brain will process such an amount of information.
Vedella new map when
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users