[Ronkkrop]

new Float:fpOrigin[3]
	new pOrigin[3]
	get_user_origin(id, pOrigin)
	fpOrigin[0] = float(pOrigin[0])
	fpOrigin[1] = float(pOrigin[1])
	fpOrigin[2] = float(pOrigin[2])
	new iEnts[20]
	new iEntity = find_ent_in_sphere(-1, fpOrigin, 200.0)
	find_sphere_class(0, "info_player_deathmatch", 20.0, iEnts, 20, fpOrigin)
	server_print( "found something %f %f %f", fpOrigin[0],fpOrigin[1],fpOrigin[2] )
	//

look at that. this tidbit of code is used to try and find out how find_ent_in_sphere and find_sphere_class work. Im doing it based on player location, but i seem to get tag mismatch everywhere even when i convert it to a float, and when i run hlds, i get bad load. Anybody know anythign about this? I need to be able to find a spawn point based on the location of a player. So any help would be great, mmmmmkay

Thanks for the help in advance.


Edit: im aware that the server_print shows nothing but the player origin as converted floats.

[DS]

Using only that code, I get 0 tag mismatches. The only warning I get is about an unused variable, but that isn't important. And as far as running it, I don't have any problems. Engine module enabled?

[Ronkkrop]

Yes it compiles like this, but it gets a bad load when you run hlds.

Edit: Yep, i did have engine module commented out, its been too long since i made amx scripts.

[Johnny got his gun]

Not sure that using find_ent_sphere() or anything that uses that function is good. Nowadays I usually just use find_ent_by_class() anyway and then just check the distance from one point or entity to another point or entity, using entity_range() or vector_distance(). I think that should be faster in most cases.