v1.0.3

git checkout -b nqtr-tool
git checkout nqtr-tool
git config pull.rebase false
git pull https://github.com/DRincs-Productions/NQTR-System.git v1.0.3 --allow-unrelated-histories

Now NQTR is a python library, and renpy interacts with it through easy-to-use functions.

What it means:

Pros:

• Performance
• I can now develop directly with python. this makes my life easier since I can use the tools to develop in python
• Can create tests
• From now on future versions will have less complex migration: since now I aim to modify as little as possible renpy functions , but only the library.

Cons:

• Sharing variables with renpy and the library is slightly more difficult because it relies on pointers. (As long as I only share dictionaries, I won't have any big problems).

Migrations

Use search and replace of vscode with regex functionality enabled

quest_start

• quests\["(.*)"\].start\(\)
• quest_start(id = "$1")

quest_nextStage

• quests\["(.*)"\].nextStage\(\)
• quest_nextStage(id = "$1")

quest_nextStageOnlyIsCompleted

• quests\["(.*)"\].nextStageOnlyIsCompleted\(\)
• quest_nextStageOnlyIsCompleted(id = "$1")

quest_setDayNumberRequiredToStart

• quests\["(.*)"\].SetDayNumberRequiredToStart\((.*)\)
• quest_setDayNumberRequiredToStart(id = "$1",$2)

new_day

• tm.new_day\((.*))\
• new_day($1)

new_hour

• tm.new_hour((.*))
• new_hour($1)

setFlags

• flags\["(.*)"\] =(.*)
• setFlags("$1",$2)

What's Changed

• 55 convert pos to align by @donrp in #56
• 57 convert all class in library py by @donrp in #58

Full Changelog: v1.0.2...v1.0.3