You're right, the monster declarations lack the model definition.
This one's easy, but then there's stuff like func_clock, func_counter and func_spawn that have a box that's bigger than the usual sized ones (especially func_spawn_small which is ironically bigger than the usual func_spawn), so I guess there's a model that needs to be attached?
But in the end I guess those models not showing up in TB doesn't matter, because the core coding comes from the qc files, and the fgd file's just here for clarification. I'll still declare the monster models though. 

whether these entities are supposed to have models or not. The size of the box (in the editor) is determined in the def / fgd files also. All that TB knows about entities comes from these files. It doesn't read anything from anywhere else except the model(s) if they are declared in the def / fgd file. 

This means fteQCC, because of computer magic, doesn't work for me anymore.

There is no such thing as computer magic, just computer things-you-don't-yet-understand.

Are there any absolute pathnames in your progs.src file?

What output is FTEQCC giving you in the command prompt? Did it stop working after only changing the directory name, or did you also blindly paste a ton of Hipnotic code in with it and expect it to work?

According to the GMQCC output, there's an error in weapons.qc on line 62. Did you investigate this? 

I just changed the mod directory name, I didn't move fteQCC or any other files out.
And the software just loads for eternity until I reboot the laptop. Task Manager can't find it when this happens. This happens for both the DOS exec and the interfaced exec. Some people told me it's dependant on another program but I don't know how to find this out.
As for line 62 of weapons.qc, it has a problem with old_velocity, but it's definied in hipdef.qc, which has been added to progs.src, so I don't know what's the deal here. 

http://ejesa.statig.com.br/bancodeimagens/67/2i/tk/672itke03ty4qrk5w6prcj2tc.jpg 

 

 

There is no such thing as computer magic

All that wishing for nothing. 

I just had two pounds and an ounce of laugh. 

There is no such thing as computer magic

No white magic, at least. 

Have you tried undoing the change that resulted in this? If that doesn't work, this would indicate that you did in fact change more than just the directory name, but you didn't notice or forgot, or maybe deem unrelated. 

I think changing the name actually made an impact on fteQCC.I can't retry renaming the directory and run fteQCC, as I've tried to run it this morning and is without a doubt still trying to load at this moment, and I don't want to reboot my laptop right now. Maybe tomorrow. 

He didn't ask you what you think, he asked you to do the one thing that would prove your theory.

How long does your laptop take to reboot, exactly? 

I'll try it now, I didn't want to do it at first cause I wanted to work on that start map 

Must be the fteQCC execs. I'll reboot now to take them away. 

Tried to delete the fteQCC execs, but it doesn't want to.
What the hell! I was sure they would go away if I rebooted.
Then there has to be another program at work, but what is it? 

Might be time to launch this laptop into the fires of Mordor and try again ... 

Isn't there a way to know which program uses other programs? Cause everytime something like this happens I can't help but say to myself "Yes but WHAT PROGRAM?" 

Google? File unlocker or sometime. 

By checking the old fteQCC program that's still lying there, it says the one program that's locking is System.

Oh...
This doesn't sound good at all, doesn't it? Especially unlocking fteQCC would mean to close System as well...

I also checked the fte compilers I downloaded earlier this day and it says they aren't locked. However when I execute them System locks them away.
Is there anything I can do about this? 

 

OK. 

 

The school bus guy? 

The compiler is just one small program though that gathers up your qc files and spits out a progs.dat.

I tend to have multiple copies (one per project) of it all over the place just for convenience.

Even so, this sounds like OS crap. Are you using something toxic like Vista or something? If not, what about your antivirus or possibly DeepGuard - even spyware scanners can lock up a potentially dangerous program (for example, one which compiles files from others...)