Progress Report

[ZoriaRPG]

Like I said; none. Just an empty script.

Most of those things are all the same thing though. It's not like NPCs in RPGs are really complex until you add in messages with events, etc. But even those are only run when activated so I don't think it'll matter much.

The way rpg maker, game maker, et al. do it is everything is a "god object'. ex; an npc is an event is an sprite is an waypoint is a object is a battle character, etc. IMHO this is the worst kind of abuse of OOP design, and is just bad to do whenever performance is an issue. I'm not doing this at all. I'll be putting in small, specialized cases. If you want a warp event at location x,y, you don't put a particle system or NPC there, you put a warp there. It's just common sense. Only a player can interact with warps so that's instant "optimization" if you want to think about it like that. I just think of it as sane.

Speaking of god objects, here's a true story. I was looking at a platform layer for mobile a while back, came across cocos2d; apparently it's really popular, anyway--cutting to the end: The sprite class alone was like 1.5 kilobytes, allocated a bunch of stuff, had like 4 matrix4 transformations, and was virtual, and hierarchical. If you think I am full of shit when I say that everything is shit these days, just go take a look at that.

...but just about everything is shyte. That's just a fact.

People don't care if what they make has good performance. They just tell you to buy a faster, more powerful system, which is rubbish. I occasionally do that too, but it's very minimal, and only because when things I make demand something faster/better/newer, it's faster/better/newer than ten-plus years ol; and then only because whatever I'm using as a base requires it, with all my modifications pushing it to its limits.

I'm not about to go back to doing things in raw assembly though.

To clarify my earlier question: How many other objects do NPCs examine to gauge interaction, their movement, and such? Do they consider other NPCs as a factor, as that is something that I would expect to cause exponential performance hindrance.

[Gleeok]

I'm not about to go back to doing things in raw assembly though.

I actually just realized that I could do generics in c or c++ without template crap, function pointers, or switch cases. For example:

inline void InvokeSomeFunction(void* obj, void* f, void* param0)
{
	__asm
	{
		push param0
		mov ecx, obj;
		call f
	}
}

Stupid crap like 'type safety' 'iso standards' is just getting in my way. haha ..Oh boy and think of all the MACROS ! :)

.
To clarify my earlier question: How many other objects do NPCs examine to gauge interaction, their movement, and such? Do they consider other NPCs as a factor, as that is something that I would expect to cause exponential performance hindrance.

I've actually never had collisions as a bottleneck so I am literally zero-worried about that. Since 2D rpgs probably have the least collisions of any game I'll probably just use brute force as a placeholder to be honest.

As for what can collide with what, you're welcome to request something. I was thinking of throwing in filter mask for now.