-
-
Notifications
You must be signed in to change notification settings - Fork 203
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement CGib::SpawnHeadGib
and CGib::SpawnRandomGibs
#650
Implement CGib::SpawnHeadGib
and CGib::SpawnRandomGibs
#650
Conversation
CGib::SpawnHeadGib
and CGib::SpawnRandomGibs
It's useless. Any entity can be created using rg_create_entity. |
Then let's create natives for each entity. rg_spawn_defuser rg_spawn_hostage rg_spawn_weaponbox ... |
Not sure if you are serious or not but did you even tried to do what are you implying? Based on what you say there are plenty of things that are implemented on ReAPI that can be done through members, entvars or create_entity, you are not forced to use these natives but then stick to your own methods, things like these makes programming easier for the end user. |
No need for rubbish api with unnecessary natives. That's why today's programmers are so lazy. |
Your argument is pretty vague honestly, again, based on your statement just keep RegisterHookChain/set/get_entvar and set/get_member and just let people do their job in a hard way? Maybe you should go and google what is a Framework or how libraries/API works, maybe you will notice a common pattern which is making programmer life easier, by the way not everyone is cappable of making a functional code even with everything ready or how to use on their respective docs. #636 this is easily programmable. Just to contribuite this Pull Request, this is part of complementing this implementation by fl0werD rehlds/ReAPI#164 just to make everything chained and functionally without workarounds. |
Absolutely wrong comparison. It looks like you yourself do not know what api is. Try to do something first |
"#555 Hey this can be made too!" you won't do it. all my commits are made to exclude amxmod dependency. |
your api is only needed for one plugin. don't be smart here |
In fact I do not need anything from ReAPI/ReGameDLL because it already offers what I need. Uhm yeah, making random spawns is pretty easy through AMXX, I am not trying to be smart or anything, just making a point on your argument (can be considered as that? seems just a complain for nothing), you have good pull request and issues, not gonna lie, but your statement regarding this one just make nonsense, please, take a look at ReGameDLL and ReAPI main page, pull request are welcomed and are presented as a powerful and extended API for mods/plugins. ReGameDLL goals:
Instead of not adding content just because it it useless (?), if you do not need it, just do not use it, more people will find it useful and whoever has a use will be grateful for this implementation rather than searching for a workarounds. |
@metita I will not argue with a fool. good luck |
By the way, I tried to have a good discussion with you but looks like I was not wrong at all with your attitude, sadly. |
"Uhm yeah, making random spawns is pretty easy through AMXX" show me at least one normal random generator. you have no idea how it works. |
Yes, how dare they make their job easier! |
"#600 You seems to be a crybaby, noticed some pattern there too, don't give up))" I love that! Hehehe! About the submition of those gib functions, well, more functions we have, better this is. And adding some in that structure is not gonna hurt, especially knowning the internal code of those gibs functions can call a lot of things and at the end, this will make programmers job easier... But obviously we have to avoid puting "duplicate/similar" code already existing on other binaries (for simplicity), which can also maybe make the coders a bit lost. So yeah, those functions should be added. |
CGib::SpawnHeadGib
and CGib::SpawnRandomGibs
CGib::SpawnHeadGib
and CGib::SpawnRandomGibs
related rehlds/ReAPI#200