2025-07-20 22:15 CEST

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0004169Spring engineGeneralpublic2014-01-26 09:26
ReporterPepeAmpere 
Assigned TojK 
PrioritylowSeverityfeatureReproducibilityalways
StatusresolvedResolutionreopened 
Product Version95.0.1+git 
Target VersionFixed in Version 
Summary0004169: add Spring.GetUnitCollisionVolumeData(unitDefID) or access default col values in UnitDefs
Descriptionif given unit wasnt added/spawned/created in given game yet, widget/gadget is not able to get collision volume data for given unitDefID/unitName for some own needs.

we store(d) such default values for model (radius, height - due wiki) in UnitDefs, so "it can be changed later by gadgets" is kind of excuse argument why dont have collision values there, too :).

Generaly i would expect i find all standard defs from unit definition file in UnitDefs (with naming desync i can live :)

Btw i suggest similar function or table data for Features, too.



TagsNo tags attached.
Checked infolog.txt for Errors
Attached Files

-Relationships
+Relationships

-Notes

~0012210

jK (developer)

why?

~0012213

PepeAmpere (reporter)

i need to know init values given to object before its created

so storing DEFAULT values of hitsphere in UnitDefs seems to me reasonable, because its just another property which comes from definition of unit

~0012214

PepeAmpere (reporter)

and if you ask "why it is so important?" - hitspheres is main engine mechanic from general final behavior of game view, it changes the feeling of player, result of mass actions, etc. so much, so i think game developer should have more control above it. If game developer knows what he can expect from engine (in this case size and type of sphere unit gets after creation), he can more control the output behavior of game.

~0012215

silentwings (reporter)

Last edited: 2013-11-26 16:26

View 2 revisions

But what's wrong with triggering whatever behaviour you're trying to achieve with UnitCreated? E.g. the DCV gadget.

Imo its confusing to have this in unitdefs since its really a property of the unit - for some units it even changes dependent on their current state.

~0012216

PepeAmpere (reporter)

for example the unit is never UnitCreated? :)

~0012217

PepeAmpere (reporter)

or its created long after i need to know the setup

~0012219

jK (developer)

1. you didn't named a reason
2. all data is available in the unitdefs

~0012220

PepeAmpere (reporter)

ad 2.: where?
+Notes

-Issue History
Date Modified Username Field Change
2013-11-26 05:08 PepeAmpere New Issue
2013-11-26 08:00 jK Note Added: 0012210
2013-11-26 16:13 PepeAmpere Note Added: 0012213
2013-11-26 16:17 PepeAmpere Note Added: 0012214
2013-11-26 16:20 silentwings Note Added: 0012215
2013-11-26 16:22 PepeAmpere Note Added: 0012216
2013-11-26 16:23 PepeAmpere Note Added: 0012217
2013-11-26 16:26 silentwings Note Edited: 0012215 View Revisions
2013-11-26 22:26 jK Note Added: 0012219
2013-11-26 22:26 jK Status new => closed
2013-11-26 22:26 jK Assigned To => jK
2013-11-26 22:26 jK Resolution open => no change required
2013-11-27 00:43 PepeAmpere Note Added: 0012220
2013-11-27 00:43 PepeAmpere Status closed => feedback
2013-11-27 00:43 PepeAmpere Resolution no change required => reopened
2014-01-26 09:26 jK Changeset attached => spring develop 05eaad70
2014-01-26 09:26 jK Status feedback => resolved
+Issue History