ZDoom

It's terrible for code readability, it's terrible for an open project that accepts contributions from people of all levels of programming, and it's terrible practice in general. If you're still doing that professionally, don't tell me what work you've published because I want no part of that! It ...

Armchair developer indeed. It was hard reading through that tirade with the vast majority of it just showing a profound lack of understanding. Understanding of what, exactly? Let's break it down here , Maybe we can get somewhere, I have done my best to make the initial post descriptive, May as well ...

Many of the suggestions made by me here are considered hacks, The reason for that is practicality, As i do not wish for breaking backward compatibility for existing modes. My suggestions - resorting to some hack'ish practices. There is a need to redesign much of the code but let's face facts, its ...

Solutions will be offered (They will be specific to simplify things but should be broaden to EVERYTHING in the project) Binary size - Current version of gzdoom 3.7.2 x86_64 for NTFS is standing on 8.5MB, How on EARTH did the developers let such a thing happen? With each extra byte , You are killing ...

One issue for you, personal opinion, Plasma rifle projectile is too opaque and the shape of it may need some rework.

Unsure if its a "code suggestion", But i would like to suggest to extend the zscript prototytpe (as well the internal engine function) of "RoughMonsterSearch" and "p_RoughMonsterSearch" to allow the acceptance of : "white-list/black-list of species" arguments and/or accepting/rejecting actor indices ...

That's pretty much the easiest way to debug, by printing out the variable. Here's a page you can use to convert from many types to a string for printing if needed. Well i guess i will have to deal with it with that method, not exactly what i had in mind but if there are no other ways, that will do ...

Quick question, Is there a way to debug zscript?

without debugging gzdoom project as a whole?
and without attempting to print out every variable i want to test?

What practices you guys use when it comes to writing zscript code and testing it?

I've already answered this in your previous thread, but TraceResult isn't exported out of the C++ code yet. If you do a Search for TraceResult in GZDoom's source code, you can see it used everywhere. But it hasn't been exposed for user ZScripts yet. Here's a list of what kind of data you could ...

Is there a way to query in zscript the player/actor's leg tracing collision with surfaces? (or the lack of (midair)) I was hoping for a flag that can tell me with what content/surface the actor leg trace(sprite's bottom plane) is interacting(colliding) with? I do know you can query info on the ...

Blue Shadow wrote:Math functions: https://zdoom.org/wiki/DECORATE_express ... _functions

Oh its in decorate, i was looking under zscript, THANK YOU!
yea i know its an extension to some degree but i forgot all about it, my bad.

Time for another question, Any support for C standard library math functions via callbacks on zscript? (sqrt, log and friends) that should be safe to add i believe, I am talking about callbacks in zscript that are directly linked to the c standard library under gzdoom. If so, how do i access them ...

1): No. A memset equivalent is far too dangerous in the context of a scripted language and 2): Again no. Since type sizes can vary depending on the current platform, making this available runs a high risk of breaking things. 3): Double can be formatted with String.Format or Console.Printf. 64 bit ...

Some questions regarding logging/IO , datatypes and structures 1.)Is there a memory set/zeroing function for variables of a given size (primitive datatypes/structures/arrays, all are the same pretty much), equal to the C memset standard function? so i won't have to use a pseudo-like copy constructor ...

Ok so this really got me ticked off , For someone with an existing mod that is trying to convert some stuff to zscript from decorate The first thing you will do is run a test-case once you have the proper gzdoom binary file that supports it 2.3.x onward, You will add a test file, add it to where ...