git.xonotic.org Git - xonotic/xonotic-data.pk3dir.git/commit

]> git.xonotic.org Git - xonotic/xonotic-data.pk3dir.git/commit

projects / xonotic / xonotic-data.pk3dir.git / commit

author	bones_was_here <bones_was_here@xonotic.au>
	Sat, 3 Jun 2023 18:01:22 +0000 (04:01 +1000)
committer	bones_was_here <bones_was_here@xonotic.au>
	Sat, 3 Jun 2023 18:18:06 +0000 (04:18 +1000)
commit	927b760f9f7b29ca15195db9089779ee37c8791e
tree	516b39edf097e97ca484ad980653d82c7a9ca2a2	tree \| snapshot
parent	de73cb2cbef247dc616e02166e3b686f2d4a934b	commit \| diff

Fix trigger_push and trigger_impulse prediction

It's a bit awkward that some triggers require the model field unset and
others require it unchanged, so rather than having duplicated code that
restores it after it was unset, an argument is added to control that
behaviour.

This should have been included in 2b46f62db61e8ca869fc591d9ebe4053c3e876d7
and/or 0f843f8c9e7891ba3029ac5a18c6ebebde3a30da

See also: https://gitlab.com/xonotic/xonotic-data.pk3dir/-/issues/2838

RSS Atom

qcsrc/common/mapobjects/func/ladder.qc		diff \| blob \| history
qcsrc/common/mapobjects/trigger/impulse.qc		diff \| blob \| history
qcsrc/common/mapobjects/trigger/jumppads.qc		diff \| blob \| history
qcsrc/lib/warpzone/common.qh		diff \| blob \| history
qcsrc/lib/warpzone/server.qc		diff \| blob \| history
qcsrc/lib/warpzone/util_server.qc		diff \| blob \| history
qcsrc/lib/warpzone/util_server.qh		diff \| blob \| history