User talk:Cazomino05: Difference between revisions
Jump to navigation
Jump to search
Cazomino05 (talk | contribs) |
No edit summary |
||
| Line 3: | Line 3: | ||
* Will do, for the moment it's taking a back foot while I fix some bugs that cropped up in ped/weapon models should be fixed today though. --[[User:Cazomino05|Cazomino05]] 12:17, 20 September 2011 (CEST) | * Will do, for the moment it's taking a back foot while I fix some bugs that cropped up in ped/weapon models should be fixed today though. --[[User:Cazomino05|Cazomino05]] 12:17, 20 September 2011 (CEST) | ||
* Another thing i just remembered are glitches including setGlitchEnabled. They do very manual checks on weapons with certain characteristics e.g. being able to run with them, and do certain things to prevent glitching. This would need tidying up to not just look for certain weapon IDs, but for stats characteristics appropriately. Not only this, but some glitches are hardcoded to be fixed (i.e. cannot be accessed with setGlitchEnabled) that need accounting for too. --[[User:Talidan|Talidan]] 23:45, 23 September 2011 (CEST) | |||
Revision as of 21:45, 23 September 2011
Custom Weapon Stats Branch
- Nice work so far. Just remember to add to your to-do list that all utility functions need to be custom weapons ready, where appropriate. e.g. getSlotFromWeapon, or getPedAmmoInClip etc. Perhaps nothing needs to be done at all, it's just something to think about and look over. --Talidan 15:16, 17 September 2011 (CEST)
- Will do, for the moment it's taking a back foot while I fix some bugs that cropped up in ped/weapon models should be fixed today though. --Cazomino05 12:17, 20 September 2011 (CEST)
- Another thing i just remembered are glitches including setGlitchEnabled. They do very manual checks on weapons with certain characteristics e.g. being able to run with them, and do certain things to prevent glitching. This would need tidying up to not just look for certain weapon IDs, but for stats characteristics appropriately. Not only this, but some glitches are hardcoded to be fixed (i.e. cannot be accessed with setGlitchEnabled) that need accounting for too. --Talidan 23:45, 23 September 2011 (CEST)