Profile of Sie_Sayoka

Avatar Area

Offline Unknown SteamID unknown
Posts: 100 | Subs: 1

General Information


Thread: SWS Cannot use ability on this target.7 Jan 2022, 04:33 AM The SWS halftrack has all the relevant references within the squad category. You will want to look for ability and loadout extensions and reference those accordingly. To diagnose the problem why the ability cannot be used, label the requirements so you know which requirement is not being fulfilled. I have looked at the ability requirements and none of them have the string "Cannot Use Ability On This Target". I'm unsure if this is because the mod tools are outdated or because its a default message of some target requirement within the ability not being met. If you can still not diagnose the issue then start by deleting requirements until it works. In: Modding and Tools
Thread: [Guide] Attaching to Moving Entities5 Dec 2021, 17:50 PM I'm not sure if I've encountered the issue where it will turn after teardown although I haven't used that specific behavior in the weapon. There are 3 possible solutions I can think of. 1. Target action. You can add an action to this to have it target something else, maybe itself, and it might change the direction of the turret. I'm not really sure how this works it may require an action that will affect the turret. 2. Enable hardpoint modifier. Normally if you disable a hardpoint with -1 it will revert back to its default direction. 3. Override_weapon_target_prereq_action. If your filter removes all possible targets maybe it will revert to its default direction. In: Modding and Tools
Thread: Armor Company - Can't dispatch Assault Engineers3 Dec 2021, 09:47 AM I don't know the specific cause of your problem perhaps some change between when mod tools was last updated and now. This can easily be tested. 1. Clone the assault_engineer_squad_mp in sbps and label everything under squad_requirement_ext>ui_name. This should let you know specifically what the issue is. 2. If the requirements for the ability are still blank clone the assault_engineer_dispatch in abilities category. Label the requirements as well. Once you know what the problem is it should be fairly simple to fix it. Hopefully this points you in the right direction. In: Modding and Tools
Thread: [Guide] Attaching to Moving Entities30 Nov 2021, 12:30 PM Jump back to quoted post30 Nov 2021, 01:23 AMDar 1. Sometimes, for minutes even, the vehicle will drive 10 meters back and forth on the spot until it eventually heads to a new target of opportunity. This happens in combat as well, and looks rather ridiculous. Never encountered anything like this before 2. The AI uses the vehicle much like a team weapon, despite it's armor, mobility and firepower. That means it won't do a frontal assault with it, but rather drive around the edges of the map looking for an open flank, sometimes parking the tank there to wait for you. Not terrible, but not what I had in mind. The tank will also try to remove itself from any engagement with other armor and sometimes infantry by reversing away, even if it could put up a fight. These are just guesses. For the first problem this may be an issue with the simbox where the pathing becomes confused. For example if the entity is either has something in its abp that has conflicting pathing or something attached else is blocking it, it will try to move around something that is attached to itself. You can try and use a vanilla blueprint for the alternative_sua within entity_blueprint_ext and see if this works. For the second problem this sounds like an issue with tactics. Check out the ai_squad category and ai_settings>tactics to possibly change the behavior. Ensure the all entities within the squad are of the correct types. In: Modding and Tools
Thread: [Guide] Attaching to Moving Entities29 Nov 2021, 10:02 AM Wow those tanks look amazing. Attached entities are able to be seen on AI controlled units but it is inconsistent. I'm not sure what the cause is but I haven't looked into it as only 1 AI unit within my mod uses it. This may be related to the attached entity not updating its position fully and having it spawn within the FoW somehow prevents them rendering but this is only a theory. I'm not entirely convinced that the dummy weapon itself is the issue at hand but I don't know enough about AI to say for certain. Several units natively have dummy weapons and since the other weapons on your entities are useful the AI should use the units normally. An easy way to test if the weapons are causing the issue would be to replace the dummy weapon with a normal one. A time-consuming way I would test if this isn't the cause would be to make a test mod and clone a team weapon. Then slowly start changing the extensions. Because you know the AI would build the vanilla unit it will be easy to determine the specific cause of the issue. I'm probably not the best person to ask about AI behavior. Sneakeye or Zycat should have more insight into this. In: Modding and Tools
Thread: [Guide] Attaching to Moving Entities23 Nov 2021, 18:37 PM I see, so it's a more sophisticated version, my mistake. In: Modding and Tools
Thread: [Guide] Attaching to Moving Entities19 Nov 2021, 00:40 AM Well done, those look perfect. In: Modding and Tools
Thread: [Guide] Attaching to Moving Entities18 Nov 2021, 13:49 PM Have you ever experimented with attach action chains? Like, make the attached child spawn an attached child of their own? In my limited testing, I could never get the child of the child to stay around as it would despawn for some reason after a few ticks. My thinking was that if child A is turned backwards, child B (child of child A) will be faced forwards using the same attach marker. Presumably attaching to an attached entity doesn't work correctly because child entities do not have their position updated fully, as evidenced by them only attacking where they have spawned. What happens is that the child entity will switch between its spawn point and the position where it's attached to. I've done some testing but didn't dig that deep into it. In most cases this is not helpful at all but an interesting thing of note would be that trailing effects such as smoke from a projectile will travel between these 2 positions. You could then use this to have visuals of linking 2 separate positions to one another. In: Modding and Tools
Thread: "prefer vehicles" for infantry anti-tank weapons?17 Nov 2021, 13:59 PM I think you can put the ability on the entity then have the slot item as a requirement on that ability. If that doesn't work you can make a clone of the infantry unit and have it be the only one that spawns with a bazooka. To have infantry not target tanks you can use not>required_unit_type. Of course this wouldn't actually check if the unit can be damaged or not so you'll have to make sure that the penetration and armor values of the things you want affected are accounted for. In: Modding and Tools
Thread: "prefer vehicles" for infantry anti-tank weapons?15 Nov 2021, 15:00 PM What is the purpose of having 5 identical override actions? Also, many of these commented changes don't work with always_on as far as I know. If I'm reading this right you want an always_on ability that will only target vehicles. Luckily I use one of these within my mod although it targets a different unit type and is only an entity without a squad. I don't think it should matter though. <instance description="vehicle hold fire Ability specific to the OKW Raketenwerfer" template="abilities"> <group name="ability_bag"> <group name="action_list"> <list name="end_self_actions"> </list> <list name="end_target_actions"> </list> <list name="start_self_actions"> <template_reference name="action" value="action\ui_unit_modifier_action"> <bool name="die_with_creator" value="True" /> <template_reference name="ui_info" value="tables\ui_info"> <locstring name="screen_name" value="0" /> <locstring name="help_text" value="0" /> <icon name="icon_name" value="Icons_abilities_hold_fire_on" /> <string name="hotkey_name" value="" /> </template_reference> <uniqueid name="id" value="1073754249" /> </template_reference> </list> <list name="start_target_actions"> <template_reference name="action" value="action\override_weapon_target_prereq_action"> <list name="requirement_table"> <template_reference name="required" value="requirements\required_unit_type"> <enum name="reason" value="usage" /> <locstring name="ui_name" value="0" /> <enum name="unit_type" value="bangalore" /> <template_reference name="qualify_option" value="options\none"> </template_reference> <bool name="search_load_out" value="False" /> <bool name="owned_by_player_only" value="True" /> </template_reference> </list> <instance_reference name="weapon_to_override" value="" /> <uniqueid name="id" value="1073754250" /> <bool name="auto_attack_only" value="True" /> <bool name="persist_on_weapon_change" value="True" /> </template_reference> </list> </group> <enum name="activation" value="always_on" /> <bool name="can_interrupt" value="True" /> <bool name="can_target_in_fow" value="False" /> <float name="caster_close_in_distance" value="2" /> <bool name="casters_can_evacuate" value="False" /> <group name="cost"> <float name="action" value="0" /> <float name="command" value="0" /> <float name="fuel" value="0" /> <float name="manpower" value="0" /> <float name="munition" value="0" /> <float name="popcap" value="0" /> </group> <string name="cursor_ghost_blueprint" value="" /> <float name="cursor_ghost_blueprint_angle" value="0" /> <bool name="disable_combat" value="False" /> <bool name="disable_when_active" value="False" /> <float name="duration_time" value="3" /> <bool name="enable_in_building" value="False" /> <bool name="enable_in_vehicle" value="False" /> <bool name="engage_combat" value="True" /> <float name="entity_busy_time" value="0" /> <float name="facing_angle" value="5" /> <bool name="facing_ignore" value="False" /> <float name="final_close_in_distance" value="0" /> <bool name="fire_and_forget" value="False" /> <bool name="garrison_target" value="False" /> <bool name="has_speech_code" value="False" /> <float name="initial_delay_time" value="10" /> <bool name="initial_recharge" value="False" /> <bool name="is_default_action" value="False" /> <bool name="move_back" value="False" /> <float name="move_back_distance" value="10" /> <float name="range" value="0" /> <bool name="range_ignore" value="True" /> <float name="recharge_time" value="0" /> <bool name="refundable" value="True" /> <bool name="require_no_shot_block" value="False" /> <enum name="shared_timer" value="" /> <bool name="shared_timer_player_wide" value="False" /> <group name="speech_code_2"> <string name="code_1" value="hf" /> <string name="code_2" value="" /> <string name="code_3" value="" /> </group> <group name="speech_code_3"> <string name="code_1" value="" /> <string name="code_2" value="" /> <string name="code_3" value="" /> </group> <enum name="squad_caster" value="one_entity" /> <enum name="target" value="tp_squad" /> <group name="target_special_validation"> <template_reference name="target_special_validation" value="type_ability_target_type\all"> </template_reference> </group> <float name="toggled_recharge_time_off" value="0" /> <float name="toggled_recharge_time_on" value="1" /> <group name="ui_cursor"> <string name="cursor_bad" value="modal_ability_cancel" /> <string name="cursor_good" value="modal_ability" /> <string name="cursor_nonmodal_good" value="" /> </group> <group name="ui_info"> <locstring name="extra_text" value="0" /> <locstring name="help_text" value="0" /> <string name="hotkey_name" value="P" /> <icon name="icon_name" value="Icons_abilities_ability_common_face_team_weapon" /> <string name="overlay_name" value="" /> <bool name="reveal_for_decryption" value="False" /> <locstring name="screen_name" value="0" /> <icon name="icon_alternate_name" value="Icons_abilities_ability_common_cancel_face_team_weapon" /> <locstring name="brief_text" value="0" /> <locstring name="help_text_alternate" value="0" /> <locstring name="screen_name_alternate" value="0" /> <locstring name="screen_name_short" value="0" /> </group> <locstring name="ui_usage_txt" value="0" /> <bool name="validate_actions" value="False" /> <list name="global_self_actions"> </list> <list name="requirements"> </list> <enum name="ability_super" value="tp_none" /> <int name="ui_position" value="23" /> <bool name="ui_mini_map_capture" value="False" /> <bool name="facing_ignore_during_active" value="False" /> <instance_reference name="ui_range" value="" /> <instance_reference name="ui_reticule" value="" /> <float name="ui_reticule_radius_min" value="1" /> <float name="ui_reticule_radius_max" value="1" /> <enum name="pending_ability_out_of_range_behaviour" value="chase" /> <enum name="ui_group" value="group_primary" /> <string name="ui_targetable_sm_key" value="" /> <string name="ui_targetable_on_key" value="" /> <string name="ui_targetable_off_key" value="" /> <enum name="ui_targetable_receiver" value="local" /> <enum name="ui_combine_type" value="intersection" /> <enum_table name="ui_modal_highlight"> <bool name="world_sector" value="False" /> <bool name="map_sector" value="False" /> <bool name="map_sector_hq_link_extender" value="False" /> </enum_table> <enum name="ui_group_cast_type" value="multi" /> <list name="requirements_target"> </list> <template_reference name="targeted_ability_option" value="options\none"> </template_reference> <enum name="ui_direction_requirement" value="nondirectional" /> <instance_reference name="cursor_ghost_ebp" value="" /> <bool name="can_cast_whilst_constructing" value="False" /> <list name="requirements_self_recharge"> </list> <bool name="can_cast_outside_active_battle_field" value="False" /> <bool name="ability_super_event_cue" value="False" /> </group> <uniqueid name="pbgid" value="1073741940" /> </instance> This is a modified clone of the okw_ratken_vehicle_hold_fire_mp toggle ability. You can change the bangalore unit type to vehicle. I believe the only changes are the requirements, start_self_actions, and activation. I'm not entirely sure what the exact issue of your ability is but ensure that it is given to the entity that is holding the RPG. In: Modding and Tools