Skip to content

Conversation

carl3175
Copy link

@carl3175 carl3175 commented Oct 4, 2025

Changes proposed:

  • Fixed the issue where the player's field of view would drop towards the ground when entering the game and clicking to ride a vehicle after writing the corresponding data to vehicle_template_accessory, vehicle_accessory, and npc_spellclick_spells.

Issues addressed:

None

Tests performed:

Tested for switching back and forth between a single vehicle and multiple vehicles.

Known issues and TODO list: (add/remove lines as needed)

  • None

…be incorrect after boarding a vehicle

Fixed the issue where the player's field of view would drop towards the ground when entering the game and clicking to ride a vehicle after writing the corresponding data to vehicle_template_accessory, vehicle_accessory, and npc_spellclick_spells.

Tested for switching back and forth between a single vehicle and multiple vehicles.
@mdX7
Copy link
Member

mdX7 commented Oct 5, 2025

is the sending of the related packets sniff confirmed?

@carl3175
Copy link
Author

carl3175 commented Oct 5, 2025

I'm sorry, I'm not a real programmer and I don't know how to confirm the sending of relevant data packets. I often encountered this issue during the previous quests repair process, so I just hope to fix it as soon as possible.

aquadeus and others added 7 commits October 5, 2025 22:19
…be incorrect after boarding a vehicle

Fixed the issue where the player's field of view would drop towards the ground when entering the game and clicking to ride a vehicle after writing the corresponding data to vehicle_template_accessory, vehicle_accessory, and npc_spellclick_spells.

Tested for switching back and forth between a single vehicle and multiple vehicles.
In many quests, it's necessary to use the SMARTAI_TARGETS with TARGET_INVOKER_ SUMMONED_ENTRY as the target in SAI.
It takes the Entry of the summoned creature that triggered the event as the parameter and has been tested in SAI.
…se ConditionValue3 as a criterion for determining the number of halo layers a player possesses.

Improve the CONDITION-AURA trigger condition to use ConditionValue3 as the criterion for determining the number of halo layers a player possesses. When the number of halo layers a player possesses is greater than or equal to ConditionValue3, the condition will be triggered.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants