New DLL callbacks - any requests?

[Red Devil]

apologies if i have requested this already:

a callback to dynamically detect/increase/decrease water/lava level, please.

[Ded10c]

apologies if i have requested this already:

a callback to dynamically detect/increase/decrease water/lava level, please.

Seconded. That would be nice to see.

[Nielk1]

A method to call editor only commands from the DLL in a way that prevents them from being called in any other way (as per running in bzone.exe) would be a better way to say that. The issue of course is that these functions are probably currently entirely isolated into bz2edit.exe and making a separate set of accessible functions would be quite difficult.

I made a request, but 701, for a function badly needed to fix many old mod missions with a note on what is needed to actually implement it. I may end up with more over time that I need to fix things.

[General BlackDragon]

A parallel to DLLEXPORT void DLLAPI SetLifespan(Handle h, float timeout);

float DLLAPI GetLifeSpan(Handle h);

[mase]

Is there any way to get information about the geometry of objects?
Like collison box/sphere?

[DarkCobra262]

Is there any way to get information about the geometry of objects?
Like collison box/sphere?

collision for objects is based on their animations (Turret rotating included)... generally are a giant box unless there's a specific collision mesh (I believe that's how it works I believe.. GBD or various others might be of more help)

[Red Devil]

place an object in the editor, toggle the console with Ctrl + ~ and type in debug.collisions, then toggle the console again.

[Zero Angel]

Is there any way to get information about the geometry of objects?
Like collison box/sphere?

collision for objects is based on their animations (Turret rotating included)... generally are a giant box unless there's a specific collision mesh (I believe that's how it works I believe.. GBD or various others might be of more help)

Actually, BZ2 uses sphere-based collisions for everything except buildings, this includes object-object collisions and object-ordnance collisions. Think of the effect radius of the shields on scion units. This almost completely corresponds with their actual collision spheres -- it also explains why you can't 'ride the bomber'.

There are ways to override the object-ordnance collision in the ODF to use boxCollide=1 in the ODF. Scouts and tanks can be given boxcollide to make ordnance (like cannons, guns and missiles) to accord more with the 'unit selection box' when you select the unit, but it makes everything way too hard to hit, especially on thin units like the scouts and especially in multiplayer where the big hit spheres make up for the natural lag/warp that occurs.

[DarkCobra262]

Is there any way to get information about the geometry of objects?
Like collison box/sphere?

collision for objects is based on their animations (Turret rotating included)... generally are a giant box unless there's a specific collision mesh (I believe that's how it works I believe.. GBD or various others might be of more help)

Actually, BZ2 uses sphere-based collisions for everything except buildings, this includes object-object collisions and object-ordnance collisions. Think of the effect radius of the shields on scion units. This almost completely corresponds with their actual collision spheres -- it also explains why you can't 'ride the bomber'.

There are ways to override the object-ordnance collision in the ODF to use boxCollide=1 in the ODF. Scouts and tanks can be given boxcollide to make ordnance (like cannons, guns and missiles) to accord more with the 'unit selection box' when you select the unit, but it makes everything way too hard to hit, especially on thin units like the scouts and especially in multiplayer where the big hit spheres make up for the natural lag/warp that occurs.

ahhhhhhhh, learn something new every day.. mostly XD

[vlad_C0M]

Maybe it will be sometime realized. I suggest to make "timed powerups."
With "backup.lastweapon".
And as with opportunity to specify, instead of "backup.lastweapon" any g*.odf

it will open great opportunities for modmaking. And not only.

[mase]

place an object in the editor, toggle the console with Ctrl + ~ and type in debug.collisions, then toggle the console again.

Interesting, I only just saw your post. But I don't think there is a way to read this information out by dll is there?

[Red Devil]

no, it might be useful to do so, but it would be a *lot* of information

[General BlackDragon]

If there could be made a version of GiveWeapon(Handle h, char Weapon, int Slot); that took in a specific weapon slot to give it to, then the DLL could easily do that timed powerup thing.

[Nielk1]

If there could be made a version of GiveWeapon(Handle h, char Weapon, int Slot); that took in a specific weapon slot to give it to, then the DLL could easily do that timed powerup thing.

I think in general 2 features that would open up a lot of power is direct access to weapon slots by DLL and more direct access to the factories (what they are building and if they are busy for example). I do not believe you can easily do either.
I would say setting power states of buildings would be nice, but you can do that already by spawning and despawning and attaching and detaching taps via the DLL.

[General BlackDragon]

You can easily read the files of each weapon slot, the only lacking thing is a giveweapon that specifies a slot number