killap is it safe to assume that bugs you labeled "Engine bug" (in the RP Bugs wiki) have been at least been
attempted to be fixed but failed to actually fix, by the community here?
If so that's a shame because some of these are rather significant
[spoiler:4f4ed83a90] Unlimited Ammo bug: Give an NPC several identical empty guns and appropriate ammo. Remove/trade other guns or ammo so they won't be selected. Set the NPC's combat choice to ranged. Select 'Use best weapon' then click on 'Talk'. Click on 'I need to talk to you about your gear' then 'Put your weapon away'. Select 'Trade' then manually unload their weapons. They now have more ammo than they started with. Repeat. Engine issue.
It's possible that when you or a companion enters a map you may be on the same space as an NPC. You won't be stuck though, so no worries. Engine issue.
NPCs are able to walk through locked doors. This is most often seen during combat. Engine issue.
Some companions, such as Vic, become unresponsive and act like walking containers. This is caused by the companion getting knocked out in combat and you leave the map during this. You need to go into combat mode again to let them 'wake up'. Engine issue.
If you have low unarmed skill and then miss on a standing fire gecko, the hit-n-miss animation won't play. Engine issue.
The floating text is rolling very furiously when some of your opponents lie unconscious in combat. Engine issue.
For the Educated Perk: It applies for the current level, *IF* you take it at the first time since leveling up at the character creation screen. If you click the character creation screen, cancel out of the perks list, close and reopen the character creation screen, and then select the Educated Perk, it DOES NOT apply to the current level. (Note: This bug goes back all the way to Fallout 1.) Engine issue.
Clicking your weapon at the exact moment that someone else initiates combat causes the button to remain "pressed in" graphically, and it doesn't release until you try to initiate combat again that way. Engine issue.
In the Pip boy, if you click status, click a city, then click somewhere else on the Pipboy screen, it'll load up another city's quest status. Engine issue.
If you give a critter tons of super stims in hopes of killing it, and then leave the map, the game will crash when it tries to kill the critter. Engine issue.
NPCs hooked on jet becomes utterly useless - stuck with 1 AP. Jet antidote doesn't work on them. Engine issue.
Ability to gain too high stats from drug use - use drug twice, save and load and you can use drugs to raise your stats even more. Engine issue.
Drugs used on one critter will affect all critters of that same type (i.e. look the same). Engine issue.
NPC's leveling up while under drug influence don't end up with correct stats - it checks the current stats and not base stats. Engine issue.
A game saved in combat where one of your NPC's has died will become corrupted. Engine issue.
Saving in combat is generally just a bad idea and will cause many unexpected problems. Engine issue.
Sometimes if you do an insta-kill to a critter (super critical hit, etc), code in their death procedure is not run and things regarding that character might be broken from that point on (e.g. no one recognizes the critter as dead). Engine issue. [/spoiler:4f4ed83a90]
