Small fix for CanBeDamaged function

[pinco]

The canbedamaged function never control if the mobile is alive or not.

You can found the standard function in mobile.cs at line 4900 about...:

 
public virtual bool CanBeDamaged()
{
return !m_Blessed;
}

overwrite the function with this new one:

 
public virtual bool CanBeDamaged()
{
return !m_Blessed && Alive;
}

recompile and the bug is solve

[pinco]

I didn't like the overwrite if I can change the original...

[Greystar]

Originally Posted by pinco

I didn't like the overwrite if I can change the original...

I just responded the way I did since a modified core can prevent you from getting support, that is all. I don't care personally either way...

[Phantom]

Originally Posted by pinco

I didn't like the overwrite if I can change the original...

But there is NO reason to modify the core when you can avoid it.

[pinco]

lol my core is completely modified :P

[autumntwilight]

you do know it should be public virtual bool... not publicvirtualbool lol

[pinco]

I know, but in the copy & past the space was trimmed -.-

[Shadow1980]

Originally Posted by pinco

I know, but in the copy & past the space was trimmed -.-

So you post a core change, imo a quite significant thing to do, and you don't even put down correct code.
It doesn't take all that much work to put the spaces back in...

I have to agree with Greystar / Phantom as well, why would you bother making a core change if you really don't have to??

[pinco]

1) I have corrected the post
2) I dont told you to do the modding, if you like it, do it, else do everything you want, we are in a free cuntry
3) I dont read posting limitation in this forum, if you dislike my suggestions I take for myself, no problem, I gain nothing to post here.

[psz]

This forum is for discussing and posting core changes. That's what he did.

[Shadow1980]

Originally Posted by pinco

1) I have corrected the post
2) I dont told you to do the modding, if you like it, do it, else do everything you want, we are in a free cuntry
3) I dont read posting limitation in this forum, if you dislike my suggestions I take for myself, no problem, I gain nothing to post here.

1) Good job.
2) I never said you shouldn't post the change, but when you do it's good to get it right.
3) Que?

Originally Posted by psz

This forum is for discussing and posting core changes. That's what he did.

And we discussed it as well. I don't see the problem.

The only reason I replied is because I dislike it when people post a "fix" that can have a rather significant impact on somebodies files, and then don't even post correct code.
I know, people should be able to spot this themselves but we all know there are plenty of poeple here who only download/use other people their changes and files and who know practically nothing about RunUO or coding. Even though I personally think those people don't really belong in the community, we have to give them a chance to start somewhere and provide them with clear and accurate information. Nothing is worse then learning from incorrect code.
Just my 2 cents.

[psz]

Incorrect code is a problem, yes.

As for severely impacting the code, that's kinda what the forum is for ;-> If someone's reading this forum, they are already editing the core most likely.

[Zippy]

Lets everyone try to be nice, mmk?

[noobie]

i think it is more "appropriate" to do it in the core logically..
if you are so afraid to modify it, why even does this forum exist

[Ohms_Law]

quit trolling

[jpmythic]

I know this is an Old Post, but I thought I'd mention that in AOS.cs:

		public static int Damage( Mobile m, Mobile from, int damage, int phys, int fire, int cold, int pois, int nrgy, bool keepAlive )
		{
			if ( m == null || m.Deleted || !m.Alive || damage <= 0 )
				return 0;

It does a basic check for Alive status on general Damage types.
BUT, changing it in BaseCreatures.cs can affect the majority of them, and then you can overide in the few others that Create Mobiles from Base Mobile.cs

Otherwise, you can just do it in the Core or Create your OWN Mobile.cs that
Inherets from Mobile.cs and takes the Place of Mobile.cs for the Other Files.
Altho I think this has been discussed many times before.

'my two cents worth'

[XxSP1DERxX]

The reason why this was not put into the core is just for that reason. Maybe someone wants to make a dead mobile which can be damaged.... I dunno why, but just maybe. It is NOT a bug because the check is in AOS.cs like you stated, where if the CanBeDamaged function fails, the Alive check will correct it once they are attempted to be damaged.

mobile.Damage() -> Aos.Damage, so there is no reason for this modification at all.