Fougerite Official 1.9.9.71
- Thread starter mikec
- Start date
This post can help you a lot http://fougerite.com/threads/c-plugin-development-guide.543/page-2#post-12179
It is as if it did not help ..... in link that I have sent you says:
In Visual Studio, you must use .Net Framework 3.5! You can do this by rightclicking on FougeriteTest, then Properties, and setting the target framework to 3.5!
and the newbie of you says below that you are compiling in 4.6.2 64bits .... if you really have a problem you must learn to listen! !
Not listening is like not wanting to learn
Last edited:
As above,
Compile in 3.5 and 32bit. Hope this solves your problem
If you still get errors create a thread (Might be useful to someone else if they are looking for how to compile)
Alright, hold on a sec let me fix that thing. Apparently there is a new ulink flood thing.
CommandEvent Error: System.MissingMethodException: Method not found: 'Fougerite.Player.SafeTeleportTo'.
lol?
I can´t test at the moment. I needed to delete my whole server because of the bugs, people are getting mad ! I installed Fougerite 1.5.1 and all is running fine atm. No bugs or else. If i update to your attached fougerite fix, and things are getting bad with it, the players would kill me !
Can anyone else pls test the attached file, and gimme feedback if it is running nice now or not ? Thx Guys !
I will take a look at it myself, but dunno when does that thing happen. Possibly at health change. No idea.
@McRustReloaded @salva @xandeturf
Even better. I tested this fully with python plugin calls. Everything seems to be perfect.
I changed NPCHurt, NPCKiled, PlayerHurt, EntityHurt, EntityDestroyed
to the takedamage event hook, and that one method processes all of them. This should save a lot of juice, and should be a lot more faster. I went through all of them, and tested the damageamount changes. All seem fine. The old code for them was pretty shit, It was from Magma. I'm afraid there are still codes that are from magma that i havent noticed yet.
PlayerKilled remained at the same spot, so you can still decide if you want to drop loot or not.
Even better. I tested this fully with python plugin calls. Everything seems to be perfect.
I changed NPCHurt, NPCKiled, PlayerHurt, EntityHurt, EntityDestroyed
to the takedamage event hook, and that one method processes all of them. This should save a lot of juice, and should be a lot more faster. I went through all of them, and tested the damageamount changes. All seem fine. The old code for them was pretty shit, It was from Magma. I'm afraid there are still codes that are from magma that i havent noticed yet.
PlayerKilled remained at the same spot, so you can still decide if you want to drop loot or not.