Right now, exported standard Q3 maps converted via q3map2 open fine in NetRadiant, but moving a wall makes it crash because it can't handle the texture transform. So something is wrong. Could be just that standard Q3 textures aren't fully supported by io_export_qmap => try using qbsp to convert from Valve220 to Brush Primitves.

Right now I use special "search" operators bound to buttons next to the text field(s), but that seems rather hacky. Blender 2.93's randomize attribute geometry nodes have a text field which shows suggestions once you type, with an extra suggestion marked with a "+" icon for exactly what you typed. That's exactly what I'd need here.

See comment here:

Not sure how to do this. Last time I checked there was no way for Blender addons to listen to "events" such as the user selecting something in a drop-down menu. One option would be an additional button that needs to be pressed to "lock in" one's selection, but that is outrageously stupid.

Right now, the logic for inclusion in the map is:

• all mesh-type objects that don't have mesh_as="NONE" (or MODEL because that's not implemented yet)
• even those meshes that do have mesh_as="NONE" if they have an entity classname or entity key-value pairs set
• objects of any other type if they have an entity classname or entity key-value pairs set

Perhaps it would be better if, in addition to that, there was a global "include in map" flag at the top of the BlendRadiant properties for easily switching "off" certain objects without having to change any of their properties?

Right now there are a lot of terms like "non-brush" / "brushless" entities - in entities.ent, these are simply called "point" entities, in contrast to "brush entities" which are called "group entities".
I think "brush entities" is pretty established, but the other thing should definitely be called "point entities".

E.g. if it's a number, show Blender's native integer thing, etc. Types are defined in entities.ent for each key.
Perhaps that would require moving it out of template_list, but that's fine by me, anyway.

entities.ent defines dimensions for point entities. Meshes in Blender marked as Mesh as: Nothing but with entity stuff set could be scaled so their bounding box matches these dimensions.

I.e. you eyedrop on another object and if it has an entity targetname defined, that will be used as the target.

Either via external conversion (q3map2 or qbsp) or better by directly writing out in this format. Requires better understanding of texture maths though.

Naming of classes etc. is all over the place... some use Blender's recommendations, others don't. Look up how to name what and fix.
Also, all operators etc. should have the blendradiant_ prefix (BlenderKit does it that way, makes sense).

UI for setting these has been built, now for the actual export...

Right now, high-level modifications to objects (e.g. applying modifiers) are made by duplicating them first right before the export so the original remains untouched, then deleting them after the export is complete. This is a bit stupid as it does modify the scene itself and if something goes wrong, there will be leftover duplicates polluting it.

A bettter approach would be to do something like suggested here, save the entire scene somewhere else and operate on that copy. AFAICT the "Save As Copy" function could be used for that (save in some tmp dir), followed by launching a new Blender instance in batch mode as a subprocess to operate on that copy. This would leave the original scene entirely untouched.

Would help with #3.

I.e., mesh_as= *anything brush* => only group entities, mesh_as=NONE (or not a mesh) => only point entities.

Part of #15.

For gamepacks, should use the load_according_to_prefs() method introduced in 1f768ae.

Would be good to do this for gamepacks before implementing caching itself (#15) for entities because it makes clear which methods are required on these Cached... classes.

Right now they are reloaded on each redraw (I think) => horrendously inefficient.