you literally just said not to assume the rules are static. what's the opposite of static rules?
For mother ****ing sakes do I need to spell it out for both of you "software developers"?
If you have an abstraction or interface, it may or may not be implemented and can be derived.
If an interface or abstraction is enforced on this system for every dungeon, each dungeon could have a unique implementation of said contract. By no means would this involve any artificial intelligence because the developers could simply override or use existing rules from the base implementation (if one exists).
I'm sure we're both very glad we don't work with each other. The above is really basic knowledge; I used the terms interface and abstraction intentionally as they're well understood by anyone that goes onto stackoverflow for work or school.
Last edited by SendohJin; 06-28-2017 at 06:03 AM.
|
|
![]() |
![]() |
![]() |
|
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.



Reply With Quote


