Advertisement
Guest User

Untitled

a guest
Jul 22nd, 2012
92
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 2.21 KB | None
  1. auREAX | FR: config flag to apply fix_rollback globally
  2. renpytom | ?
  3. auREAX | without having to call it after each choice
  4. auREAX | feature request (FR).
  5. renpytom | auREAX, features that annoy players should annoy creators. :-)
  6. Edwin_ | :-)
  7. auREAX | so why have fix_rollback in the first place then
  8. auREAX | :-)
  9. Edwin_ | That's how I initially implemented it
  10. Edwin_ | I suppose you can add it yourself in one strategically place line
  11. renpytom | There are times when a choice is so important that the developer demands it be fixed.
  12. renpytom | I just think that it's something that needs to be considered.
  13. auREAX | hence why it's a config flag and not mandatory globally
  14. renpytom | It's too easy for a config flag to be just slapped in a template somewhere.
  15. auREAX | yes, easy is probably the goal I'm going for here
  16. auREAX | y'know, as opposed to adding a pycode statement after each choice option
  17. renpytom | The problem is that I tend to accidentally make wrong choices on a semi-regular basis.
  18. renpytom | so when a game disables rollback, I curse under my breath.
  19. renpytom | If I hadn't saved recently, it's above my breath.
  20. auREAX | well perhaps you should slow down on choices then
  21. auREAX | also if that's the case there's no need for fix_rollback in the first place
Advertisement
RAW Paste Data Copied
Advertisement