ZDoom

And back to our regularly scheduled "mostly fixes" releases :p zt-bcc might be entering a feature freeze phase, where I'll mostly only fix bugs and add very minor new features. Not many more features to add and there's a ton of bugs to be fixed so we can finally get another stable release. * Added ...

Two updates I forgot to post here. Another release dedicated primarily to fixes, but there's also a new feature. Sorry for the rather unstable code I churned out earlier. -Added #pragma pointer_space. Allows defining a default address space for pointers/references (ex: #pragma pointer_space global ...

A quick fix release. Better late than never.

Fixed broken module-scope struct/array reference type checking (Basically, & references were completely unusable unless they pointed to world/global space, as the equality check would always fail).

It's alright. That's something that over the years I've come to realize is, unfortunately, quite common.

I have to say this is incredibly cool 8-) :thumb: But I think the lack of replies is probably because its too advanced for most people to use; for everything but map manipulation we have ZScript and there's a lot of that which you can do with ZScript, especially as you can now create your own ...

Another alpha release. This has a very big focus on references/pointers and brings zt-bcc more up to par with GDCC in that aspect, including great benefits like using world/global arrays for dynamic memory allocation, interoperability with modules using pointers written with GDCC and more ...

It's a state literally called "held". It's run every tic you have the item. Like Pickup/Use on CustomInventory but instead run every tic an actor has said item.

This is kind of an evil hack, but the Held state (which I believe is also available on the Weapon class) allows you to call action functions on the weapon/item. You could maybe wrangle that in some way to use SetActorState on the weapon. The challenge here is that in this context, you don't have ...

No, this isn't possible (you can't really return a string from ACS to DECORATE, nor can you even pass in a dynamic value to A_Jump's target). You can just use SetActorState to achieve the same effect, though.

An alpha release. I still intend to do more with this before a full release, but here's a preview of the changes so far. Changelog: -Added libbcs.bcs. Currently provides malloc/realloc/free, dynamic array and C-style printf functions. -Added zcommon.acs, which simply imports zcommon.bcs. -Nullable ...

Updated. I added a Quake weapons mod. It's been a while, hasn't it?

I have one more mod I want to upload, but I lost the DEH9000 source to it and it's missing some important features. So once I remake it in DECOHack it'll be here.

That's great news then. I'll make a PR at some point.

Crosspost of my own post on the GZDoom dev channel. Yet another ACS question. I was thinking of adding pointers to module storage to ACS. Function pointers are already supported, but that's about it. You can't pass an array or variable by reference to a function or anything like that. While this can ...

To any Zandronum users, most of the constant definitions (except those for the lump reading API) are currently missing, this is a known issue (caused by yours truly ). Will be fixed for the next release, whenever that is.

On GZDOOM 4.10 does not work, as it gives these errors: Script error, "DoomFortress2_Beta_1.0.pk3:actors/tf_ammo.txt" line 93: Script error, "DoomFortress2_Beta_1.0.pk3:actors/tf_ammo.txt" line 93: Tried to define class 'DummyWeapon' more than twice in the same file. On Zandronum 3.1 it works fine ...